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. Use when adding or running a unit or functional test; understanding the test layout; writing a recipe YAML; downloading or updating golden values; reproducing a test failure locally; 'how do I add a test', 'run unit tests', 'pytest fails', 'test layout', 'golden values', 'recipe YAML', 'marker filter'.
18k4d agoReviewMountCreate a free account to mount
Test AG2 beta agents and tools without hitting a real LLM provider. Pass `TestConfig(...)` from `autogen.beta.testing` as the agent's config (or per-`ask`) to mock LLM responses, inject `ToolCallEvent`s to simulate tool execution, and assert success / error paths. Use when the user is writing pytest tests for an Agent or Tool.
2527mo agoReviewMountCreate a free account to mount
Write unit and integration tests for Go services. Use when creating, editing, or updating tests, test helpers, mocks, fuzz tests, or benchmarks in Go projects.
Run coverage, inspect results, and identify missing test scenarios for a given source file. Use when analysing test coverage or finding untested branches.
Steady7 mentions in 2 weeks
No other project uses it yet
2.1k8mo agoReviewMountCreate a free account to mount
Husi project's testing conventions. Use whenever adding, updating, or debugging tests under composeApp/ — ViewModels, updaters, ktx helpers, anything in commonTest/desktopTest. Also use when a piece of production code needs a DI seam to become testable (HTTP, DataStore, Libcore). Do not reach for mockk first or invent a new base class — consult this skill before writing the first test in a new file.
1.9k8d 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.
2243mo agoReviewMountCreate a free account to mount
Use when writing, changing or debugging a vitest unit test in packages/ - mocks, fake timers, jsdom or happy-dom, mounting providers or dnd-kit components, StrictMode, counting renders, a test that passes for the wrong reason, a throwaway probe test - and when a downstream package's tests seem to run old behaviour.
1.7k1d agoReviewMountCreate a free account to mount
GAIA's multi-tier regression harness — runs unit, integration, and real-world (on-machine) tiers and brings back screenshots, logs, traces, planted-fact retrieval proof, and per-operation timing with anomaly flags, all collected to the local machine (no remote login needed to view). It carries GAIA's drivers (Agent UI, Agent UI MCP), exact commands, ports, and `gaia eval agent` baselines, and extends (does not replace) the generic `testing` skill. Fires when the user wants real-world / on-hardware proof, screenshots, or end-to-end evidence that a feature, agent, change, fix, or release actually works — not a quick 'is the app running' check (the `verify` skill) or an LLM-behaviour scorecard alone (`gaia eval agent`). Scales: 'run the unit tests' stays unit-only and skips the planning gate; 'test / validate / QA this feature or release' runs all applicable tiers with evidence.
1.6k1d agoReviewMountCreate a free account to mount
Decide whether a change needs a test, where it lives, what it asserts, and which check to run before calling it done. Use when adding, moving, or reviewing a unit, component, integration, story, or end-to-end test, or choosing the smallest check to run before a PR.
2326d agoReviewMountCreate a free account to mount
Verify software against its requirements and find what is broken - plan what to test, write meaningful unit, integration, and end-to-end tests, exercise edge cases, check accessibility and performance, reproduce failures, check regressions, and report results with evidence. Use when a task asks to test, verify, or review that something works, when building or reviewing any feature that must be proven, and when a bug must be reproduced and pinned with a test.
Guide for writing SGLang CI/UT tests. Covers CustomTestCase, CI registration, which tier (base, extra, nightly, weekly) and runner a test belongs to, server fixtures, model selection, mock testing, and test placement. Always read test/README.md for the full CI layout, how to run tests, and extra tips. Use when creating new tests, adding CI test cases, writing unit tests, moving a test between tiers, or when the user asks to add tests for SGLang features.
Steady5 mentions in 2 weeks
1 project uses a version of this
39k1d agoReviewMountCreate a free account to mount
Capsem testing policy and workflow. Use whenever running or writing tests. For VM, hypervisor, frontend, or Python specifics see the dev-testing-* skills.
17917d agoReviewMountCreate a free account to mount
Testing Skill
Compare two URL variants with the same persona to determine which provides a better user experience. This skill guides the comparison logic and report generation.
## When
Instructions for writing, running, and updating unit/end-to-end tests. Should be used when prompted specifically to add tests for a given feature, bug, or regression.
Steady26 mentions in 2 weeks
1 project uses a version of this
10k4d agoReviewMountCreate a free account to mount
Write adversarial test cases that break production code instead of producing false confidence. Use when writing, reviewing, or planning tests for any codebase. Triggers on: "write tests", "add test coverage", "test this function", "create unit tests", "integration tests", "fix flaky tests", "improve test coverage", "review test quality", "are these tests good", "test plan", "break this code", "find edge cases", or any task involving pytest, vitest, jest, or other test frameworks. Enforces the prime directive — a test that cannot fail is not a test — and prevents common AI testing pitfalls: over-mocking, testing frameworks instead of production code, fake implementations that bypass real logic, and assertion-free tests.
3273d 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.