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

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.

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.

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

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.

The-OpenROAD-ProjectSkill

add-test

The-OpenROAD-Project/OpenROAD/.agents/skills/add-test/SKILL.md

Add integration or unit tests to an OpenROAD module. Handles the complete workflow: writing the Tcl/C++ test, generating golden files, and registering the test in Bazel. Use when asked to add tests, improve test coverage, create regression tests, or write unit tests for any OpenROAD module (ant, cts, dpl, drt, gpl, grt, mpl, odb, pad, pdn, psm, rcx, rsz, sta, stt, tap, upf, utl, etc.). Also triggers on: "add test", "write test", "test coverage", "missing tests", "create regression test", "add unit test".

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.