Find the best CLAUDE.md, AGENTS.md and Claude skills

SupabaseSkill

studio-testing

supabase/supabase/.agents/skills/studio-testing/SKILL.md

Testing strategy for Supabase Studio. Use when writing tests, deciding

jpoehneltSkill

eng-testing

jpoehnelt/skills/eng-testing/SKILL.md

Decide whether a change needs a test, where it lives, what it asserts, and which check to run before calling it done. Use when adding, moving, or reviewing a unit, component, integration, story, or end-to-end test, or choosing the smallest check to run before a PR.

amdReads credentialsSkill

gaia-testing

amd/gaia/.claude/skills/gaia-testing/SKILL.md

GAIA's multi-tier regression harness — runs unit, integration, and real-world (on-machine) tiers and brings back screenshots, logs, traces, planted-fact retrieval proof, and per-operation timing with anomaly flags, all collected to the local machine (no remote login needed to view). It carries GAIA's drivers (Agent UI, Agent UI MCP), exact commands, ports, and `gaia eval agent` baselines, and extends (does not replace) the generic `testing` skill. Fires when the user wants real-world / on-hardware proof, screenshots, or end-to-end evidence that a feature, agent, change, fix, or release actually works — not a quick 'is the app running' check (the `verify` skill) or an LLM-behaviour scorecard alone (`gaia eval agent`). Scales: 'run the unit tests' stays unit-only and skips the planning gate; 'test / validate / QA this feature or release' runs all applicable tiers with evidence.

No other project uses it yet

adezeSkill

mcp-testing

adeze/raindrop-mcp/.github/skills/mcp-testing/SKILL.md

MCP Testing Strategies with Vitest, Inspector, and Integration Tests

sgl-projectSkill

write-sglang-test

sgl-project/sglang/.agents/skills/write-sglang-test/SKILL.md

Guide for writing SGLang CI/UT tests. Covers CustomTestCase, CI registration, which tier (base, extra, nightly, weekly) and runner a test belongs to, server fixtures, model selection, mock testing, and test placement. Always read test/README.md for the full CI layout, how to run tests, and extra tips. Use when creating new tests, adding CI test cases, writing unit tests, moving a test between tiers, or when the user asks to add tests for SGLang features.

IntegralistSkill

go-testing

Integralist/agent-skills/.agents/skills/go-testing/SKILL.md

Write unit and integration tests for Go services. Use when creating, editing, or updating tests, test helpers, mocks, fuzz tests, or benchmarks in Go projects.

ncklrsSkill

ab-testing

ncklrs/claude-chrome-user-testing/skills/ab-testing/SKILL.md

Testing Skill Compare two URL variants with the same persona to determine which provides a better user experience. This skill guides the comparison logic and report generation. ## When

Often used withfree-tools·marketing-council·emails

GoogleSkill

dev-testing

google/capsem/skills/dev-testing/SKILL.md

Capsem testing policy and workflow. Use whenever running or writing tests. For VM, hypervisor, frontend, or Python specifics see the dev-testing-* skills.

Strategic-AutomationSkill

api-testing

Strategic-Automation/violin/skills/api-testing/SKILL.md

Test REST, GraphQL, SOAP, and WebSocket API surfaces.

TypeCellOSSkill

testing-skill

TypeCellOS/BlockNote/.claude/skills/testing-skill/SKILL.md

Instructions for writing, running, and updating unit/end-to-end tests. Should be used when prompted specifically to add tests for a given feature, bug, or regression.

theexperiencecompanySkill

accurate-testing

theexperiencecompany/gaia/.agents/skills/accurate-testing/SKILL.md

Write adversarial test cases that break production code instead of producing false confidence. Use when writing, reviewing, or planning tests for any codebase. Triggers on: "write tests", "add test coverage", "test this function", "create unit tests", "integration tests", "fix flaky tests", "improve test coverage", "review test quality", "are these tests good", "test plan", "break this code", "find edge cases", or any task involving pytest, vitest, jest, or other test frameworks. Enforces the prime directive — a test that cannot fail is not a test — and prevents common AI testing pitfalls: over-mocking, testing frameworks instead of production code, fake implementations that bypass real logic, and assertion-free tests.

lichtblick-suiteSkill

unit-testing

lichtblick-suite/lichtblick/.github/skills/unit-testing/SKILL.md

Unit testing patterns, mock builder usage, and test data construction strategies for the Lichtblick monorepo.

MicrosoftSkill

code-testing

microsoft/testfx/.agents/skills/code-testing/SKILL.md

ALWAYS USE for test work that requires changes: write, add, generate, repair, or strengthen tests for existing code in xUnit, MSTest, NUnit, pytest, Vitest/Jest, Go, or another framework. Includes regression cases, failing or flaky tests, coverage-driven additions, and audit-then-fix requests. Focused work stays direct; broad or multi-stage work invokes test-engineer. DO NOT USE for only running tests, analysis-only audits, framework/platform migrations, a test blocked on a missing production seam (testability-obstacle), or MSTest API/configuration corrections that do not design new cases (writing-mstest-tests). Within an active test-engineer pipeline, reuse supplied guidance and do not re-enter this skill.

javierbreaSkill

unit-testing

javierbrea/eslint-plugin-boundaries/.agents/skills/unit-testing/SKILL.md

Complete or maximize unit test coverage for a specific TypeScript file in this repo. Use when: a test run is short of the 100% coverage threshold and you need to find and close the gap, or when deciding whether an uncovered branch is genuinely unreachable. For everyday test-writing conventions (AAA, mocking, placement, type safety), see .agents/rules/unit-testing.md instead — it loads automatically for any *.spec.ts file.

AllThingsSmittySkill

ts-testing

AllThingsSmitty/proven-skills/skills/ts-testing/SKILL.md

TypeScript testing advisor. Always use this skill when writing tests in TypeScript, setting up Jest or Vitest with TypeScript, creating type-safe mocks, or writing type-level tests. Use when the user asks "how do I mock this in TypeScript", "my mock has the wrong type", "how do I test that a type is correct", "jest.fn doesn't match my interface", "how do I set up Jest with TypeScript", "how do I avoid as any in tests", or "how do I write a type-level test". Read this skill before writing any TypeScript tests or mocks.

baturSkill

ts-testing

batur/ts-baseline-docs/.agents/skills/ts-testing/SKILL.md

Defines the TypeScript testing standard for AI coding and review. Use when adding, changing, or reviewing tests, test structure, Vitest, Playwright e2e, validation/error/PATCH/auth/security/tenant tests, fixtures, mocks/fakes, coverage, CI test commands, or any behavior that needs test protection.

feast-devSkill

feast-testing

feast-dev/feast/skills/feast-testing/SKILL.md

How to test and debug Feast — running targeted tests, writing unit tests for new components, debugging registry and online store issues, and inspecting live feature store state. Use when writing tests for a new feature, debugging a failing test, investigating a runtime error, or verifying that a change works correctly end-to-end.

No other project uses it yet

ngocsangyemSkill

mk:testing

ngocsangyem/MeowKit/.claude/skills/testing/SKILL.md

Use when writing tests, running validation scripts, or (in TDD mode) enforcing red-green-refactor cycle. Activates during Phase 2 (Test) and Phase 3 (Build). NOT for coverage gap mapping (see mk:nyquist); NOT for sprint contract negotiation (see mk:sprint-contract).

jabrenaSkill

321-frameworks-spring-boot-testing-unit-tests

jabrena/cursor-rules-java/skills/321-frameworks-spring-boot-testing-unit-tests/SKILL.md

Use when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test profiles, and @TestConfiguration. For framework-agnostic Java use @131-java-testing-unit-testing. For integration tests use @322-frameworks-spring-boot-testing-integration-tests. This should trigger for requests such as Review Java code for Spring Boot unit tests; Apply best practices for Spring Boot unit tests in Java code; Write Mockito-first unit tests for Spring Boot services; Avoid unnecessary @SpringBootTest in Spring unit tests; Review Spring Boot slice-free unit test design. Part of Plinth Toolkit

starkware-libsSkill

writing-tests

starkware-libs/cairo/.claude/skills/writing-tests/SKILL.md

Use when writing or changing tests in this repo, deciding what to test or where a test belongs, adding a regression test for a bug fix, reviewing the test portion of a PR, deciding which golden outputs to bless and reviewing the blessed diff, or adding a benchmark. Trigger phrases include "add a test", "write tests for", "is this covered", "does this need a test", "review the tests here", "which layer should this test go in". Also use for the mechanics of the golden framework itself — the //! > file format, creating test_file_test! runners, or how CAIRO_FIX_TESTS works (covered in references/golden-framework.md).