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
bromso/metapowers/plugins/development/skills/test Skill
1★ repoWrite tests for existing code or validate test coverage
bromso/metapowers/plugins/marketing/skills/ab-test-setup Skill
1★ repoDesign A/B tests with hypothesis, measurement, and statistical rigor
bromso/metapowers/plugins/security/skills/security-testing Skill
1★ repoPlan SAST, DAST, SCA, and penetration testing program
tuannv14/claude-team-toolkit/skills/maestro Skill
1★ repoUse when running mobile E2E on React Native / iOS / Android, recording user flows, inspecting view hierarchy, or hunting flaky UI tests with Maestro. Multi-environment via MAESTRO_PROFILE.
tuannv14/claude-team-toolkit/skills/rspec Skill
1★ repoUse when running RSpec on a Rails project — re-running only failed examples, parallelizing with parallel_tests, generating coverage, or bisecting test-order failures. Multi-project via RSPEC_PROFILE.
Thanasimos/Thanas-flare-builders-toolkit/flare-dapp-pitfalls Skill
1★ repoHard-won, cross-project lessons from building, deploying, and operating Flare-family (Flare / Songbird / Coston2) dApps. Use this skill whenever the user is: deploying or interacting with a Flare/Songbird/Coston2 contract, building a frontend with RainbowKit + Wagmi for Flare chains, writing Foundry fork tests against Flare-family state, claiming or rotating FTSO reward redistributors, debugging a stuck or silently-failing transaction, choosing RPC endpoints for browser vs server use, or troubleshooting MetaMask / wallet connection on Flare. Trigger on any mention of: Flare RPC, Songbird canary, Coston2 testnet, FTSO reward claim, WNAT vote-power, FlareDrops, FtsoRewardRedistributor, FlaresRewardsRedistributorForNft, Enosys redistributor, RainbowKit MetaMask hang, Ankr origin locked, Multicall3 on Flare, EIP-150 63/64 gas, eth_getLogs 30-block cap, "why is my Flare contract test failing in CI", "why did my claim transaction return zero", "Wrap SGB to WSGB", or any question about gotchas specific to Flare-family chains.
Thanasimos/Thanas-flare-builders-toolkit/test-foundry Skill
1★ repoGenerate a comprehensive Foundry/Forge test suite for a Solidity contract. Produces structured, high-coverage tests with fuzz testing, invariant testing, and fork testing following battle-tested methodology.
Thanasimos/Thanas-flare-builders-toolkit/test-hardhat Skill
1★ repoGenerate a comprehensive Hardhat test suite for a Solidity contract. Produces structured, high-coverage tests following battle-tested smart contract testing methodology.
SkillMedev/b2b-prospecting-engine/skills/prospecting-metrics Skill
1★ repoUse when you need to turn outbound prospecting into a measurable, backsolvable funnel instead of guesswork - for quota planning, activity targets, funnel diagnosis, and A/B test sizing. Triggers include "how many emails do I need to send", "backsolve my quota", "what's a good reply rate", "how many meetings per 100 contacts", "my outbound isn't converting", "where is my funnel breaking", "is this A/B test significant", "how many contacts to hit pipeline target", "what activity do I need this week", and "what conversion rates should I expect for cold outbound". Workflow: define the canonical funnel, plug in your real (or benchmark) conversion rates, backsolve required weekly activity from a quota, diagnose which stage is broken, and size tests honestly. Do NOT use for writing the actual messages - use [[cold-email-craft]]; Do NOT use for designing the multi-step cadence itself - use [[outreach-sequence-designer]]; Do NOT use for fixing inbox placement - use [[cold-email-deliverability]].
The same file is in 1 other repository
lifesight/lifesight/skills/lifesight-experiment-design Skill
1★ repoUse when the user wants to prove or validate causality with an experiment — "is X actually incremental", "prove this channel works", "design a geo-lift test", "set up a holdout", "run an incrementality test", "what should I test next", "read my experiment results", "did the test work", "validate the optimization before we commit". Covers both designing tests and interpreting results. Routed to from the `lifesight` router after the workspace is calibrated.
lubochka/xiigen-general-skills/agent-skills/e2e-test-matrix Skill
1★ repoDesign end-to-end coverage across critical paths. Use for release readiness, user workflows, UI/API flows, and adapter validation.
lubochka/xiigen-general-skills/agent-skills/integration-testing Skill
1★ repoVerify boundaries between components. Use when behavior crosses services, modules, tools, adapters, or data formats.
lubochka/xiigen-general-skills/agent-skills/test-integrity Skill
1★ repoKeep tests meaningful and honest. Use when writing, changing, disabling, or interpreting tests.
lubochka/xiigen-general-skills/agent-skills/user-journey-testing Skill
1★ repoValidate work through a realistic user path. Use for UX, tool workflows, onboarding, and generated instructions.
lubochka/xiigen-general-skills/claude/skills/e2e-test-matrix Skill
1★ repoDesign end-to-end coverage across critical paths. Use for release readiness, user workflows, UI/API flows, and adapter validation.
lubochka/xiigen-general-skills/claude/skills/integration-testing Skill
1★ repoVerify boundaries between components. Use when behavior crosses services, modules, tools, adapters, or data formats.
lubochka/xiigen-general-skills/claude/skills/test-integrity Skill
1★ repoKeep tests meaningful and honest. Use when writing, changing, disabling, or interpreting tests.
lubochka/xiigen-general-skills/claude/skills/user-journey-testing Skill
1★ repoValidate work through a realistic user path. Use for UX, tool workflows, onboarding, and generated instructions.
lubochka/xiigen-general-skills/codex/skills/e2e-test-matrix Skill
1★ repoDesign end-to-end coverage across critical paths. Use for release readiness, user workflows, UI/API flows, and adapter validation.
lubochka/xiigen-general-skills/codex/skills/integration-testing Skill
1★ repoVerify boundaries between components. Use when behavior crosses services, modules, tools, adapters, or data formats.
lubochka/xiigen-general-skills/codex/skills/test-integrity Skill
1★ repoKeep tests meaningful and honest. Use when writing, changing, disabling, or interpreting tests.
lubochka/xiigen-general-skills/codex/skills/user-journey-testing Skill
1★ repoValidate work through a realistic user path. Use for UX, tool workflows, onboarding, and generated instructions.
lubochka/xiigen-general-skills/skills/universal/e2e-test-matrix Skill
1★ repoOpen-source AI agent skills for safer Claude, Codex and Cursor coding workflows
lubochka/xiigen-general-skills/skills/universal/integration-testing Skill
1★ repoOpen-source AI agent skills for safer Claude, Codex and Cursor coding workflows
lubochka/xiigen-general-skills/skills/universal/test-integrity Skill
1★ repoOpen-source AI agent skills for safer Claude, Codex and Cursor coding workflows
lubochka/xiigen-general-skills/skills/universal/user-journey-testing Skill
1★ repoOpen-source AI agent skills for safer Claude, Codex and Cursor coding workflows
jajupmochi/agent-harness/skills/general/code-verifier Skill
1★ repoUse BEFORE claiming any code/test/script runs successfully. Detects FAKE-RUN patterns (hardcoded results, assert True, mocks-only tests, swallowed exceptions, fabricated numbers, dead-code short-circuits). Apply automatically whenever about to claim "test passes", "code works", "results show X", "training converges", or commit/push. Complements superpowers:verification-before-completion (which enforces real-run discipline) by auditing whether the run itself is genuine.
Playwright ops demo playwright browser
guorunjie/skillpack-forge/examples/generated/playwright-browser/.claude/skills/playwright-ops-demo-playwright-browser Skill
1★ repoUse when running playwright browser workflows for playwright-ops-demo.
Playwright ops demo playwright browser
guorunjie/skillpack-forge/examples/generated/playwright-browser/.codex/skills/playwright-ops-demo-playwright-browser Skill
1★ repoUse when running playwright browser workflows for playwright-ops-demo.
Test automation demo test automation
guorunjie/skillpack-forge/examples/generated/test-automation/.claude/skills/test-automation-demo-test-automation Skill
1★ repoUse when running test automation workflows for test-automation-demo.
Test automation demo test automation
guorunjie/skillpack-forge/examples/generated/test-automation/.codex/skills/test-automation-demo-test-automation Skill
1★ repoUse when running test automation workflows for test-automation-demo.
ninnettesudanese653/claude-plugins/plugins/socials/commands/test Skill
1★ repoComprehensive test suite for all Socials tools and functionality
ssurmic/claude-investment-skills/earnings-flash-dip-catch Skill
no license1★ repoSTOCK TRADING ONLY — Build a post-earnings "catch the flash dip, sell the strength" ladder (财报接飞刀 / 盘后捞货). Pulls latest + after-hours price, the key stats, option walls + max pain + the straddle expected move, finds the MOST-RECENT price shelf, and outputs tiered limit-buy catch levels + sell levels + a structural stop. Use when user asks Chinese: "$TICKER 财报接飞刀", "$TICKER 财报后怎么接", "盘后捞货", "$TICKER 闪跌接刀", "财报后抄底 $TICKER", "$TICKER 财报砸下来怎么买", or English: "catch the dip on $TICKER earnings", "$TICKER post-earnings flash dip", "where to buy $TICKER after earnings", "$TICKER earnings knife-catch ladder". DO NOT trigger for: code/CI "flaky test" catches, exception/error catching, fishing, or any non-equity topic. Requires a clear ticker + an earnings/post-earnings context.
Shivam990q/better-than-claude-skills/skill-creator Skill
1★ repoBehavioral guidelines to reduce common LLM coding mistakes AND a complete system for creating, testing, and optimizing skills. Use this skill WHENEVER the user asks you to write, review, debug, refactor, or discuss code — or whenever you are about to generate any code yourself. Also use when the user wants to create a skill from scratch, edit or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. Apply to every coding task including fixing bugs, adding features, creating new files, refactoring, code reviews, architecture discussions, writing tests, and skill development.
Shivam990q/better-than-claude-skills/webapp-testing Skill
1★ 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
alexngai/skill-tree/docs/demo/skills/react-component-testing Skill
1★ repoTest React components with Testing Library — render, query by role, and assert on user-visible behavior.
alexngai/skill-tree/docs/demo/skills/vitest-migration Skill
1★ repoMigrate a Jest test suite to Vitest — config, globals, and mock API differences.
alexngai/skill-tree/scraper/test/fixtures/valid-skill Skill
1★ repoHelps write and debug React component tests using React Testing Library. Use when writing unit tests for React components, debugging test failures, or setting up testing infrastructure.
svyatov/agent-toolkit/plugins/generate-cicd/skills/generate-cicd Skill
1★ repoGenerate CI/CD workflows (GitHub Actions) through interactive conversation by analyzing repository structure and user preferences. Use when the user asks to: (1) set up CI/CD for a project, (2) create GitHub Actions workflows, (3) add automated testing/building/deployment pipelines, (4) improve or review existing CI/CD configuration. Also use when the user mentions automating tests, running checks on PRs, or deploying on merge — even without explicitly saying "CI/CD". Triggers on: "CI/CD", "CI", "GitHub Actions", "workflow", "pipeline", "continuous integration", "continuous deployment", ".github/workflows", "automate tests", "run checks on PRs", "deploy on merge".
svyatov/agent-toolkit/plugins/refactor/skills/refactor Skill
1★ repoALWAYS use this skill before refactoring any code. It prevents over-refactoring and wrong refactoring by requiring an assessment first — catching code that is already clean, problems that are architectural rather than code-level, and missing test coverage that must exist before touching business logic. Trigger on: refactor, clean up, simplify, reduce complexity, code smells, messy code, break up function, reduce nesting, remove dead code, file too big, extract method, too many parameters, duplicated code, cognitive complexity, god class, magic numbers. Also trigger when a linter or static analysis tool flags complexity issues. Language-agnostic.
Playwright vision low resource
chf3198/megingjord-harness/skills/playwright-vision-low-resource Skill
no license1★ repoApply a low-resource operating profile for Playwright MCP + Claude Vision on constrained machines. Use this at session start, before visual QA, or after browser-context/OOM failures. Establishes bounded retries, local-vs-remote execution split, and optimized screenshot/vision practices.
shane9coy/katana-agent/agent/skills/agent-tools/playwright Skill
no license1★ repoBrowser automation via Playwright MCP — reservations, ordering, scraping, form filling. Always confirm before final submission.
yyykf/spellbook-skills/skills/test-driven-development Skill
1★ repoUse when implementing a feature, fixing a bug, or changing behavior — write a failing test first, watch it fail, write minimal code to pass, then refactor. Adds Kent Beck's Tidy First (separate structural vs behavioral changes) and a Canon test list. Language-agnostic core; per-language notes under references/languages/. Not for throwaway prototypes, generated code, or pure config changes (ask first).
The same file is in 1 other repository
SWEStash/swe-workflow-skills/plugins/architect/skills/project-review Skill
1★ repoReview a built project's execution health before a milestone — scope alignment, roadmap / execution-plan adherence, implementation maturity (what's production-ready vs stub/deferred), and the evidence it actually works (tests, coverage, validation results, changelog). Use strategic-review for vision/positioning/market; technical-debt-review for a pure code-health audit.
SWEStash/swe-workflow-skills/plugins/backend/skills/code-slop-cleanup Skill
1★ repoStrip AI slop from a branch diff before PR — judge each hunk against the surrounding file's conventions, remove without changing behavior, re-run tests. Removal only: hunting bugs → code-reviewing; structural improvement → refactoring; repo-wide audit → technical-debt-review; pruning tests → test-suite-design.
SWEStash/swe-workflow-skills/plugins/backend/skills/tdd-workflow Skill
1★ repoGuide test-driven development with red-green-refactor. For NEW code via test-first — use test-suite-design for adding tests to existing code.
SWEStash/swe-workflow-skills/plugins/backend/skills/test-data-strategy Skill
1★ repoDesign and generate test data — factories, synthetic data, property-based testing, boundary analysis, contract testing, load scenarios, GDPR-safe data. Triggers: test data, synthetic data, fake data, factory, seed data, fixtures, property-based testing, fuzz testing, boundary values, contract testing, Pact, load test data, anonymize, GDPR test data.
SWEStash/swe-workflow-skills/plugins/backend/skills/test-suite-design Skill
1★ repoDesign comprehensive test suites for existing code — strategy across unit/integration/e2e, fixtures, factories, helpers. Triggers: add tests, write tests for, increase coverage, test this module, testing strategy, test plan, what tests do I need, test infrastructure, test helpers, this has no tests. Not for TDD — use tdd-workflow.
SWEStash/swe-workflow-skills/plugins/data-scientist/skills/data-quality Skill
1★ repoKeep warehouse and pipeline data trustworthy — dbt tests, expectations (Great Expectations/Soda), data contracts with upstream producers, source freshness, schema-drift and volume anomaly detection, lineage and blast radius, severity and alerting. Triggers: data quality, bad data in dashboards, data validation, dbt tests, data contract, schema drift, stale data, freshness check, duplicate rows, nulls in the warehouse, data lineage, data SLA, upstream schema change broke us. Generating test/synthetic data → test-data-strategy; schema design → data-modeling.
SWEStash/swe-workflow-skills/plugins/data-scientist/skills/statistical-analysis Skill
1★ repoDesign and analyze experiments and statistical tests — test selection with stated assumptions, sample size and power, effect sizes and confidence intervals over bare p-values, and pitfall discipline (multiple comparisons, p-hacking, peeking/optional stopping). Owns experiment statistics generally; live A/B evaluation of AI/LLM apps (quality metrics, judges, feedback) → ai-evaluation.
SWEStash/swe-workflow-skills/plugins/data/skills/data-quality Skill
1★ repoKeep warehouse and pipeline data trustworthy — dbt tests, expectations (Great Expectations/Soda), data contracts with upstream producers, source freshness, schema-drift and volume anomaly detection, lineage and blast radius, severity and alerting. Triggers: data quality, bad data in dashboards, data validation, dbt tests, data contract, schema drift, stale data, freshness check, duplicate rows, nulls in the warehouse, data lineage, data SLA, upstream schema change broke us. Generating test/synthetic data → test-data-strategy; schema design → data-modeling.
SWEStash/swe-workflow-skills/plugins/data/skills/test-data-strategy Skill
1★ repoDesign and generate test data — factories, synthetic data, property-based testing, boundary analysis, contract testing, load scenarios, GDPR-safe data. Triggers: test data, synthetic data, fake data, factory, seed data, fixtures, property-based testing, fuzz testing, boundary values, contract testing, Pact, load test data, anonymize, GDPR test data.
SWEStash/swe-workflow-skills/plugins/devops/skills/cicd-pipeline Skill
1★ repoDesign CI/CD pipelines for automated build, test, deploy — GitHub Actions, GitLab CI, quality gates. Triggers: CI/CD, pipeline, GitHub Actions, GitLab CI, workflow, automated deployment, build pipeline, continuous integration, continuous deployment, automate tests on PR, deploy automatically, quality gate.
SWEStash/swe-workflow-skills/plugins/em/skills/dx-audit Skill
1★ repoAudit and improve developer experience — inner-loop feedback (build/test/reload times), CI wait and queue times, flaky tests, local environment setup, onboarding time-to-first-PR, tooling friction, docs discoverability; produce a prioritized remediation plan. Triggers: developer experience, DX audit, devex, builds are slow, CI takes forever, flaky tests, onboarding takes weeks, tooling friction, developer productivity, engineers are frustrated. Code health/debt hotspots → technical-debt-review; designing one pipeline → cicd-pipeline.
SWEStash/swe-workflow-skills/plugins/em/skills/project-review Skill
1★ repoReview a built project's execution health before a milestone — scope alignment, roadmap / execution-plan adherence, implementation maturity (what's production-ready vs stub/deferred), and the evidence it actually works (tests, coverage, validation results, changelog). Use strategic-review for vision/positioning/market; technical-debt-review for a pure code-health audit.
SWEStash/swe-workflow-skills/plugins/frontend/skills/browser-verification Skill
1★ repoVerify a web app change by driving the real UI in a browser — reproduce the user flow end to end, watch console errors and network failures, exercise loading/error/empty states, capture screenshots as evidence. Use before claiming a UI change works. Triggers: check it in the browser, verify the UI, click through the flow, console errors, test it like a user, smoke test the frontend. Designing persistent test suites → test-suite-design; the generic done-gate → verification-before-completion (this is its browser-specific practice).
SWEStash/swe-workflow-skills/plugins/frontend/skills/code-slop-cleanup Skill
1★ repoStrip AI slop from a branch diff before PR — judge each hunk against the surrounding file's conventions, remove without changing behavior, re-run tests. Removal only: hunting bugs → code-reviewing; structural improvement → refactoring; repo-wide audit → technical-debt-review; pruning tests → test-suite-design.
SWEStash/swe-workflow-skills/plugins/frontend/skills/tdd-workflow Skill
1★ repoGuide test-driven development with red-green-refactor. For NEW code via test-first — use test-suite-design for adding tests to existing code.
SWEStash/swe-workflow-skills/plugins/frontend/skills/test-suite-design Skill
1★ repoDesign comprehensive test suites for existing code — strategy across unit/integration/e2e, fixtures, factories, helpers. Triggers: add tests, write tests for, increase coverage, test this module, testing strategy, test plan, what tests do I need, test infrastructure, test helpers, this has no tests. Not for TDD — use tdd-workflow.
SWEStash/swe-workflow-skills/plugins/ml/skills/test-data-strategy Skill
1★ repoDesign and generate test data — factories, synthetic data, property-based testing, boundary analysis, contract testing, load scenarios, GDPR-safe data. Triggers: test data, synthetic data, fake data, factory, seed data, fixtures, property-based testing, fuzz testing, boundary values, contract testing, Pact, load test data, anonymize, GDPR test data.