evidence-artifact
Turns a ticket's test evidence into ONE private claude.ai page (an Artifact) that a developer or PM can open and read: a verdict header, the build under test,…
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-05 00:16
Testing & quality
13,127 results
exploratory-testing
Ticket-free exploratory testing of a critical flow, a module or the whole product, across UI, API and DB together, in the Execution stage. Runs a charter, a…
playwright-best-practices
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking…
sprint-conductor
Boot, run and resume the sprint QA conductor: one session that conducts a fleet of sprint-testing workers (one per ticket) on Orca and watches the whole sprint…
adapt-framework
Adapt this boilerplate's KATA test architecture, auth, schemas, variables, fixtures, CI, MCPs, and reporting to a project already reverse-engineered by…
agentic-qa-core
Foundation skill that hosts shared references cited by other workflow skills (briefing template, dispatch patterns, orchestration doctrine, skill composition…
agentic-qa-onboard
Walks new users through this repo's QA flow — Playwright + KATA + Allure + Xray stack, Jira QA workflow (Backlog → Shift-Left QA → Estimation → Ready For Dev →…
pr-review-lead
Acts as a QA Lead / QA Architect reviewing a pull request's test-automation work against this repo's KATA doctrine (or the target repo's own doctrine, if it…
regression-testing
Execute regression test suites via CI/CD, analyze results, classify failures, and produce GO/NO-GO release decisions. Use when running regression, smoke, or…
shift-left-testing
Orchestrates pre-sprint Shift-Left QA on a batch of backlog Stories. Use when the user wants to refine acceptance criteria, surface ambiguities + gaps, draft…
sprint-testing
Orchestrates in-sprint manual QA per issue across Stages 1 (Planning), 2 (Execution) and 3 (Reporting). Use for user-story testing, bug retesting, and…
test-automation
Plan, write, and review automated tests following KATA (Komponent Action Test Architecture) on Playwright + TypeScript, or explain existing automated tests in…
test-documentation
Analyze, prioritize, and document test cases in TMS (Jira/Xray), or repair an existing Story-ATS-ATP-ATR-TC cascade through a sealed explicit mode. Use for…
control-cli
Build a local harness to drive, inspect, and profile an interactive CLI or TUI. Use for CLI UX checks, startup regressions, hangs, or prompt-flow verification.
playwright
Write, run, and maintain reliable end-to-end tests with Playwright. Use for test generation, CI integration, trace debugging, and cross-browser validation.
principle-prove-it-works
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy,…
run-smoke-tests
Run Playwright smoke tests, debug failures, and verify fixes
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the…
atdd-assistant
Guide teams through Acceptance Test-Driven Development workflow. Use when: defining acceptance criteria, running specification workshops, writing user stories…
bdd-assistant
Guide developers through Behavior-Driven Development workflow. Use when: writing BDD scenarios, using Gherkin syntax, Given-When-Then format, feature files,…
testing-guide
Testing pyramid and test writing standards for UT/IT/ST/E2E. Supports ISTQB and Industry Pyramid frameworks. Use when: writing tests, discussing test coverage,…
ack-code-review
Receive a code review report, judge item by item whether to adopt it, and perform incremental fixes for the adopted issues based on the current code. Use when the user asks to handle a review report, adopt or reject review findings, continue fixing after code…
e2e-find
Run the current web service, analyze the system interaction flow based on the code, and generate or iterate end-to-end test case Markdown specifications. Use when the user asks to analyze a web app flow, discover e2e scenarios, generate test cases from code,…
e2e-run
Run the current project's e2e assets, save execution results, and output problem analysis and follow-up recommendations. Use when the user asks to run e2e tests, execute Playwright/Cypress cases, validate an existing e2e spec against a running…