Agent skill

Write Test

A skill your agent uses when adding or modifying JETLS tests.

MITAuto-check passedTesting & QA

Install Write Test

skills CLI

$ npx skills add aviatesk/JETLS.jl --skill write-test -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install aviatesk/JETLS.jl write-test --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/aviatesk/JETLS.jl.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-test .claude/skills/write-test && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "write-test" agent skill from https://github.com/aviatesk/JETLS.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

$skill-installer install https://github.com/aviatesk/JETLS.jl/tree/master/.agents/skills/write-test

Type 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.

skills CLI

$ npx skills add aviatesk/JETLS.jl --skill write-test -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install aviatesk/JETLS.jl write-test --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aviatesk/JETLS.jl.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/write-test .agents/skills/write-test && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "write-test" agent skill from https://github.com/aviatesk/JETLS.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.

skills CLI

$ npx skills add aviatesk/JETLS.jl --skill write-test -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install aviatesk/JETLS.jl write-test --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aviatesk/JETLS.jl.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/write-test .cursor/skills/write-test && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "write-test" agent skill from https://github.com/aviatesk/JETLS.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

$ gemini skills install https://github.com/aviatesk/JETLS.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.

skills CLI

$ npx skills add aviatesk/JETLS.jl --skill write-test -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install aviatesk/JETLS.jl write-test --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aviatesk/JETLS.jl.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/write-test .gemini/skills/write-test && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "write-test" agent skill from https://github.com/aviatesk/JETLS.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.

GitHub CLI

$ gh skill install aviatesk/JETLS.jl write-test

Installs 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).

skills CLI

$ npx skills add aviatesk/JETLS.jl --skill write-test -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/aviatesk/JETLS.jl.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/write-test .github/skills/write-test && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "write-test" agent skill from https://github.com/aviatesk/JETLS.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.

skills CLI

$ npx skills add aviatesk/JETLS.jl --skill write-test -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install aviatesk/JETLS.jl write-test --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aviatesk/JETLS.jl.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/write-test .opencode/skills/write-test && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "write-test" agent skill from https://github.com/aviatesk/JETLS.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: 314
Token cost: ~707 tokens
SKILL.md length: 229 words
Files: 1
Skills in repo: 4
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when adding or modifying JETLS tests.

Modifying JETLS tests
SKILL.md covers Test file structure, Organizing test code, Language-server feature tests and After writing tests
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/JETLS.jl. Use when adding or modifying JETLS tests. Covers test file and module structure, @testset organization, let blocks, withserver usage, and when subroutine tests are sufficient for language-server features.

Its SKILL.md is about 710 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 new language server for Julia, enabling modern, compiler-powered tooling. The licence is MIT.

When your agent uses it

Modifying JETLS 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 037f91b. 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 707 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 229 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~55
When it runs · the whole SKILL.md, loaded when a task matches: ~707

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/JETLS.jl at commit 037f91b, republished under its MIT licence (© aviatesk). 229 words, ~707 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 JETLS tests. Covers test file and module structure, `@testset` organization, `let` blocks, `withserver` usage, and when subroutine tests are sufficient for language-server features.

Write JETLS tests

Use this skill when you add new tests or modify existing JETLS test code.

Test file structure

Test code for new language server features should be written in files that define independent module spaces with a test_ prefix. Include those files from test/runtests.jl.

This lets each test file run independently from the REPL.

For example, test/test_completions.jl should look like:

julia

module test_completions
using Test
...
end # module test_completions

Then include it from test/runtests.jl like this:

julia

@testset "JETLS.jl" begin
    ...
    @testset "completions" include("test_completions.jl")
    ...
end

Organizing test code

Use @testset "testset name" to organize tests cleanly.

For code clarity, avoid placing using, import, or struct definitions inside @testset blocks unless it is specifically necessary. Prefer top-level definitions.

Use let blocks to avoid unintentionally reusing names across test cases, unless a helper function or do block already provides local scope.

Example:

julia

module test_completions

using Test
using JETLS: some_completion_func

function testcase_util(s::AbstractString)
    ...
end
function with_testcase(s::AbstractString)
    ...
end

@testset "some_completion_func" begin
    let s = "..."
        ret = some_completion_func(testcase_util(s))
        @test test_with(ret)
    end
    let s = "..."
        ret = some_completion_func(testcase_util(s))
        @test test_with(ret)
    end

    with_testcase(s) do case
        ret = some_completion_func(case)
        @test test_with(ret)
    end
end

end # module test_completions

Language-server feature tests

Testing language server functionality is challenging. To fully test such functionality, you need to start a server loop and send requests that mimic realistic user interactions.

For those tests, use withserver from test/setup.jl. Refer to test/test_full_lifecycle.jl as an example.

A good pattern is test/test_definition.jl: it keeps the full withserver coverage to one request/response sanity test for the DidOpen → analysis → DefinitionRequest path, while most cases use definition_test to call find_definition directly and assert on returned locations. Prefer this split for LSP handlers.

After writing tests

When you add or modify tests, use the run-test workflow to run the most specific relevant test command.

Files

Just SKILL.md in .agents/skills/write-test of aviatesk/JETLS.jl.

Open the folder on GitHubat commit 037f91b

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.

Write Test compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Write Test this skillaviatesk/JETLS.jl	314	—	~707	Automated safety check: Pass	MIT	yesterday
Emcaklofas/kicad-happy	1.3k	1 repos	~2.8k	Automated safety check: Pass	MIT	yesterday
Swig Testswig/swig	6.3k	—	~2.3k	Automated safety check: Pass	Custom licence	today
Generate Test Cases342164796/generate-test-cases	119	1 repos	~2.9k	Automated safety check: Pass	None	6 mo ago
Verify Cc Safety Netkenryu42/cc-safety-net	1.6k	—	~2k	Automated safety check: Pass	MIT	yesterday
Wioworkersio/skills	180	—	~5.8k	Automated safety check: Pass	MIT	2 mo ago

Similar skills

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…
1.3k GitHub starsUsed in 1 repo~2.8k tokens
Testing & QAAuto-check passed
Swig Test
swig/swig
Run SWIG test suite for specific languages. An agent skill from swig/swig.
6.3k GitHub stars~2.3k tokensUpdated today
Testing & QAAuto-check passed
Generate Test Cases
342164796/generate-test-cases
自主学习型测试文档生成器。从需求文档（Markdown）生成测试用例 XMind 文件，支持持久化记忆和持续学习。当用户提到"生成测试用例"、"根据需求生成测试"时触发。
119 GitHub starsUsed in 1 repo~2.9k tokens
Testing & QAAuto-check passed
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.
1.6k GitHub stars~2k tokensUpdated yesterday
Testing & QAAuto-check passed
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.
180 GitHub stars~5.8k tokensUpdated 2 mo ago
Testing & QAAuto-check passed
File Server
microsoft/WindowsProtocolTestSuites
Official
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…
567 GitHub stars~4.1k tokensUpdated 22 days ago
Testing & QAAuto-check passed

Questions about Write Test

What does Write Test do?

A skill your agent uses when adding or modifying JETLS tests. jl. Use when adding or modifying JETLS tests.

When should I use Write Test?

Write Test fits situations like: modifying JETLS tests; tasks that involve Test generation.

How do I install Write Test in Claude Code?

Run `npx skills add aviatesk/JETLS.jl --skill write-test -a claude-code`. Or copy the skill folder (.agents/skills/write-test in aviatesk/JETLS.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/JETLS.jl --skill write-test -a codex`. Or copy the skill folder (.agents/skills/write-test in aviatesk/JETLS.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/JETLS.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 707 tokens (SKILL.md is roughly 2.8k 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/JETLS.jl, which has 314 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.

Source: aviatesk/JETLS.jl on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Write Test

Install Write Test

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Write JETLS tests

Test file structure

Organizing test code

Language-server feature tests

After writing tests

Files

Compare with similar skills

Similar skills

Emc

Swig Test

Generate Test Cases

Verify Cc Safety Net

Wio

File Server

More from aviatesk/JETLS.jl

Run Test

Changelog

Zed Agent Diagnostics

Questions about Write Test

Install Write Test

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Write JETLS tests

Test file structure

Organizing test code

Language-server feature tests

After writing tests

Files

Compare with similar skills

Similar skills

More from aviatesk/JETLS.jl

Related

Questions about Write Test