Test
10,607 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
intelligems-io/intelligems-mcp-skills/skills/test-roadmap Skill
0★ repoUse when a user wants a prioritized Intelligems testing roadmap based on historical results, untested areas, customer segments, and profit opportunities.
intelligems-io/intelligems-mcp-skills/skills/testing-strategy-health-check Skill
0★ repoUse when a user wants to evaluate the health of an Intelligems testing program, including velocity, win rate, test mix, learnings, and coverage gaps.
intelligems-io/intelligems-mcp-skills/skills/weekly-test-pulse Skill
0★ repoUse when a brand operator or agency asks for a quick weekly status report on running Intelligems tests and recommended next actions.
NyXXiR/skillboard/examples/multi-source-skills/matt/tdd Skill
0★ repoRun test-driven implementation loops.
NyXXiR/skillboard/examples/multi-source-skills/private/tdd-work-continuity Skill
0★ repoKeep local TDD work resumable with plan and verification notes.
NyXXiR/skillboard/examples/multi-source-skills/wshobson/python-testing Skill
0★ repoPython testing workflow skill.
NyXXiR/skillboard/examples/skills/tdd Skill
0★ repoDrive coding tasks through failing-first tests, implementation, and verification.
draculavan/agent-skill-atlas/tests/fixtures/skills/normal-skill Skill
no license0★ repoBuild a small software feature with focused tests and verification.
shaxzodbek-uzb/laravel-guardrails/skills/laravel-pest-testing Skill
0★ repoThis skill should be used when the agent writes or modifies a Laravel feature (controller, route, job, command, policy, model, notification, mail) and needs tests; when it adds or edits files under tests/ or a *Test.php / Pest test file; when it touches Pest.php, phpunit.xml, or a dataset; when it mocks or fakes (Http::fake, Queue::fake, Mail::fake, Mockery, ::shouldReceive); when it asserts on database state, status codes, redirects, jobs, or mail; when it deals with authorization (401/403/404) or time-dependent logic (now(), Carbon, travel, freezeTime); or when the user mentions Pest, "tests", "coverage", "datasets", "arch test", "factory", RefreshDatabase, flaky tests, over-mocking, or "test the happy path". Use it to ship behavior-driven, non-brittle tests that cover the unhappy path and authorization, not just the happy path.
Sarmkadan/dotnet-senior-skills/skills/testing-anti-patterns Skill
0★ repoReview .NET test code for common anti-patterns - mocking DbContext, asserting implementation details, Task.Delay timing, missing cancellation tokens, and brittle assertions. Use when reviewing test PRs or designing test suites.
Sarmkadan/dotnet-senior-skills/skills/testing-strategy Skill
0★ repoDecide what to test at each layer of a .NET service, when integration tests beat unit tests, why mocking DbContext is a smell, and what makes tests worth their maintenance cost. Use when writing tests, reviewing test PRs, or designing a test suite.
bingelp/skills/skills/tdd Skill
no license0★ repoRed-green-refactor discipline for writing new functionality. Use whenever adding new behavior, a new function, or a new feature that can be driven by a test — not just when the user says "TDD".
bingelp/skills/skills/test Skill
no license0★ repoVerifies a completed build against the spec's acceptance criteria. Only runs when the user explicitly types /test.
Pdbjork/hermosskills-site/skills/ce-dogfood-beta Skill
no license0★ repo[BETA] Hands-off end-to-end branch dogfood pass with browser testing, auto-fixes, regression tests, and fix commits.
The same file is in 1 other repository
Pdbjork/hermosskills-site/skills/ce-test-browser Skill
no license0★ repoRun browser tests for pages affected by the current branch or PR.
The same file is in 1 other repository
Pdbjork/hermosskills-site/skills/ce-test-xcode Skill
no license0★ repoBuild and test iOS apps on simulator with XcodeBuildMCP.
The same file is in 1 other repository
Pdbjork/hermosskills-site/skills/ecc-e2e-testing Skill
no license0★ repoPlaywright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.
The same file is in 1 other repository
Pdbjork/hermosskills-site/skills/ecc-tdd-workflow Skill
no license0★ repoUse this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
The same file is in 2 other repositories
Pdbjork/hermosskills-site/skills/static-site-ship Skill
no license0★ repoShip a redesigned (or new) static website end-to-end on a VPS — design the site, build it, validate it, deploy to a static mirror under /var/www or equivalent, smoke-test nginx (with the right Host header) AND the backend capture service, write a handoff report, and ping the user. Load when the user asks to "redesign", "build", "ship", "deploy", or "publish" a website, especially a research/education/foundation/nonprofit public-facing site where privacy-by-default, consent-first forms, and "no false claims" discipline matter. Skip for SPA / SSR app deploys (Next.js, Vite, etc.) — those have their own build pipelines. Skip for hosted-platform-only deploys (Vercel/Netlify/Cloudflare Pages with no VPS mirror).
HeyEddi-com/skills/skills/heyeddi-pr-review Skill
0★ repoReviews submitted PRs using only committed changes: product fit, docs drift, engineering quality, test coverage, and pre-merge gate. Use when approving a PR, doing reviewer QA, or self-checking before requesting review. Not for replying to review comments (use heyeddi-pr-respond).
ZC0325/sol-native-guardrails/plugins/sol-native-guardrails/skills/testing-strategy Skill
0★ repoChoose proportionate tests when the validation approach is a material engineering decision, such as critical behavior, regressions, weak or expensive test harnesses, cross-system integrations, or meaningful tradeoffs between strict test-first, targeted automation, and visual or manual evidence. Do not use for routine changes with an obvious existing test path.
angpysha/api2skill/.agents/skills/api-local-test Skill
0★ repoLocally test a backend API at runtime with mcp2cli — turn any OpenAPI, GraphQL, or MCP endpoint into a CLI (zero codegen, token-efficient). Use to smoke-test a running local server, exercise endpoints against acceptance criteria / API contracts, and verify responses during Phase 7 integration tests and Phase 8 testing.
angpysha/api2skill/.agents/skills/dotnet-unit-tests Skill
0★ repoRun dotnet unit tests with Cobertura coverage and VSTest TRX output for Azure DevOps. Use at Phase 7.5 after writing tests. Produces TestResults/azure-devops-results.json.
jcdavis131/cursor-agent-skills/skills/affected-tests Skill
0★ repoRun only the tests for packages/dirs actually touched by the current change, quiet output, tailed to the last few lines. Use after any code edit where a test suite exists, instead of running the full suite every time. Also: batch independent shell commands in parallel rather than serializing them.
jcdavis131/cursor-agent-skills/skills/smoke-import Skill
0★ repoFast sanity-check that new or edited packages import cleanly, without running a full dependency sync or test suite. Use after creating/editing a Python package's __init__.py, adding a new module to a monorepo, wiring sibling packages, or before wiring a package into a router — any time you want the cheapest possible "did I wire this up" signal.
incuca/incuca-ads/skills/ads-test Skill
0★ repoA/B test design and experiment planning for paid advertising. Structured hypothesis framework, statistical significance calculator, test duration estimator, sample size calculator, and platform-specific experiment setup guides (Meta Experiments, Google Experiments, LinkedIn A/B). Use when user says A/B test, split test, experiment design, test hypothesis, statistical significance, sample size, or test duration.
vaibhavsaxena022/skills/api-testing Skill
0★ repoDesign and organize API tests (Postman/Newman, REST Assured, or similar). Use when building an API test suite or collection, including via an agent driving Postman. Covers structure, assertions, environments, and CI.
vaibhavsaxena022/skills/automation-test-cases Skill
0★ repoDesign UI/API automation test cases that are stable and maintainable. Use when writing or reviewing Selenium / REST Assured / Playwright automation. Covers selector strategy, independence, data handling, and what to automate.
vaibhavsaxena022/skills/junit-test-scaffold Skill
0★ repoGenerate JUnit 5 test skeletons for a Java class or method. Use when asked to add tests, scaffold tests, or improve coverage for Spring/Java code. Produces arrange-act-assert tests with mocked dependencies and edge cases.
vaibhavsaxena022/skills/testing-guidelines Skill
0★ repoWrite tests that are trustworthy and worth maintaining. Use when adding or reviewing tests for your code. Covers what to test, the test pyramid, and the FIRST qualities.
Paldom/landing-page-builder-skills/skills/landing-page-experimentation Skill
0★ repoSets up conversion measurement and A/B testing for a landing page - server/edge variant assignment (no flicker), A/B vs multi-armed bandit, statistical significance, filtering bot/AI traffic, analytics. Use when asked to A/B test, run an experiment, measure conversions, check significance, or set up landing-page analytics. Not for writing copy, page structure, or Core Web Vitals.
SamyakJhaveri/loam/cultivation/marketplace/pocock-engineering/skills/tdd Skill
0★ 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.
SamyakJhaveri/loam/seed/_research/skills/augment-test Skill
0★ repoData augmentation testing workflow. Use when testing a new augmentation transform, diagnosing transform failures on a specific input, or validating transforms against known-good baselines. Runs augmentation pipeline and reports pass/fail per transform.
ats4321/claude-engineering-skills/skills/debugging-playbook Skill
0★ repoSystematic debugging for ANY stack. Auto-load on any bug, test failure, crash, hang, wrong output, flaky behavior, or "why isn't this working". Enforces reproduce → isolate → hypothesize → test ONE variable → verify root cause. Covers reading error messages in full, binary-search isolation (git bisect, commenting out, minimal repro), distinguishing environment vs code vs dependency failures, and recognizing when a framework abstraction is itself the bug (drop to primitives). Trigger keywords: bug, error, exception, traceback, stack trace, crash, hang, fails, broken, "not working", flaky, regression, "worked yesterday", debug, troubleshoot.
ats4321/claude-engineering-skills/skills/evaluation-frameworks Skill
0★ repoMeasure whether an LLM system actually works. Auto-load when building or improving evals, golden sets, or benchmarks for an LLM feature; when comparing prompts, models, or parameters; when someone claims an AI change "seems better"; when calibrating an LLM-as-judge; or before shipping any prompt/model change to an LLM system. An eval is to an LLM system what a test is to code. NOT for writing conventional code tests (validation-and-testing) and NOT for fixing malformed outputs (llm-integration-reliability).
ats4321/claude-engineering-skills/skills/validation-and-testing Skill
0★ repoRisk-first test strategy for ANY codebase. Auto-load when writing tests, adding a runnable check to a change, deciding what to test first, bootstrapping tests into an untested project, or choosing between mocks/fakes/monkeypatch. Covers testing the highest-risk surface first (security boundaries, parsers, money paths), preferring monkeypatch and hand-rolled fakes over mocking libraries, leaving at least one runnable check per non-trivial change, adding a first test to an untested codebase, and knowing when NOT to write a test (trivial one-liners). Trigger keywords: test, testing, pytest, unit test, coverage, mock, monkeypatch, fake, fixture, "add a test", "how do I test", "is this tested".
yousefkadah/laravel-ai-kit/skills/write-test Skill
0★ repoUse when adding or fixing a test in a Laravel project that uses Pest. Covers feature vs unit tests, factories, fixtures, failure-path coverage, and tenant-isolation assertions.
dungsil/skills/skills/writing-java-tests Skill
0★ repoWrite, improve, or review Java tests with JUnit, Mockito, Spring Boot, Spring Data JPA, and JSpecify across unit, integration, and E2E levels. Use only for Java test work, including domain, use-case, entity, validation, repository, adapter, HTTP API, nullability, or Java test-level selection decisions.
dungsil/skills/skills/writing-kotlin-tests Skill
0★ repoWrite, improve, or review Kotlin tests with kotlin-test, MockK, Spring Boot, and Spring Data JPA across unit, integration, and E2E levels. Use only for Kotlin test work, including domain, use-case, entity, validation, repository, adapter, coroutine, HTTP API, nullability, or Kotlin test-level selection decisions.
kulapoo/opencode-agent-harness/.opencode/skills/test-driven-development Skill
0★ repoDrives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
srfinch17/peckworks-skills-laboratory/skills/sandwich-test Skill
0★ repoUse when a received instruction admits more than one plausible reading - quantifier-heavy or idiomatic asks ("clean up", "everywhere", "any", "old", "tidy", "fix the tests", "make it work"), outcome-only phrasing with no method - or when a plausible misreading would be destructive, irreversible, or externally visible; also use when asked to "sandwich-test" a written instruction artifact (plan, prompt, doc, rule) that an LLM will later execute without its author present.
DevOtts/review-it/plugins/review-it/skills/review-it Skill
0★ repoThe QA front door of the DevOtts lifecycle family \u2014 plan-it plans, build-it builds, /review-it verifies. PRIMARY mission: run the unit tests, e2e tests and test-cases generated at plan phase to prove the build obeys the plan \u2014 the independent verification leg of the plan\u2192build\u2192review triangle. Also verifies third-party side-effects (the Airtable class), staging/prod deploys (deployed-code ladder + [REAL] re-runs), and runs a severity-tiered PR review. Routes execution to full-qa, iterate, chrome-cdp-control, make-eval and parallel-lifecycle \u2014 never re-implements them \u2014 and enforces an 11-rule gate catalog that makes false-VERIFIED claims un-shippable. Invoked with no Test Contract it never refuses and never self-grades \u2014 it runs the no-contract ladder and tags every verdict AUTHORED or DERIVED. Use when the user says "/review-it", "review it", "verify the build", "run the test contract", "QA this feature", "verify this deploy", "review this PR", or when build-it reaches its QA phase.
ceilidhboy/skills/skills/pest-testing-conventions Skill
0★ repoPest 4 testing conventions, workflows, and troubleshooting for Laravel projects. Activates when writing or debugging tests, working with browser/smoke/architecture tests, handling test output issues (PAO mode, crash diagnostics), setting up datasets or mocking, and following project conventions for assertions, higher-order expectations, and test organization.
ceilidhboy/skills/skills/tdd-laravel Skill
0★ repoTest-driven development with red-green-refactor loop using Pest PHP. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, asks for test-first development, or needs guidance on writing testable code with Pest.
Cocos creator scene less test bootstrap
ChrisLamDev/cocos-creator-debug-skills/skills/cocos-creator-scene-less-test-bootstrap Skill
0★ repoUse when creating a runtime test without a .scene file in Cocos Creator 3.x. triggers: - scene less - no scene - test without scene
ChrisLamDev/cocos-creator-debug-skills/skills/cocos-standalone-test Skill
0★ repoUse when testing Cocos Creator code as a standalone HTML without the IDE. triggers: - cocos test - standalone test - cocos preview
Syo-M/codex-frontend-skills/.agents/skills/storybook Skill
0★ repoStorybook CSF3 stories, play functions, decorators, and component behavior tests. Use for stories or component-test requests. 日本語の依頼例:「Storybook」「ストーリーを書く」「コンポーネントテスト」「play関数」。
Syo-M/codex-frontend-skills/.agents/skills/testing-playwright Skill
0★ repoPlaywright E2E tests, locators, web-first assertions, isolation, network stubbing, and flake prevention. 日本語の依頼例:「E2Eテスト」「Playwright」「ブラウザテスト」「flakyを直す」。
Syo-M/codex-frontend-skills/.agents/skills/testing-vitest Skill
0★ repoVitest tests for pure logic and headless hooks/providers, plus config, MSW, mocks, and timers. Not for Storybook-owned visible behavior or Playwright journeys. 日本語の依頼例:「ユニットテスト」「Vitest」「モック」「ロジックのテスト」。
Syo-M/codex-frontend-skills/.agents/skills/visual-regression Skill
0★ repoVisual regression testing with Storybook or Playwright screenshots, deterministic baselines, and diff review. 日本語の依頼例:「スクショテスト」「ビジュアルリグレッション」「見た目の差分」「Chromatic」。
Syo-M/codex-frontend-skills/plugins/codex-frontend-skills/skills/storybook Skill
0★ repoStorybook CSF3 stories, play functions, decorators, and component behavior tests. Use for stories or component-test requests. 日本語の依頼例:「Storybook」「ストーリーを書く」「コンポーネントテスト」「play関数」。
Syo-M/codex-frontend-skills/plugins/codex-frontend-skills/skills/testing-playwright Skill
0★ repoPlaywright E2E tests, locators, web-first assertions, isolation, network stubbing, and flake prevention. 日本語の依頼例:「E2Eテスト」「Playwright」「ブラウザテスト」「flakyを直す」。
Syo-M/codex-frontend-skills/plugins/codex-frontend-skills/skills/testing-vitest Skill
0★ repoVitest tests for pure logic and headless hooks/providers, plus config, MSW, mocks, and timers. Not for Storybook-owned visible behavior or Playwright journeys. 日本語の依頼例:「ユニットテスト」「Vitest」「モック」「ロジックのテスト」。
Syo-M/codex-frontend-skills/plugins/codex-frontend-skills/skills/visual-regression Skill
0★ repoVisual regression testing with Storybook or Playwright screenshots, deterministic baselines, and diff review. 日本語の依頼例:「スクショテスト」「ビジュアルリグレッション」「見た目の差分」「Chromatic」。
cat2000/domain-knowledge-ops/.cursor/skills/ticket-test-design Skill
0★ repoDesign release-confidence test cases for one Jira story: must/should/later cut, AC traceability, ISTQB technique selection without checklist theater. Triggers: @ticket-test-design, Jira key, pasted AC, brief, mode=analysis, focus=security, or after @requirement-risk / @ticket-splitter on the same key. Reads domain briefs as evidence only; does not write curated.
IcodeNet/agent-skills/skills/diagnose Skill
0★ repoDisciplined diagnosis loop for hard bugs — intermittent, non-deterministic, environment-dependent, or performance regressions — where the first step is constructing a reliable feedback loop. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when the user says "diagnose this", when a bug resists a simple repro, is flaky or timing-dependent, or when a performance regression needs measurement. For deterministic failures with a clear signal (failing test, build break, readable stack trace), use debug instead.
IcodeNet/agent-skills/skills/tdd Skill
0★ 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.
IcodeNet/agent-skills/skills/testing-strategy Skill
0★ repoDesigns test coverage plans and verification gates. Use when writing tests, planning coverage, asking how to test a change, or designing a test plan before implementation. Do not use for red-green-refactor implementation loops (use tdd) or stop-the-line failure triage (use debug).
shinzoxD/knackbox/skills/coding/load-test-planning Skill
0★ repoPlan and interpret load tests with clear goals, scenarios, and pass/fail criteria. Use whenever the user asks for k6, Locust, JMeter, Gatling, soak tests, stress tests, capacity tests, or how to read p95 latency and error rates under load.
shinzoxD/knackbox/skills/coding/test-generation Skill
0★ repoDesign and write focused automated tests for new code, bug fixes, and risky behavior. Use whenever the user asks for tests, shares untested code, fixes a defect that needs regression coverage, mentions coverage gaps, or wants help deciding what to test, even if they do not name a testing framework.