Test
10,621 rows, by stacks then stars
1,559 of these skill files have been read, by 1,201 distinct authors, and what they tell an agent counted. What Test authors agree on, and what they forbid
imtiazrayhan/agentscamp-library/skills/mock-data-factory Skill
1★ repoGenerate a typed mock/fixture factory for a given type, interface, or schema, inferring believable values from field names and types. Use when tests or local dev need realistic, type-safe sample data with per-field overrides.
imtiazrayhan/agentscamp-library/skills/mutation-test-runner Skill
1★ repoMeasure whether a test suite actually catches bugs by running mutation testing — introduce small faults into the code and check which ones a test kills versus which slip through silently. Use when line coverage is high but bugs still ship, when you suspect tests assert weakly, or to find the exact assertions a suite is missing.
imtiazrayhan/agentscamp-library/skills/property-test-designer Skill
1★ repoDesign property-based tests — generate hundreds of random inputs and assert invariants that must hold for ALL of them — to surface the edge cases hand-picked examples never reach. Use when code has a large input space (parsers, serializers, encoders, math, data transforms), when a bug keeps slipping through despite green example tests, or when you can't enumerate every case worth checking.
imtiazrayhan/agentscamp-library/skills/test-scaffolder Skill
1★ repoScaffold a test file with sensible cases for a given module or function. Use when adding tests to untested code and you want a fast, structured starting point.
imtiazrayhan/agentscamp-library/skills/type-coverage-improver Skill
1★ repoRaise TypeScript type strictness incrementally — measure the any/implicit-any baseline, enable one strict sub-flag at a time, and fix the fallout per flag instead of all at once, keeping the typecheck green at every step. Use when a codebase is loosely typed, when you want strict mode on without a big-bang break, or when `any` keeps hiding bugs that surface in production.
vindm/dotclaude/plugins/core/skills/testing Skill
1★ repoElicit test-coverage risk priorities for a project and write them to a thin artifact — `.claude/dotclaude/test-risk-model.md` plus a `dotclaude.yml` key — derived from the project's actual test/source ratio, its most-edited untested files, and the user's own sense of what scares them most. No agent, rule, or hook is authored: the consumed `test-architect` agent already reads this artifact at runtime. Invoke /dotclaude:testing in any project where tests exist OR should exist.
vindm/dotclaude/plugins/design/skills/persona-testing Skill
1★ repoRun three orthogonal outside-eyes tests on every user-visible string — day-30 (frequency-jaded), partner (voice-register), and stranger (already-knows-me) — to catch voice violations that pass a deny-list but still feel wrong. Load at design time on every proposed string and at audit time on every visible string on a captured surface.
SkillMedev/legacy-modernization/skills/tdd-expert Skill
1★ repoDrive development with strict Red-Green-Refactor discipline - write one failing test, write the minimum code to pass it, refactor on green - including test-list planning and a worked kata cycle. Use when someone asks "write this test-first", "do TDD on this feature", "help me practice red-green-refactor", "write a failing test for this bug", or wants tests to drive a new module's design. Do NOT use for adding tests to existing untested legacy code before a refactor - use characterization-test-writer instead - or for designing shared fixtures and factories - use test-data-builder instead.
The same file is in 3 other repositories
simanam/theaiteam/team/skills/engineering/test-driven-development Skill
no license1★ repoUse when implementing any feature or bugfix, before writing implementation code
The same file is in 33 other repositories
simanam/theaiteam/team/skills/qa/_trailofbits/mutation-testing/skills/mutation-testing Skill
no license1★ repoConfigures mewt or muton mutation testing campaigns — scopes targets, tunes timeouts, and optimizes long-running runs. Use when the user mentions mewt, muton, mutation testing, or wants to configure or optimize a mutation testing campaign.
The same file is in 2 other repositories
simanam/theaiteam/team/skills/qa/_trailofbits/property-based-testing/skills/property-based-testing Skill
no license1★ repoProvides guidance for property-based testing across multiple languages and smart contracts. Use when writing tests, reviewing code with serialization/validation/parsing patterns, designing features, or when property-based testing would provide stronger coverage than example-based tests.
The same file is in 6 other repositories
simanam/theaiteam/team/skills/qa/ai-regression-testing Skill
no license1★ repoRegression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.
The same file is in 6 other repositories
simanam/theaiteam/team/skills/qa/webapp-testing Skill
no license1★ repoToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
The same file is in 45 other repositories
simanam/theaiteam/team/skills/security/_trailofbits/building-secure-contracts/skills/audit-prep-assistant Skill
no license1★ repoPrepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments).
The same file is in 4 other repositories
simanam/theaiteam/team/skills/security/_trailofbits/differential-review/skills/differential-review Skill
no license1★ repoPerforms security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.
The same file is in 2 other repositories
iwritec0de/wp-dev/skills/wp-testing Skill
1★ repoThis skill should be used when the user asks to 'write WordPress tests', 'add PHPUnit tests', 'test a plugin', 'test a theme', 'test REST endpoints', 'test WooCommerce', 'set up WordPress testing', 'bootstrap PHPUnit for WordPress', or mentions 'WP_UnitTestCase', 'WordPress test factories', 'phpunit wordpress', 'wp-env testing'. Provides WordPress-specific testing patterns using PHPUnit and the WordPress test suite.
dayvisonassis/sdd-skills/skills/evaluator Skill
1★ repoExternally evaluates an already-implemented feature against its contract.md (environment, quality gates, coverage manifest, observable criteria), producing screenshots, a report, and chat findings. Owns the evaluation loop — keeps the attempt counter in progress.json, decides the state (CLEAN/FAIL/PENDING/ABORTED), and routes each failure: code failures (gate/observable) to fix-runner, test failures to the matching test-writer (then confirmed by the matching test-validator) before resuming. Loops until CLEAN, PENDING, or ABORTED.
dayvisonassis/sdd-skills/skills/implement-feature Skill
1★ repoImplements a feature autonomously based on its spec, plan, AND contract.md, committing one commit per phase, satisfying the contract's quality gates and observable criteria, writing progress.json, and reporting results against the feature's acceptance criteria. Delegates test writing to the matching test-writer skill (unit/integration/monorepo) by path/stack when the project fits, and falls back to writing tests itself otherwise.
dayvisonassis/sdd-skills/skills/integration-test-validator Skill
1★ repoAudits PABX backend integration tests (apps/backend/__tests__/integration/) against the integration-test-writer rules, producing a compliance report with a PASS/FAIL/PASS WITH WARNINGS verdict, per-violation severity, and fix suggestions. Read-only — never writes or fixes tests. Dispatched by the evaluator to confirm a corrected integration test conforms before resuming evaluation, or run directly by a user.
dayvisonassis/sdd-skills/skills/integration-test-writer Skill
1★ repoPlans and implements comprehensive integration tests for the PABX backend (apps/backend/__tests__/integration/) using Jest + supertest against a real test database. Runs interactively (3 phases with an approval checkpoint) when a user calls directly, or autonomously (no pause) when dispatched by implement-feature/evaluator. Also runs in correction mode to fix a specific failing integration test flagged by the evaluator. Enforces PABX rules (setupTestDatabase, try-finally cleanup, foreign-key order, English-only, NODE_ENV=testing, batches). Never modifies production code.
dayvisonassis/sdd-skills/skills/monorepo-unit-test-validator Skill
1★ repoAudits PABX monorepo unit tests (node-express, node-worker, python-fastapi apps outside apps/backend and apps/frontend) against the monorepo-unit-test-writer rules, auto-detecting the stack and producing a compliance report with a PASS/FAIL/PASS WITH WARNINGS verdict, per-violation severity, and fix suggestions. Read-only — never writes or fixes tests. Dispatched by the evaluator to confirm a corrected test conforms before resuming evaluation, or run directly by a user.
dayvisonassis/sdd-skills/skills/monorepo-unit-test-writer Skill
1★ repoPlans and implements unit tests for any PABX monorepo app EXCEPT apps/backend and apps/frontend — auto-detecting the stack (node-express, node-worker, or python-fastapi) and applying stack-specific patterns. Runs interactively (3 phases with an approval checkpoint) when a user calls directly, or autonomously (no pause) when dispatched by implement-feature/evaluator. Also runs in correction mode to fix a specific failing test flagged by the evaluator. Enforces PABX rules (mock-before-import, Promise.all() mocks, GPU/torch mocks, English-only, batches). Never modifies production code.
dayvisonassis/sdd-skills/skills/unit-test-validator Skill
1★ repoAudits unit tests in the PABX monorepo (Angular frontend .spec.ts + Node.js backend __tests__/unit/) against the unit-test-writer rules, producing a compliance report with a PASS/FAIL/PASS WITH WARNINGS verdict, per-violation severity, and fix suggestions. Read-only — never writes or fixes tests. Dispatched by the evaluator to confirm a corrected test conforms before resuming evaluation, or run directly by a user.
dayvisonassis/sdd-skills/skills/unit-test-writer Skill
1★ repoPlans and implements comprehensive unit tests for the PABX monorepo — Angular frontend (Jest + jest-preset-angular, .spec.ts) and Node.js backend (Jest, apps/backend/__tests__/unit/). Runs interactively (3 phases with an approval checkpoint) when called by a user, or autonomously (no pause) when dispatched by implement-feature/evaluator. Also runs in correction mode to fix a specific failing test flagged by the evaluator. Enforces PABX rules (real component imports, manual service instantiation, localStorage/jQuery mock order, Promise.all() mock correctness, cleanup, English-only). Never modifies production code.
iggmasterdev/badquality-lab/agile-tester/skills/exploratory-charter Skill
1★ repoGenerate session-based exploratory testing charters for a feature, area, or build — each with a mission, timebox, test ideas, heuristics and oracles, personas to adopt, a soap-opera scenario, data setup needs, and a session sheet to record results. Use this whenever someone wants to do exploratory testing, asks for a test charter, asks "what should I poke at" or "how should I explore this feature", mentions session-based testing, persona testing, or soap-opera testing, or wants structured-but-unscripted testing beyond their automated checks. Trigger even when the user just says "I need to test this new feature and don't know where to start" — charters are the structured way in.
iggmasterdev/badquality-lab/agile-tester/skills/testing-quadrants-mapper Skill
1★ repoMap a feature, story, release, or system to the four Agile Testing Quadrants and produce a concrete test-coverage plan — what to test, who owns it, automated vs manual, when, and with which modern tools — that deliberately surfaces the test types teams forget (Quadrant 3 exploratory/UAT/usability and Quadrant 4 performance/security/reliability). Use this whenever someone asks what tests a feature needs, plans test coverage or a test strategy for a story or release, asks "am I missing any kinds of testing", wonders how to balance unit vs functional vs exploratory, or mentions the testing quadrants. Trigger even when the user only describes a feature and asks "how should I test this" — the quadrants are the right lens for a complete answer.
iggmasterdev/badquality-lab/example-mapping Skill
1★ repoTurn a raw user story or feature request into a shared, testable specification BEFORE coding starts: clarifying questions, concrete examples, acceptance criteria as Given/When/Then, conditions of satisfaction, a ripple-effect impact list, and a "ready / not ready" verdict. Use this whenever someone is refining, grooming, or kicking off a story; writing or reviewing acceptance criteria; preparing a three-amigos / example-mapping session; checking a Definition of Ready; or asking "what should this feature actually do" or "is this story ready to build". Trigger even if the user only pastes a story and asks for tests or scenarios — the right first move is to map examples, not jump to test cases.
iggmasterdev/badquality-lab/exploratory-charter Skill
1★ repoGenerate session-based exploratory testing charters for a feature, area, or build — each with a mission, timebox, test ideas, heuristics and oracles, personas to adopt, a soap-opera scenario, data setup needs, and a session sheet to record results. Use this whenever someone wants to do exploratory testing, asks for a test charter, asks "what should I poke at" or "how should I explore this feature", mentions session-based testing, persona testing, or soap-opera testing, or wants structured-but-unscripted testing beyond their automated checks. Trigger even when the user just says "I need to test this new feature and don't know where to start" — charters are the structured way in.
iggmasterdev/badquality-lab/testing-quadrants-mapper Skill
1★ repoMap a feature, story, release, or system to the four Agile Testing Quadrants and produce a concrete test-coverage plan — what to test, who owns it, automated vs manual, when, and with which modern tools — that deliberately surfaces the test types teams forget (Quadrant 3 exploratory/UAT/usability and Quadrant 4 performance/security/reliability). Use this whenever someone asks what tests a feature needs, plans test coverage or a test strategy for a story or release, asks "am I missing any kinds of testing", wonders how to balance unit vs functional vs exploratory, or mentions the testing quadrants. Trigger even when the user only describes a feature and asks "how should I test this" — the quadrants are the right lens for a complete answer.
pipipip169/fable5-handoff/sources/adamentwistle-fable-skills/edge-case-sweep Skill
no license1★ repoEnumerate edge cases against a concrete checklist before declaring code complete. Use when implementing or reviewing any function, handler, parser, or data transformation — after the happy path works, before reporting done.
pipipip169/fable5-handoff/sources/adamentwistle-fable-skills/root-cause-debugging Skill
no license1★ repoSystematic debugging — reproduce, bisect, prove the cause with a falsifiable hypothesis, fix minimally, re-verify against the original repro. Use for any bug, test failure, regression, or flaky behavior, before proposing a fix — and whenever a first fix didn't work.
pipipip169/fable5-handoff/sources/adamentwistle-fable-skills/test-design Skill
no license1★ repoWhat to test and how — regression test fails first, boundary tables, behavior over implementation, boundary-only mocks, the mock-echo trap. Use when writing tests, adding regression coverage for a fix, or judging whether existing tests protect anything.
Dolphinllc/claude-security-skills/skills/offensive/genai/anthropic-sdk-attack-probe Skill
1★ repoAuthorized red-team probe for applications built on the Anthropic SDK. Tests Claude-specific quirks - XML/tag confusion attacks, tool_use schema bypass, prompt-cache cross-tenant probing, and assistant-prefill manipulation - against your own chat or agent endpoint discovered via env/entrypoint. Use when the user asks to "red-team" or "attack-test" their Claude-based app.
Dolphinllc/claude-security-skills/skills/offensive/genai/langchain-attack-probe Skill
1★ repoAuthorized red-team probe for applications built on LangChain or LangGraph. Tests PythonREPL/ShellTool exploitation, RAG injection via user-uploaded documents, output-parser injection, callback-handler leakage, and SQL agent privilege checks against your own endpoint discovered via env/entrypoint. Use when the user asks to "red-team" or "attack-test" their LangChain app.
Dolphinllc/claude-security-skills/skills/offensive/genai/mcp-server-attack-probe Skill
1★ repoAuthorized red-team probe for Model Context Protocol (MCP) servers. Tests tool path traversal, command injection in shell-like tools, SSRF via fetch tools, HTTP/SSE transport authentication, DNS rebinding via Origin header, and resource URI traversal. Use when the user asks to "red-team" or "attack-test" their own MCP server.
Dolphinllc/claude-security-skills/skills/offensive/genai/openai-sdk-attack-probe Skill
1★ repoAuthorized red-team probe for applications built on the OpenAI SDK. Tests function-calling schema bypass, structured-output schema escape, Assistants thread cross-tenant access, and vision payload injection against your own endpoint discovered via env/entrypoint. Use when the user asks to "red-team" or "attack-test" their OpenAI-based app.
Dolphinllc/claude-security-skills/skills/offensive/genai/vercel-ai-sdk-attack-probe Skill
1★ repoAuthorized red-team probe for applications built on the Vercel AI SDK (`ai` package). Tests tool execute exploitation via crafted user messages, useChat endpoint authentication, attachment limits, and streamText/dangerouslySetInnerHTML XSS via injected markdown. Use when the user asks to "red-team" or "attack-test" their AI SDK app.
Dolphinllc/claude-security-skills/skills/offensive/web/express-attack-probe Skill
1★ repoAuthorized self-pentest probe targeting Express.js-specific weaknesses. Tests prototype pollution via merge/clone middlewares, HPP (HTTP parameter pollution) via body-parser, x-forwarded-for spoofing when trust proxy is loose, qs depth/array bombs, sendFile path traversal, and known unsafe middleware patterns. Use when the user asks to "pentest" or "attack-test" their own Express app.
amansingh909/claude-bounty-skills/skills/scope-check Skill
1★ repoUse when deciding whether a target (domain, subdomain, IP, endpoint, or asset) is in scope for a bug bounty program before testing it. Symptoms: "is this in scope", pasting a program's scope table, wildcard scope like *.example.com, "am I allowed to test this", ambiguous in-scope/out-of-scope rules with carve-outs.
steph-frtech/cdesign-expo/.claude/marketplaces/pocock/skills/migrate-to-shoehorn Skill
no license1★ repoMigrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
The same file is in 15 other repositories
steph-frtech/cdesign-expo/.claude/marketplaces/pocock/skills/tdd Skill
no license1★ repoTest-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
The same file is in 6 other repositories
steph-frtech/cdesign-expo/.claude/marketplaces/superpowers/skills/test-driven-development Skill
no license1★ repoUse when implementing any feature or bugfix, before writing implementation code
The same file is in 33 other repositories
steph-frtech/cdesign-expo/.claude/marketplaces/wshobson/plugins/accessibility-compliance/skills/screen-reader-testing Skill
no license1★ repoTest web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
The same file is in 4 other repositories
steph-frtech/cdesign-expo/.claude/marketplaces/wshobson/plugins/backend-development/skills/temporal-python-testing Skill
no license1★ repoTest Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
The same file is in 4 other repositories
steph-frtech/cdesign-expo/.claude/marketplaces/wshobson/plugins/blockchain-web3/skills/web3-testing Skill
no license1★ repoTest smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
The same file is in 1 other repository
steph-frtech/cdesign-expo/.claude/marketplaces/wshobson/plugins/developer-essentials/skills/e2e-testing-patterns Skill
no license1★ repoMaster end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
The same file is in 2 other repositories
steph-frtech/cdesign-expo/.claude/marketplaces/wshobson/plugins/javascript-typescript/skills/javascript-testing-patterns Skill
no license1★ repoImplement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
The same file is in 3 other repositories
steph-frtech/cdesign-expo/.claude/marketplaces/wshobson/plugins/python-development/skills/python-testing-patterns Skill
no license1★ repoImplement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
steph-frtech/cdesign-expo/.claude/marketplaces/wshobson/plugins/shell-scripting/skills/bats-testing-patterns Skill
no license1★ repoMaster Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.
The same file is in 1 other repository
steph-frtech/cdesign-expo/.claude/skills/scenario-tester Skill
no license1★ repoUse this skill whenever the user asks to add a feature, fix a bug, refactor code, or write tests. Forces a discipline of writing test scenarios in markdown BEFORE coding, mapping each scenario 1:1 to an executable test, and maintaining tests/STATUS.md. Integrates with octo-issue-tracker via OCTO-### IDs. Triggers on: "implement", "add feature", "fix bug", "refactor", "write tests", "TDD", "ajoute", "implémente", "corrige", "code".
Superpowers test driven development
steph-frtech/cdesign-expo/.claude/skills/superpowers__test-driven-development Skill
no license1★ repoUse when implementing any feature or bugfix, before writing implementation code
The same file is in 33 other repositories
AnaCataVC/amiga-ia/skills/ami-test-creator Skill
1★ repoMust be triggered when new functionality is added and no existing tests cover the changes. Automatically generates tests for modified code.
SkillMedev/ecommerce-dtc-ops/skills/landing-page-cro Skill
1★ repoImproves an existing landing page's conversion rate through evidence-first CRO - audit heatmaps and recordings, write structured hypotheses, prioritize with ICE scoring, and run one-variable tests to statistical significance. Use when someone asks "why isn't my landing page converting", "audit this page before we scale spend", "which A/B test should we run first", or after a CVR drop or ahead of a paid-traffic push. Do NOT use for writing a new landing page from scratch - use landing-page-copy instead. Do NOT use for auditing the ad accounts sending the traffic - use paid-acquisition-audit instead. Do NOT use for reading the results of a finished experiment - use ab-test-analyzer instead.
The same file is in 2 other repositories
Songhonglei/build-better-skills/skills/skill-regression Skill
1★ repoRegression testing framework for AgentSkills. Analyzes a target skill, runs script-layer assertions and AI-layer semantic scoring, and outputs a Markdown report. Supports two backends: OpenAI-compatible LLM (default, works anywhere) or OpenClaw cron-based agent trigger (auto-detected if openclaw CLI present). Use when the user asks to "test a skill", "regression test xxx skill", "run skill QA", or "audit my skill against test cases". Requires SR_LLM_API_KEY env var or interactive setup; supports .env files.
Dom1ng0s/Claude-Skills/auto-tester Skill
1★ repoDetecta a stack do alvo, gera testes com o runner nativo dela (pytest, Jest/Vitest, go test...), roda, e auto-corrige testes mal escritos (parando se achar bug real no código).
kennguyen887/agent-foundation/skills/tdd-http-first Skill
1★ repoDrive a feature/bugfix test-first when the project mandates HTTP-layer-only testing — the failing RED test must be an HTTP/route-harness test (e.g. supertest), never a service/validator/util unit test. Trigger phrases — "làm theo TDD", "viết test fail trước", "write the failing test first", "do this test-first" — in any repo whose rules forbid unit tests.
kennguyen887/agent-foundation/skills/write-frontend-tests Skill
1★ repoUse when writing frontend tests — a test-worthiness gate first (no 1:1 per-file test mirroring), then Jest + React Testing Library for components/hooks/utils that earn a test, and Cypress + Cucumber for e2e user flows. Where tests live, what to test, mocking the router, and the lint/type/test gates. React/Next.js reference.
kennguyen887/agent-foundation/skills/write-unit-tests Skill
1★ repoUse when writing isolated unit tests (mocked deps, no DB) for CQRS handlers, services, or DTOs. Mock factories, a handler testing-module helper, DTO validation, the AAA pattern, entity builders. TS/NestJS/Jest examples.
bromso/metapowers/plugins/design/skills/test Skill
1★ repoValidate the prototype against WCAG criteria and the component contract
bromso/metapowers/plugins/development/skills/review Skill
1★ repoReview code pre-merge for bugs, security, quality, and test coverage