Garden the test suite by finding and removing redundant, vacuous, or implementation-coupled tests while preserving useful regression coverage. Use for test audits, test pruning, duplicate coverage, or reducing CI test cost. Supports focused cleanups and coordinated audit campaigns.
80 projects use a version of this
114k2d agoReviewMountCreate a free account to mount
Provides test quality standards and best practices. Use when writing test cases, creating unit tests, implementing tests, or refining/reviewing test code. Essential for test generation and test refinement phases.
1.3k56d agoReviewMountCreate a free account to mount
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.
1.1k5mo agoReviewMountCreate a free account to mount
Verify NeMo AutoModel models against HuggingFace references (state dicts, forward pass). Use for loss divergence, output mismatches, or checking state-dict mappings.
1.1k11d agoReviewMountCreate a free account to mount
Use when creating, modifying, debugging, or reviewing Aspire CLI end-to-end tests that use Hex1b terminal automation under tests/Aspire.Cli.EndToEnd.Tests/.
2 projects use a version of this
6.4k6mo agoReviewMountCreate a free account to mount
Runs model-level and module-level tests for TensorRT-LLM. First classifies the test scope (module test or model test), then dispatches to the appropriate workflow. Model tests are further classified by type (functionality/smoke test, benchmark, or evaluation). Prompts the user for parallelism parameters (tp, ep, dp), dataset paths, device type, or a config file as needed. All test execution is delegated to trtllm-case-executor.
Steady3 mentions in 2 weeks
No other project uses it yet
15k3mo agoReviewMountCreate a free account to mount
Writing unit and integration tests for the tldraw SDK. Use when creating new tests, adding test coverage, or fixing failing tests in packages/editor or packages/tldraw. Covers Vitest patterns, TestEditor usage, and test file organization.
11 projects use a version of this
51k6mo agoReviewMountCreate a free account to mount
Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications. Includes test suite generation, coverage analysis, E2E testing setup, and quality metrics. Use when designing test strategies, writing test cases, implementing test automation, performing manual testing, or analyzing test coverage.
Write and run ryOS tests with Bun's native test runner (bun:test). Covers unit/wiring tests (no server) vs API integration tests (require the standalone API server), shared HTTP helpers, and the package.json suite commands. Use when adding tests, writing test coverage for a change, or running/triaging the test suite.
Run and debug Vitess end-to-end tests. Use when working with tests under go/test/endtoend/, when asked to run e2e tests, debug e2e test failures, or investigate test flakiness.
21k4mo agoReviewMountCreate a free account to mount
Testing CKEditor 5 plugins in the Trilium monorepo. Use when adding or reviewing unit tests for the packages/ckeditor5 aggregate (including its in-tree plugins under src/plugins/), debugging a failing test, or setting up a package's test runner. Covers the Playwright browser-mode Vitest setup, the vitest.config.ts, testing against a real ClassicEditor, the model/view helpers imported from 'ckeditor5' (_setModelData / _getModelData / _getViewData and their {}/[] selection syntax), vi spies/mocks, idiomatic patterns for schema/conversion/command/UI tests, the pnpm --filter runner, and Trilium-specific conventions and gotchas. Complements the ckeditor5-plugin-development and writing-unit-tests skills.
Steady11 mentions in 2 weeks
No other project uses it yet
39k26d agoReviewMountCreate a free account to mount
Run Newton examples for visual QA of a release wheel or requested checkout, exercising viewer controls and checking motion, picking, and end-of-run settling against example-specific criteria. Use for example testing and release QA, not as a substitute for unit tests or release approval.
Inspect the current pull request, stacked pull requests, branch, or working-tree change; draft a risk-based test plan; interview the user to agree on what deserves testing, the faithful test boundary, representative cases, and explanatory comments; then implement the agreed tests. Use when asked to add tests, decide test coverage for current work, test a PR or PR stack, or turn a completed change into a reviewed test plan and test suite. Pass `decide-for-me` to skip the interview and have the agent take its own recommendations.
6 projects use a version of this
1.6k48d agoReviewMountCreate a free account to mount
Writes and runs Filament tests with Pest, Pest Browser, accessibility checks, and test databases. Use when planning verification, adding or changing tests, running tests, or validating asynchronous JavaScript changes in this repository.
Steady2 mentions in 2 weeks
No other project uses it yet
33k9d agoReviewMountCreate a free account to mount
Use when the user wants to create, update, or browse manual QA test cases and suites in TestDino — not execution runs. Covers list_manual_test_suites, list_manual_test_cases, get_manual_test_case, create_manual_test_case, update_manual_test_case, create_manual_test_suite.
No other project uses it yet
4.8k3mo agoReviewMountCreate a free account to mount
Extract a standalone JIT regression test case from a given GitHub issue and save it under a JIT regression runner folder. USE FOR: creating JIT regression tests, extracting repro code from dotnet/runtime issues, "write a test for this JIT bug", "create a regression test for issue #NNNNN", converting issue repro to xunit test. DO NOT USE FOR: non-JIT tests (use standard test patterns), debugging JIT issues without a known repro, performance benchmarks (use microbenchmark skill).
18k2y agoReviewMountCreate a free account to mount
Expert guidance for Swift Testing: test structure, #expect/#require macros, traits and tags, parameterized tests, test plans, parallel execution, async waiting patterns, and XCTest migration. Use when writing new Swift tests, modernizing XCTest suites, debugging flaky tests, or improving test quality and maintainability in Apple-platform or Swift server projects.
Surging1 mention in 2 weeks
7 projects use a version of this
6.4k28d agoReviewMountCreate a free account to mount
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.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
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.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.