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…
A skill your agent uses when adding or modifying JET tests. An agent skill from aviatesk/JET.jl.
Install Write Test
$ npx skills add aviatesk/JET.jl --skill write-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aviatesk/JET.jl write-test --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/aviatesk/JET.jl.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-test .claude/skills/write-test && 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 "write-test" agent skill from https://github.com/aviatesk/JET.jl/tree/master/.agents/skills/write-test into .claude/skills/write-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-test", 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/aviatesk/JET.jl/tree/master/.agents/skills/write-testType 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 aviatesk/JET.jl --skill write-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aviatesk/JET.jl write-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviatesk/JET.jl.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/write-test .agents/skills/write-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-test" agent skill from https://github.com/aviatesk/JET.jl/tree/master/.agents/skills/write-test into .agents/skills/write-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-test", 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 aviatesk/JET.jl --skill write-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aviatesk/JET.jl write-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviatesk/JET.jl.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/write-test .cursor/skills/write-test && 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 "write-test" agent skill from https://github.com/aviatesk/JET.jl/tree/master/.agents/skills/write-test into .cursor/skills/write-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-test", 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/aviatesk/JET.jl.git --path .agents/skills/write-test--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 aviatesk/JET.jl --skill write-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aviatesk/JET.jl write-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviatesk/JET.jl.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/write-test .gemini/skills/write-test && 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 "write-test" agent skill from https://github.com/aviatesk/JET.jl/tree/master/.agents/skills/write-test into .gemini/skills/write-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-test", 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 aviatesk/JET.jl write-testInstalls 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 aviatesk/JET.jl --skill write-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aviatesk/JET.jl.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/write-test .github/skills/write-test && 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 "write-test" agent skill from https://github.com/aviatesk/JET.jl/tree/master/.agents/skills/write-test into .github/skills/write-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-test", 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 aviatesk/JET.jl --skill write-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aviatesk/JET.jl write-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviatesk/JET.jl.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/write-test .opencode/skills/write-test && 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 "write-test" agent skill from https://github.com/aviatesk/JET.jl/tree/master/.agents/skills/write-test into .opencode/skills/write-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-test", 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
write-test- GitHub stars
- 883
- Token cost
- ~777 tokens
- SKILL.md length
- 310 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when adding or modifying JET tests. An agent skill from aviatesk/JET.jl.
- Modifying JET tests
- SKILL.md covers Choose the test location, Test file structure, Shared test utilities and Organize test code, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Test generation
What it does
Write Test is an agent skill from aviatesk/JET.jl. Use when adding or modifying JET tests. Covers component placement, independently runnable test modules, shared test utilities, @testset organization, and focused assertions for JET reports.
Its SKILL.md is about 780 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 code analyzer for Julia. No need for additional type annotations. The licence is MIT.
When your agent uses it
- Modifying JET tests
- Tasks that involve Test generation
Example prompts
- “/write-test”
What it can do on your machine
Read from SKILL.md and the folder at commit 19c3b4c. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are julia).
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
Write Test loads about 777 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 310 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 aviatesk/JET.jl at commit 19c3b4c, republished under its MIT licence (© aviatesk). 310 words, ~777 tokens.
Download SKILL.mdSave it as
.claude/skills/write-test/SKILL.md (or your agent's skills folder).- name
- write-test
- description
- Use when adding or modifying JET tests. Covers component placement, independently runnable test modules, shared test utilities, `@testset` organization, and focused assertions for JET reports.
Write JET tests
Use this skill when adding new JET tests or modifying existing test code.
Choose the test location
Place tests beside the component they cover and include new files from
test/runtests.jl. Existing component directories
include:
test/abstractinterpret/test/analyzers/test/toplevel/test/ui/
Use a root-level file under test/ for cross-component integration or
miscellaneous behavior when that matches the neighboring tests.
Test file structure
New test files should normally define an independent module with a test_
prefix matching the file name. For example,
test/toplevel/test_feature.jl should follow this structure:
module test_feature
include("../setup.jl")
@testset "feature behavior" begin
let source = "x = 1"
result = report_text(source)
@test isempty(result.res.toplevel_error_reports)
end
let source = "x ="
result = report_text(source)
@test !isempty(result.res.toplevel_error_reports)
end
end
end # module test_featureInclude it from test/runtests.jl under the relevant component:
@testset "toplevel" begin
@testset "feature.jl" include("toplevel/test_feature.jl")
endMost existing tests follow this convention. Do not copy the known exception in
test/abstractinterpret/test_inferenceerrorreport.jl, which currently depends
on running in Main.
Shared test utilities
Subdirectory tests that need JET's report helpers generally include
test/setup.jl with include("../setup.jl").
It loads Test, JET, and the helpers from test/interactive_utils.jl.
Do not include the shared setup automatically when direct using JET, Test or
narrow imports are sufficient.
Organize test code
Use concise behavior-oriented @testset names. Group related cases into
coherent @testset blocks so testrunner can select them by name. Nest
@testset blocks when a larger behavior area has useful subgroups.
Keep using, import, helper functions, macros, and type definitions at module
scope unless local placement is specifically required.
When an @testset contains multiple test units, use a separate let block for
each unit to prevent variable collisions. A let block is unnecessary when the
@testset contains only one unit because there is no later unit with which its
variables can collide. A helper function or do block also provides local
scope.
Prefer assertions on report types, fields, counts, and semantic properties.
Reserve output-string assertions for formatting and UI behavior, such as tests
under test/ui/, unless the exact rendered message is the behavior under test.
After writing tests
Use the run-test workflow and run the most specific
relevant test before broader validation.
© aviatesk, MIT. 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/write-test of aviatesk/JET.jl.
Open the folder on GitHubat commit 19c3b4c
Compare with similar skills
Write Test 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 |
|---|---|---|---|---|---|---|
| Write Test this skillaviatesk/JET.jl | 883 | — | ~777 | Automated safety check: Pass | MIT | |
| Emcaklofas/kicad-happy | 1.3k | 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 | 180 | — | ~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 aviatesk/JET.jl
Commit
aviatesk/JET.jl
A skill your agent uses when writing a commit message, and MUST invoke before creating any git commit.
Run Test
aviatesk/JET.jl
A skill your agent uses when choosing or running JET tests after code changes.
Changelog
aviatesk/JET.jl
Invoke before committing user-facing JET changes such as features, bug fixes, compatibility changes, or deprecations.
Related
Categories
Questions about Write Test
What does Write Test do?
A skill your agent uses when adding or modifying JET tests. An agent skill from aviatesk/JET.jl. jl. Use when adding or modifying JET tests.
When should I use Write Test?
Write Test fits situations like: modifying JET tests; tasks that involve Test generation.
How do I install Write Test in Claude Code?
Run `npx skills add aviatesk/JET.jl --skill write-test -a claude-code`. Or copy the skill folder (.agents/skills/write-test in aviatesk/JET.jl) into .claude/skills/write-test in your project. Claude Code loads it when a task matches its description.
How do I install Write Test in Codex?
Run `npx skills add aviatesk/JET.jl --skill write-test -a codex`. Or copy the skill folder (.agents/skills/write-test in aviatesk/JET.jl) into .agents/skills/write-test in your project. Codex loads it when a task matches its description.
Can I use Write Test 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 aviatesk/JET.jl --skill write-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-test, .gemini/skills/write-test, .github/skills/write-test and .opencode/skills/write-test in your project.
What does Write Test need to run?
SKILL.md names no scripts, command-line tools or credentials: Write Test is instructions for the agent only.
Does Write Test 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 Write Test 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 Write Test use?
Write Test is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Write Test use?
About 777 tokens (SKILL.md is roughly 3.1k 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 Write Test?
Skills that share tags, products or a category with Write Test: Emc (aklofas/kicad-happy, 1.3k 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 Write Test?
aviatesk (a GitHub user) maintains it in aviatesk/JET.jl, which has 883 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.
Source: aviatesk/JET.jl on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.