Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
EvilFreelancerSkillEvilFreelancer/secs/.agents/skills/testing-apis/SKILL.md
Test REST and GraphQL APIs for authentication bypasses, authorization flaws, IDOR, mass assignment, injection attacks, and rate limiting issues. Use when pentesting APIs or testing microservices security.
MicrosoftSkillmicrosoft/Employee-Self-Service-Agent-Developer-Kit/solutions/ess-maker-skills/src/skills/topics/test/SKILL.md
Test / Debug Topic Skill Guides a maker through debugging a topic they just created or updated — driving it, confirming the reply is real, checking the fix doesn't break
MicrosoftSkillmicrosoft/Employee-Self-Service-Agent-Developer-Kit/solutions/ess-maker-skills/src/skills/workflows/test/SKILL.md
Test Workflow Skill Guides a maker through debugging a Power Automate cloud flow (workflow) behind their agent — exercising it, reading its per-action run history, localizing a fault
Significant-GravitasSkillSignificant-Gravitas/AutoGPT/.claude/skills/pr-test/SKILL.md
E2E manual testing of PRs/branches using docker compose, agent-browser, and API calls. TRIGGER when user asks to manually test a PR, test a feature end-to-end, or run integration tests against a running system.
AndrewDrygaSkillAndrewDryga/emisar/.claude/skills/elixir-testing/SKILL.md
Write or improve ExUnit tests for portal/ the emisar way — DataCase/ConnCase, the real fixtures in test/support, and the mandatory happy / denial / cross-account paths (§7). Use when adding tests for a context/job/LiveView, or when a change is missing its denial + cross-account coverage.
SentrySkillgetsentry/sentry/.agents/skills/generate-snapshot-tests/SKILL.md
Generate snapshot test files for Sentry frontend React components. Use when asked to "generate snapshot tests", "add snapshot tests", "create visual snapshots", "write snapshot tests", "add visual regression tests", or "snapshot this component". Accepts an optional component path or name via $ARGUMENTS.
iamcaominhtienSkilliamcaominhtien/kanban-board-mcp/.github/skills/unit-testing/SKILL.md
Unit testing & component testing skill for any language or framework. Use when: writing tests, setting up a test suite, thinking about what to test, applying TDD, testing a React component, testing a Python/Node.js backend, mocking dependencies, checking test coverage, understanding unit vs component vs integration tests. Triggers: 'write a test', 'add tests for', 'unit test this', 'component test', 'test this function', 'how do I test', 'TDD', 'what should I test', 'set up vitest', 'set up pytest', 'test coverage', 'mock this', 'I don't know how to test this'.
Prompthon-IOSkillPrompthon-IO/agent-systems-handbook/skills/webapp-testing/SKILL.md
Verify a local web app in a real browser with page, element, click, form, console and screenshot evidence. Use after a build or UI change; do not implement features or publish deployments with this skill.
MicrosoftSkillmicrosoft/testfx/.agents/skills/writing-mstest-tests/SKILL.md
Write new MSTest unit tests and fix existing MSTest code using MSTest 3.x/4.x modern APIs and best practices. USE FOR: write or create MSTest unit tests, fix or modernize MSTest assertions, better MSTest assertion than Assert.IsTrue, replace hard cast with MSTest type assertion, MSTest assertion APIs (IsInstanceOfType, Contains, ContainsSingle, HasCount, IsEmpty, IsNotEmpty, DoesNotContain, StartsWith, EndsWith, MatchesRegex, IsGreaterThan, IsInRange, IsNull), fix swapped Assert.AreEqual arguments, replace ExpectedException with Assert.Throws, data-driven tests (DataRow, DynamicData, ValueTuples), test lifecycle (sealed classes, TestInitialize, TestCleanup), async tests and cancellation tokens, test parallelization (Parallelize / DoNotParallelize), MSTest.Sdk project setup. DO NOT USE FOR: broad test quality audits (use test-anti-patterns), running tests (use run-tests), MSTest version migration (use migrate-mstest-v1v2-to-v3 or migrate-mstest-v3-to-v4), xUnit/NUnit/TUnit, or non-.NET languages.
happier-devSkillhappier-dev/happier/.agents/skills/happier-testing/SKILL.md
Repo-specific TDD and test-validation workflow for Happier changes, with lane selection, fixture policy, and anti-flake guardrails.
Prorise-coolSkillProrise-cool/Claude-Code-Multi-Agent/.claude/skills/webapp-testing/SKILL.md
使用 Playwright 与本地 Web 应用程序交互和测试的工具包。支持验证前端功能、调试 UI 行为、捕获浏览器截图和查看浏览器日志。
vasceannieSkillvasceannie/slopgate/.claude/skills/slopgate-test-extender/SKILL.md
Extend Python test suites with parametrization, fixture reuse, and quality enforcement. Use when asked to add tests, extend existing tests, improve test coverage, consolidate duplicate tests, fix test quality issues, or when Slopgate reports untested-production-code, missing test references, or coverage gaps. Triggers on requests like "add tests for X", "extend these tests", "parametrize tests", "consolidate tests", "fix test quality", "improve test coverage", "write tests for this function", "test this module", "behavior tests", "integration tests", "missing tests", "coverage holes", "untested code", or when a hook denies with test-related findings.
MADTeacherSkillMADTeacher/mad-agents-skills/flutter-testing/SKILL.md
Write, fix, review, debug, and validate Flutter tests for apps, packages, and plugins. Use when adding unit tests, widget tests, integration tests, MethodChannel or plugin mocks, Mockito or mocktail test doubles, golden or accessibility checks, CI test commands, test failures, MissingPluginException, pump or pumpAndSettle problems, finder errors, build_runner mock generation, device integration testing, web integration testing, or flaky Flutter tests.
osteelSkillosteel/agent-skills/test-audit/SKILL.md
Audit the existing test suite for structural and quality issues — wrong-layer tests, redundant browser tests, infrastructure overuse, flaky/unreliable patterns, rotted skipped tests, unclear test names, dataset opportunities, duplicate tests, folder drift — then fix the approved issues. Use when the user says things like "audit the tests", "review the test suite", "our tests are slow", "our tests are flaky", "improve test distribution", "too many end-to-end tests", "tests are taking too long", "are our tests in the right layer", or "clean up the test suite". Also invoke proactively after a major feature milestone when the suite has grown significantly. Distinct from `cover` (which adds tests for recent code changes) — this skill audits what's already there and never adds net-new tests for uncovered code. Use the `test` skill to run the suite during the baseline and verification phases.
hideki5123Skillhideki5123/agent-skill-set/orch-qa/SKILL.md
Senior QA/QC engineer that evaluates existing codebases for test quality. Runs existing tests, diagnoses failures, identifies missing test coverage, and writes missing tests. Framework-agnostic — works with any language and test runner. Use when the user asks to run tests, diagnose failures, do test gap analysis, QA, quality assurance, test coverage analysis, find missing tests, test audit, quality check, quality report, fix failing tests, evaluate test quality, or assess test health of a codebase. Trigger phrases include "run tests", "QA", "quality assurance", "test audit", "test coverage", "missing tests", "gap analysis", "quality report", "fix failing tests", "diagnose test failures", "quality check", "evaluate test quality", "test health".
loulanyueSkillloulanyue/awesome-claude-notes/skills/kotlin-testing/SKILL.md
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
loulanyueSkillloulanyue/awesome-claude-notes/skills/python-testing/SKILL.md
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.
MindrallySkillMindrally/skills/python-testing/SKILL.md
Expert in Python testing with pytest and test-driven development
devpilotXSkilldevpilotX/skills/skills/test-strategy/SKILL.md
Decide what deserves a test and write tests that fail for the right reason. Use when the user asks what or how to test, asks about unit, integration or end to end tests, test coverage, mocking, fixtures, flaky tests, test driven development, snapshot tests or contract tests, asks why their tests pass while production breaks, or asks how to add tests to code that has none. Allocates effort by what a failure costs rather than by a coverage target, tests behaviour instead of implementation so refactoring does not break the suite, makes flakiness a defect rather than a retry, and states plainly that coverage percentage measures execution rather than correctness. Triggers on what should I test, how do I test, unit tests, integration tests, end to end tests, test coverage, mocking, flaky tests, TDD, snapshot tests, my tests pass but production breaks, add tests to legacy code.
PIXARTSeuSkillPIXARTSeu/Synapse/.agents/skills/test-master/SKILL.md
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.
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.
