studio-e2e-tests
supabase/supabase/.agents/skills/studio-e2e-tests/SKILL.md
Write and run Playwright E2E tests for Supabase Studio (e2e/studio).
No other project uses it yet
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.
supabase/supabase/.agents/skills/studio-e2e-tests/SKILL.md
Write and run Playwright E2E tests for Supabase Studio (e2e/studio).
No other project uses it yet
supabase/supabase/.agents/skills/studio-mock-api-tests/SKILL.md
Component tests for Supabase Studio that mock API requests at the
gradio-app/gradio/.agents/skills/frontend-unit-testing/SKILL.md
Write comprehensive, behaviour-driven unit tests for Gradio frontend Svelte components using Vitest browser mode, Playwright, and the @self/tootils test utilities.
github/awesome-copilot/skills/creating-oracle-to-postgres-migration-integration-tests/SKILL.md
Creates integration test cases targeting Oracle for .NET data access artifacts. Tests capture Oracle expected behavior as the authoritative baseline; they are written once and later ported to PostgreSQL by migrating the test project in Phase 6. Use only during Phase 3, before any PostgreSQL migration work has begun. Do not invoke during Phase 6 or against a project that has already been migrated.
No other project uses it yet
langflow-ai/langflow/.agents/skills/ibm-a11y-testing-guide/SKILL.md
Reference guide for writing and running Langflow frontend accessibility tests with axe (Jest) and IBM Equal Access (Playwright `page.runA11yScan`). Covers which engine/test layer to pick, the POUR checklist, axe-vs-IBM rule gaps, Radix/AG-Grid component gotchas, and IBM baselines. Use when writing or reviewing a11y tests, debugging a specific axe/IBM violation, or deciding which test layer fits a UI surface. Does not run scans, audit a whole surface, or fix a PR end-to-end — see ibm-a11y-route-scan, ibm-a11y-level1-audit, and ibm-a11y-pr-remediation for those.
No other project uses it yet
open-ani/animeko/.agents/skills/datasource-test/SKILL.md
Test and debug an Animeko media source from its JSON config using the datasource-test-mcp HTTP MCP server. Validates selector config syntax offline, runs the real SelectorMediaSourceEngine pipeline (searchSubjects → selectSubjects → searchEpisodes → selectEpisodes → selectMedia) with per-step traces, iterates CSS selectors offline against saved HTML, tests matchVideo regexes, extracts real video URLs via CEF WebView, and probes actual playback with VLC. Use when asked to 测试数据源 / 调试 selector 配置 / verify a datasource JSON works / diagnose why a source finds no candidates for an episode or fails to play. Covers web-selector (CSS selector) sources in depth; other factories (rss/dmhy/mikan/jellyfin/...) via end-to-end testing. Also defines the capability-evolution (进化) loop: when a site is provably beyond current engine/WebVideoExtractor capabilities, write a capability-gap document and hand it to an isolated subagent that implements the new capability and outputs a git patch, then re-verify. Works exclusively through the `ani-datasource-test` HTTP MCP; it never starts the server itself — if that MCP is not configured the skill stops and tells the user how to add it. When a `chrome-devtools` MCP is also available, it is used as the real-browser ground truth (rendered DOM, real network requests, click interactions) to distinguish config mistakes from genuine engine/extractor capability gaps.
No other project uses it yet
handsontable/handsontable/.claude/skills/browserstack-live/SKILL.md
Use when testing a local or public URL on a real device via BrowserStack, opening a live browser session on Android, iOS, or desktop browsers, or when the user mentions BrowserStack, real device testing, mobile testing, cross-browser testing, touch testing, or wants to verify behavior on a specific phone, tablet, or browser version. Also trigger when the user says "test this on Android/iPhone/Safari/Chrome mobile", asks to open a live session, or mentions demo-mobile.html, even if they don't mention BrowserStack by name.
garrytan/gbrain/skills/smoke-test/SKILL.md
Health smoke tests + auto-fix for gbrain installs (and OpenClaw services when present). Run after machine/container restarts or whenever something seems broken. Tests critical services, auto-fixes bounded local issues, and reports worker topology without starting daemons. Extensible via user-defined test scripts in ~/.gbrain/smoke-tests.d/*.sh.
Steady42 mentions in 2 weeks
21 projects use a version of this
saleor/saleor/.claude/skills/pytest-runner/SKILL.md
Run pytest tests with automatic virtual environment activation. Use this skill whenever running tests, executing pytest, or when asked to "run tests", "test this", or any test execution task. Ensures venv is always activated before pytest runs.
googleapis/mcp-toolbox/skills/maintainer/fix-failing-tests/SKILL.md
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a test passes locally but fails in CI.
Steady8 mentions in 2 weeks
3 projects use a version of this
NangoHQ/nango/.agents/skills/running-tests/SKILL.md
Use when running tests in the Nango monorepo - knows unit vs integration configs, vitest commands, Docker setup, and common test patterns
10 projects use a version of this
QuivrHQ/quivr/.agents/skills/audit-tests-dev/SKILL.md
Invoke whenever writing, changing, reviewing, or sweeping tests.
mastra-ai/mastra/.claude/skills/testing-mastracode-tui/SKILL.md
Testing mastracode TUI features interactively in Konsole. Covers model configuration, thread lifecycle, task state isolation, and common blockers.
flet-dev/flet/.agents/skills/create-flet-control-integration-tests/SKILL.md
Use when asked to create or update integration tests for any Flet control in sdk/python/packages/flet/integration_tests, including visual goldens and interactive behavior tests.
dotnet/roslyn/.github/skills/patch-il-baselines/SKILL.md
Update expected IL baselines in compiler unit tests from Actual output for tests that are explicitly reported as failed. Use when Test Explorer or test output shows IL baseline differences and the requested fix is limited to those failed tests.
streamlit/streamlit/.claude/skills/fixing-flaky-e2e-tests/SKILL.md
Diagnose and fix flaky Playwright e2e tests. Use when tests fail intermittently, show timeout errors, have snapshot mismatches, or exhibit browser-specific failures.
Steady4 mentions in 2 weeks
No other project uses it yet
prowler-cloud/prowler/skills/pytest/SKILL.md
Pytest testing patterns for Python. Trigger: When writing or refactoring pytest tests (fixtures, mocking, parametrize, markers). For Prowler-specific API/SDK testing conventions, also use prowler-test-api or prowler-test-sdk.
Steady14 mentions in 2 weeks
3 projects use a version of this
supabase/supabase/.agents/skills/vitest/SKILL.md
Vitest API and config reference (Jest-compatible) — mocking with vi.*, spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering. Use for Vitest API and configuration questions anywhere in the monorepo; for Studio-specific test strategy and component-test setup, start with studio-testing and studio-mock-api-tests.
42 projects use a version of this
vercel/ai/skills/capture-api-response-test-fixture/SKILL.md
Capture API response test fixture.
Steady2 mentions in 2 weeks
1 project uses a version of this
PostHog/posthog/.agents/skills/setup-web-tests/SKILL.md
Set up Python test environment in Claude Code for web where flox is unavailable. Use when you need to run backend tests and `uv sync` fails due to Python version mismatch.
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.