Automated software testing: test strategy and portfolios, coverage policy and CI test gates, unit and integration test design, test-driven development, property-based / mutation / fuzz testing, flaky-test triage, browser and end-to-end tests. Use when asking "what should we test""write the failing test first", "is this a bug or is the test wrong",, "write a test plan", "set a coverage target", "write tests for this", "should I mock this", "do it test-first", "red-green-refactor", "are my tests good enough", "this test fails randomly", "write a Playwright test". Not for debugging the product bug itself, the pipeline's own wiring, or WCAG conformance checks; those sit outside this skill.
cp -r cryptoskill/skills/exchanges/anoscranel-ac-testing .claude/skills/clawhub install anoscranel-ac-testingCapabilities below are detected automatically by an open-source scanner that reads the skill's text and scripts (see how this is computed). Not measured means the scanner couldn't make a confident call — it is NOT a green check, and you should treat it as a possible red flag until a human or a stronger scanner has measured it.
unknown
We did not find any well-known hosted services in this skill's text or scripts. This does NOT mean the skill is local-only — it might use services we don't yet recognize, or talk to them through code paths our scanner can't reach. A complete dependency list (every package, library, and binary, with integrity hashes) is on the roadmap; today we only show recognized hosts.
No one has audited this skill yet. That is different from “audited and clean” — it just means no professional reviewer (a security firm, the CryptoSkill team, or a verified independent researcher) has signed off on it. There are no audit reports to read. How reviewer levels work →
SKILL.md → SOURCE.md → TRUST.auto.yaml → Browse directory →
Auto-generated by cryptoskill/extract-capabilities/0.3.1 · hosted-service list version 2026-09-06 · how this is computed