Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
filipefalcaofsSkillfilipefalcaofs/repo-padrao/.claude/skills/pest-testing/SKILL.md
Testes Pest PHP em projetos Laravel — test()/it(), datasets, mocks, browser tests, smoke tests e arch(). Usar ao escrever, corrigir ou refatorar testes em tests/Feature, tests/Unit ou tests/Browser, ou quando o usuário mencionar Pest, TDD ou php artisan test.
LeostrukaSkillLeostruka/devin-bundle/skills/e2e-testing/SKILL.md
Use when the user wants to add, run, or debug end-to-end tests. Covers Playwright, Selenium, Cypress, happy paths, critical user journeys, and CI integration.
lintangknittoSkilllintangknitto/agent-skills/skills/api-testing/SKILL.md
Use when writing or running backend/API tests that hit HTTP endpoints directly (no browser) — REST or GraphQL, via Supertest/Vitest (TS/JS) or httpx/pytest (Python). Decides, per test, whether to use a mock database, a real database with transaction rollback, or a real database hit black-box over HTTP with an explicit teardown script — and never lets test data linger uncleaned. Also covers the case where the flow under test depends on an entity owned by another repo/service (e.g. testing order-cancellation when order-creation lives elsewhere) — this skill stops and asks for that dependency instead of guessing its shape. Not for browser-driven E2E (use webapp-testing/e2e-testing) or React component tests (use react-testing).
sbarbatSkillsbarbat/tentaclesauth/.agents/skills/pest-testing/SKILL.md
Use this skill for Pest PHP testing in Laravel projects only. Trigger whenever any test is being written, edited, fixed, or refactored — including fixing tests that broke after a code change, adding assertions, converting PHPUnit to Pest, adding datasets, and TDD workflows. Always activate when the user asks how to write something in Pest, mentions test files or directories (tests/Feature, tests/Unit, tests/Browser), or needs browser testing, smoke testing multiple pages for JS errors, or architecture tests. Covers: test()/it()/expect() syntax, datasets, mocking, browser testing (visit/click/fill), smoke testing, arch(), Livewire component tests, RefreshDatabase, and all Pest 4 features. Do not use for factories, seeders, migrations, controllers, models, or non-test PHP code.
vishipayyalloreSkillvishipayyallore/practical-ai-agents/.cursor/skills/e2e-testing/SKILL.md
Smoke verification for Practical AI Agents (environment, notebook JSON, optional manual notebook run). Use when smoke-testing the workspace end-to-end.
dovoanhtruongSkilldovoanhtruong/abap-agent-claudecode-workspace/.claude/skills/abap-unit-testing/SKILL.md
Help with ABAP Unit testing — test classes/methods, CL_ABAP_UNIT_ASSERT assertions, test doubles/mocking, dependency injection, CDS/OSQL test environments, RAP BO test doubles, test seams/injection, fixtures, test isolation, TDD in ABAP. Use even for a single quick test ask — "write a unit test", "create test class", "mock a dependency", "test a CDS view", "test a RAP BO", "viết unit test", "tạo test class", "mock dependency", "test method này", "kiểm thử RAP BO".
flonatSkillflonat/flonat-research/skills/webapp-testing/SKILL.md
Exercise and verify a local web application through Playwright, including user flows and rendered behaviour. Use when testing a running local app rather than issuing an isolated browser command. For ad hoc automation, use $playwright-cli.
manaflow-aiSkillmanaflow-ai/cmux/skills/cmux-test-bisect/SKILL.md
Find when and why tests broke on main: bisect a Swift package suite on CI across old commits, read the failure matrix, and decide per test whether the test went stale or the code regressed. Use when a suite is red on main, when PR CI only ran filtered tests and the full suite has drifted, or when asked which PR broke a test.
ElasticSkillelastic/kibana/.agents/skills/scout-api-testing/SKILL.md
Use when creating, updating, debugging, or reviewing Scout API tests in Kibana (apiTest/apiClient/requestAuth/samlAuth/apiServices), including auth choices, response assertions, and API service patterns.
opena2a-orgSkillopena2a-org/hackmyagent/test/SKILL.md
test
bartstcSkillbartstc/vite-ts-react-template/.agents/skills/test-building-blocks/SKILL.md
Test building block catalog — typed patterns for Storybook play-function tests, Vitest hook tests, Vitest unit tests, MSW handlers, and test data fixtures. Read the relevant rule file before writing or modifying any test, handler, or fixture. Covers: deciding which kind of test to write, authoring a new test from scratch, adding MSW mocks or fixtures, and reviewing existing tests for conformance.
JetBrainsSkillJetBrains/intellij-community/.agents/skills/testing-internals/SKILL.md
Debug IntelliJ `tests.cmd` execution, discovery, and runner internals.
JetBrainsSkillJetBrains/intellij-community/.claude/skills/testing-internals/SKILL.md
Debug IntelliJ `tests.cmd` execution, discovery, and runner internals.
MicrosoftSkillmicrosoft/typespec/packages/http-client-python/.github/skills/test-unbranded-emitter/SKILL.md
Build and test the @typespec/http-client-python emitter. Use this skill whenever the user wants to test their local changes to the emitter, run the generator test suite, check if their http-client-python changes are passing, or validate a fix. Triggers on phrases like "test the emitter", "run tests", "check if my changes pass", "run test:generator", "run CI", or any mention of testing/validating changes in the emitter package.
robomotionioSkillrobomotionio/agent-skills/skills/testing-flow/SKILL.md
Runs and authors behavioral tests for Robomotion flows using @robomotion/sdk/testing. Use when the user says "test the flow", "write tests for main.ts", "mock this service", "check branch coverage", or when a flow needs regression tests before a change. For pspec schema validation, use validating-flow instead.
wicttorSkillwicttor/pwrl/pwrl-testing/SKILL.md
Comprehensive testing framework for micro-skill pipeline architecture validation, including unit, integration, compatibility tests, and consolidation audit.
poolcamachoSkillpoolcamacho/sveltekit-testing/SKILL.md
Design, implement, review, and improve the testing strategy of production SvelteKit applications like a senior test engineer. Use this skill whenever the user is setting up tests for a SvelteKit app, asks what to unit test vs integration test vs test end to end, wants a review or "audit" of an existing SvelteKit test suite, asks how to test load functions, form actions, endpoints, authentication, or authorization, mentions flaky tests, slow tests, low or misleading coverage, or a test suite that is hard to maintain, asks about Vitest, Playwright, Vitest browser mode, vitest-browser-svelte, component tests, mocking, fixtures, factories, test databases, or CI test behavior, or asks whether they are testing the right things. Trigger even when the user does not say the word "testing". Questions like "should this be an e2e test?", "how do I test this form action?", "why is this test flaky?", or "is my test suite any good?" all apply. Framework-specific to SvelteKit, not generic frontend testing advice.
edhoferdianSkilledhoferdian/EEF/.agents/skills/test-authoring-edho-ferdian/SKILL.md
Guidance for WRITING unit and component tests well — React/Testing Library, Python/pytest, Go, and Vue, plus stack-agnostic regression-test patterns. A companion to code-review-edho-ferdian's test-quality-lens (which judges tests after they're written) and dev-kickoff-edho-ferdian's TEST stage (which mandates writing a failing test first but doesn't teach test-writing craft). Trigger phrases: "tulis test untuk component ini", "bagaimana test hook ini", "test yang bagus untuk fitur X", "tulis test pytest/Go/Vue untuk ini", or during dev-kickoff's TEST stage when the task needs concrete authoring guidance beyond "write a failing test."
AreevAISkillAreevAI/areev/.claude/skills/areev-testing/SKILL.md
How to test Areev — the test taxonomy (unit / integration / golden / property / fuzz / perf-gate / cross-surface), the determinism rules that keep the suite non-flaky, the golden bless flow, and a combination-coverage checklist for finding bugs at feature interactions. Use when writing or changing tests, adding coverage for a new feature, chasing a flaky or failing test, or hunting for bugs by exercising edge cases and feature combinations.
ariadossSkillariadoss/superskills/skills/test-coverage/SKILL.md
Finds complex business logic, edge cases, corner cases, and past regressions that lack tests, then writes the missing unit tests (and integration/E2E tests when the risk genuinely crosses a boundary) — enforcing Google's Testing on the Toilet best practices (real > fake > mock, don't mock types you don't own, verify state not queries, avoid change-detector tests, DAMP over DRY in tests, limit mocks per test). Use when asked to "add tests", "cover edge cases", "check test coverage", "write missing tests", "harden the tests", "test this properly", or "make sure this is tested".
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.
