Choosing Trend Or Slope View
PostHog/posthog
Clarify how to visualize change over a time range before building a trend.
A skill your agent uses when choosing or running JETLS tests after code changes.
MITAuto-check passed
Install Run Test
$ npx skills add aviatesk/JETLS.jl --skill run-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aviatesk/JETLS.jl run-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/JETLS.jl.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/run-test .claude/skills/run-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 "run-test" agent skill from https://github.com/aviatesk/JETLS.jl/tree/master/.agents/skills/run-test into .claude/skills/run-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-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/JETLS.jl/tree/master/.agents/skills/run-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/JETLS.jl --skill run-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aviatesk/JETLS.jl run-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviatesk/JETLS.jl.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/run-test .agents/skills/run-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 "run-test" agent skill from https://github.com/aviatesk/JETLS.jl/tree/master/.agents/skills/run-test into .agents/skills/run-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-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/JETLS.jl --skill run-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aviatesk/JETLS.jl run-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviatesk/JETLS.jl.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/run-test .cursor/skills/run-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 "run-test" agent skill from https://github.com/aviatesk/JETLS.jl/tree/master/.agents/skills/run-test into .cursor/skills/run-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-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/JETLS.jl.git --path .agents/skills/run-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/JETLS.jl --skill run-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aviatesk/JETLS.jl run-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviatesk/JETLS.jl.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/run-test .gemini/skills/run-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 "run-test" agent skill from https://github.com/aviatesk/JETLS.jl/tree/master/.agents/skills/run-test into .gemini/skills/run-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-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/JETLS.jl run-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/JETLS.jl --skill run-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aviatesk/JETLS.jl.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/run-test .github/skills/run-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 "run-test" agent skill from https://github.com/aviatesk/JETLS.jl/tree/master/.agents/skills/run-test into .github/skills/run-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-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/JETLS.jl --skill run-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/JETLS.jl run-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviatesk/JETLS.jl.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/run-test .opencode/skills/run-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 "run-test" agent skill from https://github.com/aviatesk/JETLS.jl/tree/master/.agents/skills/run-test into .opencode/skills/run-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-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
run-test- GitHub stars
- 314
- Token cost
- ~498 tokens
- SKILL.md length
- 224 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when choosing or running JETLS tests after code changes.
- Running JETLS tests after code changes
- SKILL.md covers Choose the narrowest useful test, Focused iteration with…, Avoid the full suite by default and Reporting
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Run Test is an agent skill from aviatesk/JETLS.jl. Use when choosing or running JETLS tests after code changes. Prefer component-specific tests, avoid the full suite unless needed, and use TestRunner for focused iteration.
Its SKILL.md is about 500 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Running JETLS tests after code changes
Example prompts
- “/run-test”
What it can do on your machine
Read from SKILL.md and the folder at commit 2ccdebd. 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 bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
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
Run Test loads about 498 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 224 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/JETLS.jl at commit 2ccdebd, republished under its MIT licence (© aviatesk). 224 words, ~498 tokens.
Download SKILL.mdSave it as
.claude/skills/run-test/SKILL.md (or your agent's skills folder).- name
- run-test
- description
- Use when choosing or running JETLS tests after code changes. Prefer component-specific tests, avoid the full suite unless needed, and use TestRunner for focused iteration.
Run JETLS tests
Use this skill when you need to validate JETLS changes with tests or decide which test command to run.
Choose the narrowest useful test
When you changed a specific component, run the component-specific test instead of the full test suite.
Use this standard form:
julia --startup-file=no --project=test -e 'using Test; @testset "test_XXX" include("test/test_XXX.jl")'Notes:
--startup-file=noavoids loading unnecessary startup utilities.--project=testenablesJETLS_TEST_MODEfor proper test execution.
Focused iteration with TestRunner.jl
For faster iteration on a specific @testset, use
TestRunner.jl, which the test
environment depends on:
julia --startup-file=no --project=test -m TestRunner --verbose test/test_XXX.jl "testset_name"--project=test before -m keeps JETLS_TEST_MODE enabled and resolves
TestRunner through the shared workspace manifest, so the tests run with the
TestRunner bundled in JETLS. Do not use the testrunner app shim: it loads its
own TestRunner, which conflicts with the one JETLS imports.
TestRunner.jl is still experimental, but it is reliable enough to try first
when the target @testset is clear. If it fails in a way that looks specific
to TestRunner.jl, fall back to running the test file standalone.
Avoid the full suite by default
Pkg.test() takes about 3.5 minutes as of June 2026. Avoid it unless:
- Changes affect multiple components.
- The user explicitly requests the full test suite.
- You are unsure which narrower tests are relevant.
Reporting
In the final response, report the exact test command you ran and whether it passed, failed, or timed out. If you skipped tests, explain why.
© 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/run-test of aviatesk/JETLS.jl.
Open the folder on GitHubat commit 2ccdebd
Compare with similar skills
Run 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 |
|---|---|---|---|---|---|---|
| Run Test this skillaviatesk/JETLS.jl | 314 | — | ~498 | Automated safety check: Pass | MIT | |
| Choosing Trend Or Slope ViewPostHog/posthog | 40k | — | ~947 | Automated safety check: Pass | Custom licence | |
| Choosing Causalpy Methodsbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~807 | Automated safety check: Pass | Custom licence | |
| Choosing Openmed Modelsmaziyarpanahi/openmed | 5.5k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Choosing Causalpy Methodspymc-labs/CausalPy | 1.2k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Choosing A WorkflowJetBrains/thinkrail | 513 | — | ~781 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Choosing Causalpy Methods
brycewang-stanford/Auto-Empirical-Research-Skills
Choose the appropriate CausalPy experiment class from a causal question, data structure, treatment assignment, and identification assumptions.
Choosing Openmed Models
maziyarpanahi/openmed
Discover and pick the right OpenMed model for a clinical or biomedical task, domain, or language.
Choosing Causalpy Methods
pymc-labs/CausalPy
Choose the appropriate CausalPy experiment class from a causal or impact question, data structure, treatment assignment, and identification assumptions.
- Official
Choosing A Workflow
JetBrains/thinkrail
Use at the start of new project onboarding, PR lifecycle work including PR checks, or changes that require choosing product scope, user-visible behavior, or architecture.
Choosing Derivedstateof
skydoves/compose-performance-skills
A skill your agent uses to decide when Jetpack Compose derivedStateOf is the right tool and when it is pure overhead.
More from aviatesk/JETLS.jl
Write Test
aviatesk/JETLS.jl
A skill your agent uses when adding or modifying JETLS tests.
Changelog
aviatesk/JETLS.jl
Invoke before committing user-facing changes (new features, bug fixes, behavior changes) to update CHANGELOG.md.
Zed Agent Diagnostics
aviatesk/JETLS.jl
When running as Zed's built-in coding agent in JETLS, prefer the faster built-in diagnostics tool for project instructions that require jetls check or ./scripts/selfcheck.sh, with fallback to…
Questions about Run Test
What does Run Test do?
A skill your agent uses when choosing or running JETLS tests after code changes. jl. Use when choosing or running JETLS tests after code changes.
When should I use Run Test?
Run Test fits situations like: running JETLS tests after code changes.
How do I install Run Test in Claude Code?
Run `npx skills add aviatesk/JETLS.jl --skill run-test -a claude-code`. Or copy the skill folder (.agents/skills/run-test in aviatesk/JETLS.jl) into .claude/skills/run-test in your project. Claude Code loads it when a task matches its description.
How do I install Run Test in Codex?
Run `npx skills add aviatesk/JETLS.jl --skill run-test -a codex`. Or copy the skill folder (.agents/skills/run-test in aviatesk/JETLS.jl) into .agents/skills/run-test in your project. Codex loads it when a task matches its description.
Can I use Run 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 run-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/run-test, .gemini/skills/run-test, .github/skills/run-test and .opencode/skills/run-test in your project.
What does Run Test need to run?
SKILL.md names no scripts, command-line tools or credentials: Run Test is instructions for the agent only.
Does Run Test access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Run 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 Run Test use?
Run 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 Run Test use?
About 498 tokens (SKILL.md is roughly 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 Run Test?
Skills that share tags, products or a category with Run Test: Choosing Trend Or Slope View (PostHog/posthog, 40k stars), Choosing Causalpy Methods (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars), Choosing Openmed Models (maziyarpanahi/openmed, 5.5k stars) and Choosing Causalpy Methods (pymc-labs/CausalPy, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Run 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 8, 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.