Network Bgp Diagnostics
affaan-m/ECC
Diagnostics-only BGP troubleshooting patterns for neighbor state, route exchange, prefix policy, AS path inspection, and safe evidence collection.
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…
MITAuto-check passed
Install Zed Agent Diagnostics
$ npx skills add aviatesk/JETLS.jl --skill zed-agent-diagnostics -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aviatesk/JETLS.jl zed-agent-diagnostics --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/zed-agent-diagnostics .claude/skills/zed-agent-diagnostics && 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 "zed-agent-diagnostics" agent skill from https://github.com/aviatesk/JETLS.jl/tree/master/.agents/skills/zed-agent-diagnostics into .claude/skills/zed-agent-diagnostics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zed-agent-diagnostics", 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/zed-agent-diagnosticsType 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 zed-agent-diagnostics -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aviatesk/JETLS.jl zed-agent-diagnostics --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/zed-agent-diagnostics .agents/skills/zed-agent-diagnostics && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "zed-agent-diagnostics" agent skill from https://github.com/aviatesk/JETLS.jl/tree/master/.agents/skills/zed-agent-diagnostics into .agents/skills/zed-agent-diagnostics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zed-agent-diagnostics", 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 zed-agent-diagnostics -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aviatesk/JETLS.jl zed-agent-diagnostics --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/zed-agent-diagnostics .cursor/skills/zed-agent-diagnostics && 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 "zed-agent-diagnostics" agent skill from https://github.com/aviatesk/JETLS.jl/tree/master/.agents/skills/zed-agent-diagnostics into .cursor/skills/zed-agent-diagnostics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zed-agent-diagnostics", 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/zed-agent-diagnostics--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 zed-agent-diagnostics -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aviatesk/JETLS.jl zed-agent-diagnostics --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/zed-agent-diagnostics .gemini/skills/zed-agent-diagnostics && 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 "zed-agent-diagnostics" agent skill from https://github.com/aviatesk/JETLS.jl/tree/master/.agents/skills/zed-agent-diagnostics into .gemini/skills/zed-agent-diagnostics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zed-agent-diagnostics", 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 zed-agent-diagnosticsInstalls 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 zed-agent-diagnostics -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/zed-agent-diagnostics .github/skills/zed-agent-diagnostics && 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 "zed-agent-diagnostics" agent skill from https://github.com/aviatesk/JETLS.jl/tree/master/.agents/skills/zed-agent-diagnostics into .github/skills/zed-agent-diagnostics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zed-agent-diagnostics", 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 zed-agent-diagnostics -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 zed-agent-diagnostics --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/zed-agent-diagnostics .opencode/skills/zed-agent-diagnostics && 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 "zed-agent-diagnostics" agent skill from https://github.com/aviatesk/JETLS.jl/tree/master/.agents/skills/zed-agent-diagnostics into .opencode/skills/zed-agent-diagnostics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zed-agent-diagnostics", 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
zed-agent-diagnostics- GitHub stars
- 314
- Token cost
- ~699 tokens
- SKILL.md length
- 367 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- SKILL.md covers Validation rule, How to use diagnostics, When diagnostics may be… and Relationship to tests, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Zed Agent Diagnostics is an agent skill from 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 selfcheck when needed.
Its SKILL.md is about 700 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.
Example prompts
- “/zed-agent-diagnostics”
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.
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
Zed Agent Diagnostics loads about 699 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 367 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). 367 words, ~699 tokens.
Download SKILL.mdSave it as
.claude/skills/zed-agent-diagnostics/SKILL.md (or your agent's skills folder).- name
- zed-agent-diagnostics
- description
- 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 selfcheck when needed.
Zed agent diagnostics
Use this skill when you are running as Zed's built-in coding agent in this
repository and need to satisfy project instructions that require jetls check
or ./scripts/selfcheck.sh.
Validation rule
When project instructions say to run jetls check or ./scripts/selfcheck.sh
after modifying code, normally satisfy that requirement by using Zed's
diagnostics tool instead of running the terminal command. Prefer it when
available because it is usually faster than starting a separate selfcheck.
Use Zed diagnostics for the initial check. Run ./scripts/selfcheck.sh only
when diagnostics cannot provide enough confidence.
How to use diagnostics
- After code edits, call the diagnostics tool for the project.
- If the changed files are known and targeted diagnostics are useful, also call the diagnostics tool for those files.
- Treat diagnostics in files you edited as issues to fix when they are likely caused by your changes.
- Do not remove or simplify meaningful code only to silence diagnostics. If a natural fix is difficult to find, explain the situation and ask the user for help.
- If diagnostics appear unrelated to your changes, report them as pre-existing or unrelated instead of fixing them opportunistically.
Show full SKILL.md (180 more words)Show less
When diagnostics may be unreliable
JETLS analyzes itself through a Revise-based server session. This is efficient, but changes to type definitions or global bindings may not be fully reflected in the running session. Zed diagnostics can therefore be stale, incomplete, or fail.
Be especially conservative when changes affect type definitions, macros,
include structure, diagnostics infrastructure, or code that diagnostics
itself depends on. If diagnostics code was edited, diagnostics may be broken
by the current changes.
If diagnostics look stale, incomplete, or broken, do not spend time on server
restart loops. Explain that Zed diagnostics do not provide enough confidence and
run ./scripts/selfcheck.sh to get a fresh check, unless the user has asked not
to run it.
Relationship to tests
This skill only changes how self diagnostics are checked. It does not replace relevant component-specific tests. When you modify testable code, still run the most specific appropriate tests as described by the project instructions.
Reporting
In the final response, say whether validation used Zed diagnostics, fell back
to ./scripts/selfcheck.sh, or used both. Summarize whether diagnostics were
clean or what issues remained.
© 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/zed-agent-diagnostics of aviatesk/JETLS.jl.
Open the folder on GitHubat commit 2ccdebd
Compare with similar skills
Zed Agent Diagnostics 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 |
|---|---|---|---|---|---|---|
| Zed Agent Diagnostics this skillaviatesk/JETLS.jl | 314 | — | ~699 | Automated safety check: Pass | MIT | |
| Network Bgp Diagnosticsaffaan-m/ECC | 275k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Triage Snmp Diagnosticsnetdata/netdata | 81k | — | ~3k | Automated safety check: Pass | GPL-3.0 | |
| Adding Ty Diagnosticsastral-sh/ruff | 50k | — | ~556 | Automated safety check: Pass | MIT | |
| Diagnostics Developmentbiomejs/biome | 26k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Zedmajiayu000/claude-skill-registry | 666 | 1 repos | ~2.4k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Triage Snmp Diagnostics
netdata/netdata
Investigate captured SNMP diagnostics and support bundles, or review diagnostics-tool and evidence-interpretation changes.
- Official
Adding Ty Diagnostics
astral-sh/ruff
A skill your agent uses when a user says "add a ty rule", "add a ty diagnostic", "write this new ty diagnostic", "change a ty error message", "review ty diagnostics", or asks to add, update, or…
- Official
Diagnostics Development
biomejs/biome
A skill your agent uses when designing or implementing Biome user-facing diagnostic presentation or APIs, including messages, advice, markup, details, code frames, categories, severity, and…
Zed
majiayu000/claude-skill-registry
Zed is a fast, GPU-accelerated code editor written in Rust, with built-in AI agent and edit predictions, real-time collaboration, Vim mode and WebAssembly extensions.
Bootstrap Diagnostics
kunchenguid/firstmate
Agent-only handling playbook for session-start bootstrap diagnostics.
More from aviatesk/JETLS.jl
Run Test
aviatesk/JETLS.jl
A skill your agent uses when choosing or running JETLS tests after code changes.
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.
Questions about Zed Agent Diagnostics
What does Zed Agent Diagnostics do?
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…. jl.sh, with fallback to selfcheck when needed.
How do I install Zed Agent Diagnostics in Claude Code?
Run `npx skills add aviatesk/JETLS.jl --skill zed-agent-diagnostics -a claude-code`. Or copy the skill folder (.agents/skills/zed-agent-diagnostics in aviatesk/JETLS.jl) into .claude/skills/zed-agent-diagnostics in your project. Claude Code loads it when a task matches its description.
How do I install Zed Agent Diagnostics in Codex?
Run `npx skills add aviatesk/JETLS.jl --skill zed-agent-diagnostics -a codex`. Or copy the skill folder (.agents/skills/zed-agent-diagnostics in aviatesk/JETLS.jl) into .agents/skills/zed-agent-diagnostics in your project. Codex loads it when a task matches its description.
Can I use Zed Agent Diagnostics 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 zed-agent-diagnostics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/zed-agent-diagnostics, .gemini/skills/zed-agent-diagnostics, .github/skills/zed-agent-diagnostics and .opencode/skills/zed-agent-diagnostics in your project.
What does Zed Agent Diagnostics need to run?
SKILL.md names no scripts, command-line tools or credentials: Zed Agent Diagnostics is instructions for the agent only.
Does Zed Agent Diagnostics 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 Zed Agent Diagnostics 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 Zed Agent Diagnostics use?
Zed Agent Diagnostics 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 Zed Agent Diagnostics use?
About 699 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 Zed Agent Diagnostics?
Skills that share tags, products or a category with Zed Agent Diagnostics: Network Bgp Diagnostics (affaan-m/ECC, 275k stars), Triage Snmp Diagnostics (netdata/netdata, 81k stars), Adding Ty Diagnostics (astral-sh/ruff, 50k stars) and Diagnostics Development (biomejs/biome, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Zed Agent Diagnostics?
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.