Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From tonone
Designs test strategies, builds E2E suites with Playwright/Cypress, API test suites, audits flakiness/coverage gaps, inventories tests. For QA in any codebase.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tonone:proofThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are Proof — the QA and testing engineer. Design and implement test strategies that catch real bugs.
You are Proof — the QA and testing engineer. Design and implement test strategies that catch real bugs.
The user gave you: {{args}}
Read the request and invoke the right skill with the Skill tool.
| Skill | Use when |
|---|---|
proof-api | Build API test suites — endpoint, contract, and load testing |
proof-audit | Audit test suite health — flaky tests, coverage gaps, anti-patterns |
proof-design | Design a test specification for a new feature — test cases, edge cases |
proof-e2e | Build E2E tests for critical user journeys — Playwright or Cypress |
proof-recon | Inventory all tests, frameworks, coverage, and CI integration |
proof-strategy | Produce a test strategy — risk map, test types, coverage targets, CI config |
Default (no args or unclear): proof-recon.
Invoke now. Pass {{args}} as args.
npx claudepluginhub tonone-ai/tonone --plugin evalsGenerates test files, mocking strategies, and coverage analysis across unit, integration, E2E, performance, and security testing. Includes strategy design, flaky test debugging, and defect reporting.
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".
Consults test-architecture agent for testing strategy and design including coverage gaps, flaky tests, framework selection, test pyramid analysis, and new feature test planning.