visual-test
microsoft/fluentui/.claude/skills/visual-test/SKILL.md
@../../../.agents/skills/visual-test/SKILL.md
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
microsoft/fluentui/.claude/skills/visual-test/SKILL.md
@../../../.agents/skills/visual-test/SKILL.md
quarkusio/quarkus/.agents/skills/building-and-testing/SKILL.md
How to build and test Quarkus: Maven commands, build flags, incremental builds, justfile aliases, and important build rules.
typescript-eslint/typescript-eslint/.agents/skills/tests/SKILL.md
Write rule test cases the way this repo expects — one logical unit per test case, static self-contained snippets, comments only when they add meaning, and precise error assertions. Use when adding or changing tests in packages/eslint-plugin/tests/rules or reviewing a PR that touches rule tests.
microsoft/ai-agents-for-beginners/translations/en/.agents/skills/testing-course-samples/SKILL.md
Use when asked to validate, test, smoke-test, or run the course's notebook
Steady33 mentions in 2 weeks
No other project uses it yet
usestrix/strix/skills/owasp-top-10-testing/SKILL.md
Test an application against the OWASP Top 10 with Strix — autonomous AI agents that attempt real exploits for each category of the current OWASP Top 10:2025 (broken access control including SSRF, security misconfiguration, software supply chain failures, cryptographic failures, injection, insecure design, authentication failures, integrity failures, logging and alerting failures, mishandling of exceptional conditions) and report only what they could actually prove, mapped back to the category with a proof-of-concept. Also covers the OWASP API Security Top 10 (2023). Use when the user asks for an OWASP Top 10 assessment, OWASP compliance testing, or a security review mapped to OWASP categories.
Steady5 mentions in 2 weeks
2 projects use a version of this
open-metadata/OpenMetadata/skills/java-affected-tests/SKILL.md
Use before opening or updating an OpenMetadata PR that changes Java, a JSON schema, an index mapping, a SQL migration, seed data or a pom — PR CI no longer runs the Java integration tests (they run only in the merge queue) and the JavaUIIT/search-it suites run only nightly, so this selects the unit tests and integration tests the diff can break, runs them in the lane and engine CI uses, and records the results in the PR body. Also use when asked which Java tests to run for a change, or how to run one integration test.
Steady4 mentions in 2 weeks
No other project uses it yet
tldraw/tldraw/skills/spec-driven-tests/SKILL.md
Rebuild a package's unit test suite around a behavior specification (SPEC.md) derived from the implementation, with every test citing a numbered rule ID. Use when asked to do a spec-driven test rebuild, write a SPEC.md for a package, repeat the state or store spec process (PRs #9158, #9172) for another package, or rebuild tests around a spec.
Steady2 mentions in 2 weeks
No other project uses it yet
documenso/documenso/.agents/skills/envelope-editor-v2-e2e/SKILL.md
Writing and maintaining Playwright E2E tests for the Envelope Editor V2. Use when the user needs to create, modify, debug, or extend E2E tests in packages/app-tests/e2e/envelope-editor-v2/. Triggers include requests to "write an e2e test", "add a test for the envelope editor", "test envelope settings/recipients/fields/items/attachments", "fix a failing envelope test", or any task involving Playwright tests for the envelope editor feature.
Steady7 mentions in 2 weeks
No other project uses it yet
github/awesome-copilot/skills/test-gap-audit/SKILL.md
Run a read-only audit for missing, weak, stale, or mis-scoped test coverage. If the user does not name a scope, audit the full repository and identify important code paths, routes, features, services, workflows, and contracts that lack proper tests. If the user names a feature, PR, branch, route, workflow, service, bug fix, API, security-sensitive path, or risky code change, focus only on that specific scope. Use when the user asks what tests are missing, whether coverage is enough, what regression tests to add, or how to prove a change is safe. This is not a general bug audit and not a security review; it evaluates whether behavior is covered by tests.
Surging1 mention in 2 weeks
2 projects use a version of this
appsmithorg/appsmith/.agents/skills/write-and-verify-pw-test/SKILL.md
Write a Playwright E2E test from a prompt and verify it passes against a live Appsmith deployment. Configures environment variables, writes the spec following project conventions, runs it, and auto-fixes up to 3 times. Use when asked to "write a playwright test", "test this feature on a dp", "create and run an e2e test", or "verify this flow with playwright".
Steady6 mentions in 2 weeks
No other project uses it yet
loft-sh/vcluster/.claude/skills/e2e-migration-validator/SKILL.md
Use this skill whenever a user wants to validate, review, or audit e2e tests that have been migrated from an old framework (typically in a `e2e/` directory) to the new `e2e/` framework. Triggers include: "review my migrated test", "validate this e2e test", "check my test migration", "did I migrate this correctly", "review e2e PR", "check test coverage after migration", or any request involving comparing old vs new e2e test files across the vcluster, vcluster-pro, or loft-enterprise repos. Always use this skill when an e2e test file or PR from one of these repos is provided for review — even if the user just says "take a look at this test".
Steady8 mentions in 2 weeks
No other project uses it yet
assistant-ui/assistant-ui/.claude/skills/test-quality/SKILL.md
Design and review meaningful tests for assistant-ui bug fixes, behavior changes, and pull requests that add, change, or remove tests. Use to choose test boundaries, prove regressions, and assess mocks and assertions. Editorial-only changes do not require new tests.
11 projects use a version of this
microsoft/playwright/.claude/skills/playwright-test-results/SKILL.md
Query Playwright CI test results from the aggregated DuckDB database. Answers questions about flaky tests, failure rates, slow tests, and per-run/SHA/PR results without hunting through GitHub artifacts.
No other project uses it yet
mem0ai/mem0/skills/mem0-test-integration/SKILL.md
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate and says "verify", "test the integration", "run /mem0-test-integration", or when a .mem0-integration/ directory exists and tests have not been run yet on the current branch. DO NOT TRIGGER when: the user wants to run general project tests (defer to the repo's native test command), or when no prior /mem0-integrate run exists in the current branch (ask them to run /mem0-integrate first). This skill ONLY catches compile and runtime bugs by design. Logical integration errors — wrong data stored, wrong time retrieved, wrong user scoping — are on the human reviewer.
No other project uses it yet
github/awesome-copilot/skills/react18-enzyme-to-rtl/SKILL.md
Provides exact Enzyme → React Testing Library migration patterns for React 18 upgrades. Use this skill whenever Enzyme tests need to be rewritten - shallow, mount, wrapper.find(), wrapper.simulate(), wrapper.prop(), wrapper.state(), wrapper.instance(), Enzyme configure/Adapter calls, or any test file that imports from enzyme. This skill covers the full API mapping and the philosophy shift from implementation testing to behavior testing. Always read this skill before rewriting Enzyme tests - do not translate Enzyme APIs 1:1, that produces brittle RTL tests.
1 project uses a version of this
getsentry/sentry/.agents/skills/generate-snapshot-tests/SKILL.md
Generate visual snapshot test files for Sentry frontend React components. Use for testing appearance changes such as colors, spacing, typography, CSS min/max sizing, responsive layout, and visual variants, or when asked to "generate snapshot tests", "create visual snapshots", "add visual regression tests", or "snapshot this component". Accepts an optional component path or name via $ARGUMENTS.
No other project uses it yet
github/awesome-copilot/skills/scaffolding-oracle-to-postgres-migration-test-project/SKILL.md
Scaffolds an xUnit integration test project targeting Oracle in .NET solutions. Creates the test project, transaction-rollback base class, and seed data manager. Use only during Phase 3, before writing Oracle baseline integration tests. Do not invoke during Phase 6 — the PostgreSQL test project is produced by migrating this project, not by running this skill again.
No other project uses it yet
fossasia/visdom/.agents/skills/playwright-testing/SKILL.md
Playwright E2E creation, visual regression workflow, and testing best practices for Visdom
metabase/metabase/.claude/skills/e2e-test/SKILL.md
Run Cypress E2E tests, analyze failures including screenshots, and stress test for flakiness
coleam00/Archon/.claude/skills/test-release/SKILL.md
Verify a released archon binary works end-to-end via a specific install path. Use when: cutting a new release, reproducing a user bug report on the released version, or validating that a hotfix binary actually works after a re-tag. Triggers: "test the release", "test 0.3.1 via brew", "verify the curl install", "smoke test the binary", "did the release binary work", "run /test-release", "verify the release". NOT for: testing dev work (use bun link directly), testing unreleased changes (build locally via scripts/build-binaries.sh first), or running the full validate suite (bun run validate is separate).
2 projects use a version of this
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.