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

Rain-klSkill

go-testing

Rain-kl/OpenFlare/.agents/skills/go-testing/SKILL.md

Use when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff. Also use when a user asks to write a test for a Go function, even if they don't mention specific patterns like table-driven tests or subtests. Does not cover benchmark performance testing (see go-performance).

fzyzcjySkill

tms-testing

fzyzcjy/torch_memory_saver/.claude/skills/tms-testing/SKILL.md

Use when running ordinary torch_memory_saver regression tests or the full CUDA wheel runtime matrix.

manaflow-aiSkill

cmux-testing

manaflow-ai/cmux/skills/cmux-testing/SKILL.md

Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.

Feel-ix-343Pipes a download into a shellSkill

testing-zed

Feel-ix-343/markdown-oxide/.agents/skills/testing-zed/SKILL.md

Test markdown-oxide LSP features in Zed

zapekSkill

ui-testing

zapek/Xeres/.agents/skills/ui-testing/SKILL.md

TestFX patterns for JavaFX controller testing in Xeres including FXML loading with controller factories, mocking reactive clients, and user interaction testing.

mrgoonieSkill

web-testing

mrgoonie/claudekit-skills/.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.

SentrySkill

write-tests

getsentry/sentry-javascript/.agents/skills/write-tests/SKILL.md

Write high-quality unit tests (Vitest) and E2E tests (Playwright) following senior test-engineering practices. Use this skill whenever asked to write tests, add test coverage, create test cases, fix failing tests, add missing assertions, test a new feature, write specs, or cover edge cases. Also trigger when the user says "write tests for", "add tests", "test this", "cover this", "needs tests", "add E2E test", "add unit test", "test coverage", or when reviewing code and noticing missing test coverage.

Often used withclose-spec·compare-screenshots·audit-agents

xu-xiangReads credentialsSkill

e2e-testing

xu-xiang/everything-claude-code-zh/.agents/skills/e2e-testing/SKILL.md

Playwright E2E 测试模式、页面对象模型（POM）、配置、CI/CD 集成、产物管理以及不稳定测试（flaky test）策略。

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

CesarjoquinSkill

ab-testing

Cesarjoquin/Marketing-Skills/skills/ab-testing/SKILL.md

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

Often used withmarketing-council·emails·prospecting

dotnetSkill

evaluate-pr-tests

dotnet/maui/.github/skills/evaluate-pr-tests/SKILL.md

Evaluates tests added in a PR for coverage, quality, edge cases, and test type appropriateness. Checks if tests cover the fix, finds gaps, and recommends lighter test types when possible. Prefer unit tests over device tests over UI tests. Triggers on: 'evaluate tests in PR', 'review test quality', 'are these tests good enough', 'check test coverage', 'is this test adequate', 'assess test coverage for PR'.

codeaholicguySkill

dev-testing

codeaholicguy/ai-devkit/skills/dev-testing/SKILL.md

AI DevKit · Testing phase guidance for adding and validating feature test coverage. Use when the user wants to write tests, update testing docs, run coverage, close coverage gaps, or run dev-lifecycle phase 8.

johnlindquistSkill

ts-testing

johnlindquist/claude-workshop-skills/skills/ts-testing/SKILL.md

Design, implement, and maintain high‑value TypeScript test suites using popular JS/TS testing libraries. Use this skill whenever the user is adding tests, debugging failing tests, or refactoring code that should be covered by tests.

vellum-aiReads credentialsSkill

cli-testing

vellum-ai/vellum-assistant/.claude/skills/cli-testing/SKILL.md

Manually test a running Vellum assistant end-to-end purely from the CLI — no desktop app or web UI. Hatch an instance, send messages, watch the reply, and tear it down. Use when verifying assistant behavior, reproducing a bug, or smoke-testing a change without the macOS/web clients.

paradigmxyzSkill

e2e-testing

paradigmxyz/centaur/.agents/skills/e2e-testing/SKILL.md

Write, run, and debug Centaur's end-to-end tests under e2e/. Use when adding or changing an e2e scenario, running the e2e stack locally, or investigating a failing e2e CI job.

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

L-X-TSkill

ng-testing

L-X-T/ng-agentic-skills/.agents/skills/ng-testing/SKILL.md

Write Vitest unit and component tests for Angular – TestBed for standalone + zoneless components, signal/computed assertions, DI and HttpClient mocking, and CDK component harnesses. Use when the user wants to unit-test or spec a component, service, pipe, signal, or computed, mentions Vitest, TestBed, HttpTestingController, or component harnesses, or says "test this component/service". Not for browser end-to-end tests – use create-e2e-tests.

championswimmerSkill

ui-testing

championswimmer/TwoFac/.agents/skills/ui-testing/SKILL.md

How to run, write, and debug local UI tests for Android, iOS, and browser builds.

filamentphpSkill

pest-testing

filamentphp/demo/.claude/skills/pest-testing/SKILL.md

Tests applications using the Pest 3 PHP framework. Activates when writing tests, creating unit or feature tests, adding assertions, testing Livewire components, architecture testing, debugging test failures, working with datasets or mocking; or when the user mentions test, spec, TDD, expects, assertion, coverage, or needs to verify functionality works.

whisper-moneySkill

pest-testing

whisper-money/whisper-money/.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, architecture tests, or faster test runs with Test Impact Analysis. Covers: test()/it()/expect() syntax, datasets, mocking, browser testing (visit/click/fill), smoke testing, arch(), Livewire component tests, RefreshDatabase, Tia (--tia), sharding, and all Pest 5 features. Do not use for factories, seeders, migrations, controllers, models, or non-test PHP code.

whisper-moneySkill

pest-testing

whisper-money/whisper-money/.cursor/skills/pest-testing/SKILL.md

Tests applications using the Pest 4 PHP framework. Activates when writing tests, creating unit or feature tests, adding assertions, testing Livewire components, browser testing, debugging test failures, working with datasets or mocking; or when the user mentions test, spec, TDD, expects, assertion, coverage, or needs to verify functionality works.

whisper-moneySkill

pest-testing

whisper-money/whisper-money/.github/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: 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.