用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/tomevault-io/tomes --skill zed-agent-diagnostics命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
> Use when this capability is needed.
Use when writing kernel, account, or note MASM code that reads from or writes to the advice provider (advice stack / advice map) — validate advice data.
Use when writing a Rust test that exercises a failure path or a MASM test that expects a `panic` / `assert` — assert on the specific expected error variant or error code.
基于 SOC 职业分类
正在显示 SKILL.md
| name | zed-agent-diagnostics |
| description | > Use when this capability is needed. |
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.
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.
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.
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.
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.
Source: aviatesk/JETLS.jl — distributed by TomeVault.
