Emc
aklofas/kicad-happy
EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair…
Run the core test suite (just test-core) to a clean, warning-free pass, with recipes for hanging tests and mold linker flakes.
Install Test Run
$ npx skills add mrchantey/beet --skill test-run -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mrchantey/beet test-run --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mrchantey/beet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/test-run .claude/skills/test-run && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "test-run" agent skill from https://github.com/mrchantey/beet/tree/main/.agents/skills/test-run into .claude/skills/test-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-run", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mrchantey/beet/tree/main/.agents/skills/test-runType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mrchantey/beet --skill test-run -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mrchantey/beet test-run --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mrchantey/beet.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/test-run .agents/skills/test-run && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-run" agent skill from https://github.com/mrchantey/beet/tree/main/.agents/skills/test-run into .agents/skills/test-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-run", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mrchantey/beet --skill test-run -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mrchantey/beet test-run --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mrchantey/beet.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/test-run .cursor/skills/test-run && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "test-run" agent skill from https://github.com/mrchantey/beet/tree/main/.agents/skills/test-run into .cursor/skills/test-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-run", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mrchantey/beet.git --path .agents/skills/test-run--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mrchantey/beet --skill test-run -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mrchantey/beet test-run --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mrchantey/beet.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/test-run .gemini/skills/test-run && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "test-run" agent skill from https://github.com/mrchantey/beet/tree/main/.agents/skills/test-run into .gemini/skills/test-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-run", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mrchantey/beet test-runInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mrchantey/beet --skill test-run -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mrchantey/beet.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/test-run .github/skills/test-run && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "test-run" agent skill from https://github.com/mrchantey/beet/tree/main/.agents/skills/test-run into .github/skills/test-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-run", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mrchantey/beet --skill test-run -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mrchantey/beet test-run --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mrchantey/beet.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/test-run .opencode/skills/test-run && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "test-run" agent skill from https://github.com/mrchantey/beet/tree/main/.agents/skills/test-run into .opencode/skills/test-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-run", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
test-run- GitHub stars
- 135
- Token cost
- ~544 tokens
- SKILL.md length
- 303 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Run the core test suite (just test-core) to a clean, warning-free pass, with recipes for hanging tests and mold linker flakes.
- Fix the test suite
- SKILL.md covers Context, Hanging Tests, Compile Errors and Instructions, plus 1 more section
- Calls just and cargo
- Tasks that involve Test generation
What it does
Test Run is an agent skill from mrchantey/beet. Run the core test suite (just test-core) to a clean, warning-free pass, with recipes for hanging tests and mold linker flakes. Use when asked to run or fix the test suite.
Its SKILL.md is about 540 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Test generation. The repository describes itself as: A malleable engine built on interoperable standards. The licence is Apache-2.0.
When your agent uses it
- Fix the test suite
- Tasks that involve Test generation
Example prompts
- “/test-run”
What it can do on your machine
Read from SKILL.md and the folder at commit 38648b8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
justcargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Test Run loads about 544 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 303 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mrchantey/beet at commit 38648b8, republished under its Apache-2.0 licence (© mrchantey). 303 words, ~544 tokens.
Download SKILL.mdSave it as
.claude/skills/test-run/SKILL.md (or your agent's skills folder).- name
- test-run
- description
- Run the core test suite (just test-core) to a clean, warning-free pass, with recipes for hanging tests and mold linker flakes. Use when asked to run or fix the test suite.
Run Tests
Context
Always use tail when running tests to preserve context. Run all tests piping the entire output to .agents/tmp/scratch.txt, use this for all commands, so that multiple greps can be applied without rerunning the tests.
Hanging Tests
If instructed, or you suspect, that some tests may hang, use timeout to catch these. Run an exponential backoff timeout, starting with two minutes, to catch hanging tests once you find a hanging test, shorten the timeout as much as possible to speed iteration cycles. When debugging hanging tests always pass the log-runs flag to detect the tests that dont finish, ie: timeout 120 cargo test -p beet_core --lib -- --log-runs. This will help you determine which test didnt complete
Compile Errors
these sweeping tests perform large compilations and sometimes the mold linker trips up. try running again, and if it still trips up sometimes incrementing the workspace and crates version, ie find-replace Cargo.toml 0.0.9-dev.6, ..dev.7, will unstuck it. A classic linker error is: help: you can increase rustc's stack size by setting RUST_MIN_STACK=.. this can usually be fixed by running again, and getting a little further down the compilation step.
Instructions
Run just test-core If you encounter an error, isolate it and run again, ie if the error is in beet_core lib: cargo test -p beet_core --all-features --lib -- test_name Fix the error using a subagent, then run the crate again: cargo test -p beet_core --all-features When thats clear, run the full suite again just test-core | tail After the first complete pass, run fully again, checking for warnings. Fix any warnings encountered
Success
Success means that just test-core passes without warnings. Every warning counts, including ones in code you did not touch or another agent just committed: fix it, do not report it as pre-existing. Upon completion provide a comprehensive summary of what was changed.
© mrchantey, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/test-run of mrchantey/beet.
Open the folder on GitHubat commit 38648b8
Compare with similar skills
Test Run next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Test Run this skillmrchantey/beet | 135 | — | ~544 | Automated safety check: Pass | Apache-2.0 | |
| Emcaklofas/kicad-happy | 1.4k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Swig Testswig/swig | 6.3k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Generate Test Cases342164796/generate-test-cases | 119 | 1 repos | ~2.9k | Automated safety check: Pass | None | |
| Verify Cc Safety Netkenryu42/cc-safety-net | 1.6k | — | ~2k | Automated safety check: Pass | MIT | |
| Wioworkersio/skills | 190 | — | ~5.8k | Automated safety check: Pass | MIT |
Similar skills
Swig Test
swig/swig
Run SWIG test suite for specific languages. An agent skill from swig/swig.
Generate Test Cases
342164796/generate-test-cases
自主学习型测试文档生成器。从需求文档（Markdown）生成测试用例 XMind 文件，支持持久化记忆和持续学习。当用户提到"生成测试用例"、"根据需求生成测试"时触发。
Verify Cc Safety Net
kenryu42/cc-safety-net
Launch and drive the real cc-safety-net CLI — the hook decision path, explain, status/doctor, logs, and the local policy GUI — against an isolated home, capturing evidence.
Wio
workersio/skills
Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.
- Official
File Server
microsoft/WindowsProtocolTestSuites
ALWAYS LOAD THIS SKILL when working with FileServer, SMB, SMB2, SMB3, CIFS, file sharing, MS-SMB2, MS-FSCC, MS-FSA, MS-DFSC, MS-FSRVP, MS-RSVD, MS-SQOS, or any file server protocol test…
More from mrchantey/beet
All 11 skills in this repoDownstream Create
mrchantey/beet
Scaffold a new beet downstream repo (beet<name, a sibling of this checkout depending on the beet facade by path) from the template, register it with downstream-sync and run the first sync.
Test Examples
mrchantey/beet
Run the workspace example smoke set to catch regressions unit tests miss, covering every feature gate combination with self-terminating examples and curl-probed servers.
Test The Works
mrchantey/beet
Maximal project health pass. An agent skill from mrchantey/beet.
Docs Rust Sweep
mrchantey/beet
Comprehensive public-api quality pass over the core crates, reducing pub visibility and documenting every public item to a deny(missingdocs) standard.
Docs Site
mrchantey/beet
Write and edit the public website docs in site/routes/docs (beet.org/docs).
Infra Deploy
mrchantey/beet
The release process for the beet website. An agent skill from mrchantey/beet.
Related
Categories
Questions about Test Run
What does Test Run do?
Run the core test suite (just test-core) to a clean, warning-free pass, with recipes for hanging tests and mold linker flakes. Test Run is an agent skill from mrchantey/beet. Run the core test suite (just test-core) to a clean, warning-free pass, with recipes for hanging tests and mold linker flakes.
When should I use Test Run?
Test Run fits situations like: fix the test suite; tasks that involve Test generation.
How do I install Test Run in Claude Code?
Run `npx skills add mrchantey/beet --skill test-run -a claude-code`. Or copy the skill folder (.agents/skills/test-run in mrchantey/beet) into .claude/skills/test-run in your project. Claude Code loads it when a task matches its description.
How do I install Test Run in Codex?
Run `npx skills add mrchantey/beet --skill test-run -a codex`. Or copy the skill folder (.agents/skills/test-run in mrchantey/beet) into .agents/skills/test-run in your project. Codex loads it when a task matches its description.
Can I use Test Run in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mrchantey/beet --skill test-run -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-run, .gemini/skills/test-run, .github/skills/test-run and .opencode/skills/test-run in your project.
What does Test Run need to run?
Going by SKILL.md and its folder, Test Run needs the command-line tools its instructions call (just and cargo).
Does Test Run access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Test Run safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Test Run use?
Test Run is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Test Run use?
About 544 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Test Run?
Skills that share tags, products or a category with Test Run: Emc (aklofas/kicad-happy, 1.4k stars), Swig Test (swig/swig, 6.3k stars), Generate Test Cases (342164796/generate-test-cases, 119 stars) and Verify Cc Safety Net (kenryu42/cc-safety-net, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Run?
mrchantey (a GitHub user) maintains it in mrchantey/beet, which has 135 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.
Source: mrchantey/beet on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.