Find the perfect skill
Performance Regression Detection
Testing
Detect performance regressions in web pages by establishing baselines and comparing before/after on every PR. Uses Web Vitals, load times, and resource sizes.
QA Scenario Builder
Testing
Create a QA test scenario sheet from a screen design document and a target Google Sheets URL by copying a template, filling metadata, and writing detailed test cases.
QA Validation for Pull Requests
Testing
Runs QA validation on a pull request: boots the local environment, tests acceptance criteria, and optionally posts the report as a PR comment.
Fallout 4 Compatibility Audit
Testing
Comprehensive Fallout 4 compatibility audit for ByroRedux: BA2 formats, half-float vertices, BGSM materials, and M49 precombines.
Delete Postman Resource
Testing
Delete a Postman resource (collection, request, environment, mock) by ID or name.
Multi-Agent Code Review
Testing
Multi-agent code review covering correctness, quality, architecture, test coverage, and security.
Test Retry Config
Testing
Automated assistance for test retry configuration. Covers unit testing, integration testing, mocking, and test framework best practices.
brepjs-cad Skill Eval and Fix Proposal
Testing
Run a brepjs-cad skill evaluation in this Claude session and propose fixes. Supports implement (default) and verify modes, no API key required.
E2E Testing Patterns
Testing
Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.
Browser Automation with agent-browser
Testing
Automate browser interactions using agent-browser CLI: navigate, click, fill forms, scrape content, take screenshots, and more.
Chaos Testing Implementer
Testing
Implement chaos engineering practices to test system resilience under failure conditions.
SonarQube Webapp Testing
Testing
This skill provides best practices for writing and understanding tests in the SonarQube web application. It covers testing philosophy, file naming conventions (unit, integration, snapshots), three testing layers (integration, unit, snapshots), and smart mocks usage. It also includes critical rules like preferring `findBy` over `waitFor` and `toBeInTheDocument` over `toBeVisible`.