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

JetBrainsSkill

build-tools-add-test-federation-annotations-to-integration-tests

JetBrains/kotlin/.claude/skills/build-tools-add-test-federation-annotations-to-integration-tests/SKILL.md

Annotate test classes in `kotlin-gradle-plugin-integration-tests` with Test Federation annotations (`@MustRunOnChangesInXYZ` / `@MustRunAlways`). Use this whenever the user asks to annotate, review, or fix Test Federation annotations on an integration test class, or to assess a test class for cross-domain dependencies under Test Federation (KT-87614).

loulanyueSkill

cpp-testing

loulanyue/awesome-claude-notes/skills/cpp-testing/SKILL.md

Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.

loulanyueReads credentialsSkill

e2e-testing

loulanyue/awesome-claude-notes/skills/e2e-testing/SKILL.md

Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

Often used witheverything-claude-code·everything-claude-code-conventions·bun-runtime

MaterializeIncSkill

mz-test

MaterializeInc/materialize/.agents/skills/mz-test/SKILL.md

Run tests + pick test framework in Materialize. Trigger: "run tests", "run testdrive", "run sqllogictest", "run mzcompose", "run cargo test", "run pgtest", "rewrite test results", "add a test", "reproduce a bug", "write a regression test", or mentions testing, testdrive, sqllogictest, mzcompose, pgtest, cargo test, nextest, flaky tests, test failures. Also "test this" or "how do I verify this works". Specifics: mz-platform-checks (upgrade/restart survival), mz-parallel-workload (concurrent stress), mz-limits-test (many objects).

idavidov13Reads credentialsSkill

api-testing

idavidov13/agentic-playwright/.agents/skills/api-testing/SKILL.md

Use when writing or updating an API spec under tests/**/api/**, planning coverage for an endpoint, building a response schema from the API contract, or deciding whether API setup/teardown becomes a helper fixture. Not for Zod syntax and type inference (see `type-safety`) or fixture mechanics (see `fixtures`).

NVIDIASkill

mcore-testing

NVIDIA/Megatron-LM/skills/mcore-testing/SKILL.md

Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity. Use when adding or running a unit or functional test; understanding the test layout; writing a recipe YAML; downloading or updating golden values; reproducing a test failure locally; 'how do I add a test', 'run unit tests', 'pytest fails', 'test layout', 'golden values', 'recipe YAML', 'marker filter'.

fugaziSkill

api-testing

fugazi/test-automation-skills-agents/skills/api-testing/SKILL.md

Test REST and GraphQL endpoint contracts using Playwright request fixture (TypeScript) or REST Assured (Java). Use for standalone API tests covering schemas, auth, status/error handling, pagination, idempotency, rate limits, or contract checks; not for browser E2E specs. Keywords: REST, GraphQL, API contract, schema validation, REST Assured.

ag2aiReads credentialsSkill

ag2-testing

ag2ai/build-with-ag2/.agents/skills/ag2-testing/SKILL.md

Test AG2 beta agents and tools without hitting a real LLM provider. Pass `TestConfig(...)` from `autogen.beta.testing` as the agent's config (or per-`ask`) to mock LLM responses, inject `ToolCallEvent`s to simulate tool execution, and assert success / error paths. Use when the user is writing pytest tests for an Agent or Tool.

JamieMasonSkill

testing-gaps

JamieMason/syncpack/.claude/skills/testing-gaps/SKILL.md

Run coverage, inspect results, and identify missing test scenarios for a given source file. Use when analysing test coverage or finding untested branches.

No other project uses it yet

bodhiyeSkill

ui-testing

bodhiye/ui-testing/SKILL.md

基于 Chrome DevTools MCP 的零脚本 UI 自动化测试 Skill：输入 URL 自动遍历页面并沉淀/复用 Playbook，执行 E2E 并输出标准化报告（MCP 优先，支持 CDP Proxy 降级）。

felvieiraSkill

qa-testing

felvieira/claude-skills-fv/skills/05-qa-testing/SKILL.md

Skill do QA Engineer para testes unitarios, integracao e E2E. Use quando precisar escrever testes, validar regressao, revisar cobertura, configurar estrategia de QA, ou evidenciar qualidade antes de release. Trigger em: "teste", "test", "QA", "Playwright", "Vitest", "Jest", "E2E", "coverage", "mock", "fixture", "regressao", "teste de integracao", "testing library".

xchacha20-poly1305Skill

husi-testing

xchacha20-poly1305/husi/.agents/skills/husi-testing/SKILL.md

Husi project's testing conventions. Use whenever adding, updating, or debugging tests under composeApp/ — ViewModels, updaters, ktx helpers, anything in commonTest/desktopTest. Also use when a piece of production code needs a DI seam to become testable (HTTP, DataStore, Libcore). Do not reach for mockk first or invent a new base class — consult this skill before writing the first test in a new file.

typvSkill

web-testing

typv/nest-turbo-starter/.claude/skills/web-testing/SKILL.md

Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.

petrkindlmannSkill

api-testing

petrkindlmann/qa-skills/skills/api-testing/SKILL.md

Test REST and GraphQL APIs with Playwright APIRequestContext, Supertest, or standalone HTTP clients. Covers schema validation with Zod 4/AJV, auth flow testing, CRUD lifecycle tests, error and header validation, pagination, and performance assertions. Use when: "API test," "endpoint test," "REST test," "GraphQL test," "schema validation," "Postman replacement." Not for: consumer-driven contract verification (Pact, broker) — use contract-testing; browser UI flows — use playwright-automation. Related: contract-testing, test-data-management, ci-cd-integration, playwright-automation.

Often used withexploratory-testing

SupabaseSkill

studio-testing

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

Testing strategy for Supabase Studio. Use when selecting, writing,

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.

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.