Claude skills and agent skills

fullstackheroSkill

testing-guide

fullstackhero/dotnet-starter-kit/.agents/skills/testing-guide/SKILL.md

Write tests for an FSH feature — xUnit + Shouldly + NSubstitute + AutoFixture, with naming and AAA conventions. Use when adding unit/handler/validator/entity tests. Full rules in .agents/rules/testing.md + integration-testing.md.

amElnagdySkill

test-guard

amElnagdy/guard-skills/skills/test-guard/SKILL.md

Review generated or changed test code against universal testing rules before it ships. Best used reactively after an agent writes, edits, generates, or refactors tests, before presenting, committing, or merging them. Use for pytest (test_*.py, *_test.py), PHPUnit/Pest (*Test.php), Jest/Vitest (*.test.ts, *.spec.js), Go (*_test.go), files under tests/, __tests__/, or spec/, and review requests like 'write tests for X', 'add tests', 'test this', 'review these tests', or PR diffs containing tests. Can also guide test writing when explicitly invoked before the work. This skill is the quality gate that prevents AI-generated test bloat. DO NOT USE for production or implementation code review (use clean-code-guard), CI or test-runner configuration, running or debugging tests, or general architecture discussion.

cohen-lielReads credentialsSkill

e2e-testing

cohen-liel/hivemind/.claude/skills/e2e-testing/SKILL.md

End-to-end testing patterns with Playwright. Use when writing browser automation tests, integration tests, testing user flows, or setting up E2E test suites.

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

MRCalderon3DSkill

web-testing

MRCalderon3D/everything-game-dev-code/skills/web/web-testing/SKILL.md

Test browser games with fast unit tests for pure logic, headless smoke tests, and a deliberate browser matrix.

TangleMLSkill

e2e-testing

TangleML/tangle-ui/.claude/skills/e2e-testing/SKILL.md

Playwright E2E testing best practices for this project. Use when writing, modifying, or reviewing E2E tests.

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

rommappSkill

ui-ux-testing

rommapp/argosy-launcher/.claude/skills/ui-ux-testing/SKILL.md

Drive the running app on an Android emulator and visually verify UI/UX by capturing screenshots and reading them back. Use to confirm a screen renders, navigate a flow (e.g. first-run/quickstart), check dual-modality input, or catch visual regressions. Knows the technical limits of emulator testing and when the device is still the final authority.

GitHubSkill

webapp-testing

github/awesome-copilot/skills/webapp-testing/SKILL.md

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Often used withacademy-guide·skill-share·intelligent-routing

mturacReads credentialsSkill

e2e-testing

mturac/everything-openai-codex/.agents/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

karmabReads credentialsSkill

kcli-testing

karmab/kcli/skills/kcli-testing/SKILL.md

Guides testing and code quality for kcli. Use when writing tests, running linting, or validating changes before committing.

petrkindlmannReads credentialsSkill

payment-testing

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

Test payment and checkout flows end to end against PSP sandboxes — Stripe first, with the general pattern for Adyen/Braintree/PayPal. Covers Stripe test-mode card numbers and their decline codes, the 3DS/SCA challenge flow and its nested-iframe handling in Playwright, test clocks for subscription/billing-cycle simulation, webhook testing (stripe listen/trigger, signature verification, idempotency), failed/retried payments and refunds, and never using real cards. Use when: "test Stripe checkout," "payment test," "3DS test," "test webhook signature," "test subscription renewal," "test clock," "refund test," "decline card test," "checkout E2E." Not for: General API contract testing of non-payment endpoints — api-testing. PCI-DSS/regulatory compliance audit — compliance-testing. Related: api-testing, playwright-automation, compliance-testing, test-data-management, qa-project-context.

UI5Skill

run-test

UI5/openui5/.claude/skills/run-test/SKILL.md

Run QUnit and OPA tests for OpenUI5 modules via headless Chrome. This is the ONLY way to run tests — never use karma, npm test, or browser MCP tools. Use whenever tests need execution: run tests, run unit tests, check tests pass, verify my change, do the tests still pass, run QUnit, run OPA, execute test suite, test this module, test Button/Router/Table/Dialog/MessageBox/Input/Control, run journey, check regressions. Even if the user does not say "test" explicitly but wants to verify a code change works, use this skill.

brainbytes-devSkill

ab-testing

brainbytes-dev/everything-claude-marketing/skills/analytics/ab-testing/SKILL.md

Design, execute, and analyze A/B tests across marketing channels. Use when running experiments on landing pages, emails, ads, or features.

Often used withfree-tools·marketing-council·emails

nasaSkill

fprime-component-integration-test

nasa/fprime/.github/skills/fprime-component-integration-test/SKILL.md

Integration testing phase of F Prime component development. Guides the agent through writing reusable pytest-based integration tests in the component's test/int/ folder using the GDS Integration Test API. These tests ship with the component and can be run against any deployment that includes it. Trigger when unit tests pass and the component is ready for integration testing. Keywords: F Prime, integration test, pytest, GDS, fprime_test_api, reusable test, component test.

No other project uses it yet

hyhmrrightSkill

brooks-test

hyhmrright/brooks-lint/skills/brooks-test/SKILL.md

Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "tests pass but bugs still reach production", or "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.

No other project uses it yet

ComposioHQSkill

python-testing

ComposioHQ/composio/.agents/skills/python-testing/SKILL.md

Select and run Python SDK verification with nox, Makefile targets, Ruff, mypy, pytest markers, sanity tests, type inference checks, and build checks. Use when adding Python tests, diagnosing Python CI, or validating Python SDK/provider changes. Do not use for TypeScript-only checks.

Often used withdjango-verification·python-patterns·project-guidelines-example

NVIDIASkill

mcore-testing

NVIDIA/skills/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.

FracteraSkill

use-testing

Fractera/Agent-Engineering-Infrastructure/.claude/skills/use-testing/SKILL.md

Build process. How work is PROVEN here — before you say «done», «it works», «ready to check». Load it when you are about to report a result, when a gate goes green and you feel finished, when something must be verified on the node, and when the owner asks for proof («show me the proof», «докажи»). The rule that changes behaviour: two proofs from DIFFERENT planes, one of them with a negative control, and a build log is never one of them — it reads the same whether the capability works or not.

samberSkill

golang-testing

samber/cc-skills-golang/skills/golang-testing/SKILL.md

Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see `samber/cc-skills-golang@golang-stretchr-testify`; for measurement methodology see `samber/cc-skills-golang@golang-benchmark`.

Often used withgolang-error-handling·golang-how-to·golang-security

astDenissSkill

ab-testing

astDeniss/business-skills/ab-testing/SKILL.md

Designs, sizes, and analyzes A/B tests end-to-end: hypothesis writing, primary metric and MDE selection, sample size and runtime math, guardrail metrics, and ship/kill decisions. Use when the user says \"design an A/B test\", \"what sample size do I need\", \"how long should my test run\", \"is this result statistically significant\", \"write a test hypothesis\", \"my experiment is flat, what now\", \"should we ship this variant\", \"my test results look weird\", or asks about split testing, experiment analysis, peeking, or rollout decisions.

Often used withfree-tools·marketing-council·emails

scayverSkill

ab-testing

scayver/marketing-skills/skills/ab-testing/SKILL.md

Use this skill when planning, designing, or analyzing A/B tests and growth experiments. Trigger phrases: "run an A/B test," "design an experiment," "write a hypothesis," "calculate sample size," "build an experimentation backlog," "ICE scoring," "statistical significance," "multivariate test," "growth experimentation," "test velocity."

Often used withfree-tools·marketing-council·emails