{{skill}}
{{What it does, in one sentence}}. Use when {{the trigger: the situations, in the words a task uses}}.
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- {{skill}}
- metadata
- { "pack": "{{pack}}", "layer": "{{L2 for a principle, L3 for a workflow}}" }
- description
- {{What it does, in one sentence}}. Use when {{the trigger: the situations, in the words a task uses}}.
02 资源文件 12
- 参考文档cases/fires/case.yaml85 B
- 参考文档cases/fires/graders/skill-fired.md140 B
- 参考文档cases/fires/prompt.md518 B
- 脚本cases/fixture.sh1.3 KB
- 参考文档cases/quiet/case.yaml85 B
- 参考文档cases/quiet/graders/skill-quiet.md170 B
- 参考文档cases/quiet/prompt.md570 B
- 参考文档cases/scenario/case.yaml88 B
- 参考文档cases/scenario/graders/no-mistake.md260 B
- 参考文档cases/scenario/graders/outcome.md193 B
- 参考文档cases/scenario/graders/skill-fired.md134 B
- 参考文档cases/scenario/prompt.md501 B
03 SKILL.md 正文
{{Title}}
{{The one idea, stated as the behavior to produce, in one or two sentences.}}
Why: {{the failure it prevents, as the evidence recorded it}}
Pattern:
- {{an action, ending on a condition you can check}}
- {{the next action}}
Example: {{one real instance: what went wrong at file:line, and the fix}}
Stop:
- {{an excuse recorded in the failing scenario}}: {{its counter}}
Library facts: read references/{{library}}.md when {{the moment the facts are needed}}. Drop this line when the skill needs no reference.
{{L3 only: Applies ven:<core principle>.}} Distinct from {{the nearest core or pack skill, named in plain text}}: {{the line between them}}.
04 同仓库更多 Skills
yeet
Take every local change green through the repo's own checks, slice it into conventional commits, push, and with --pr open a pull request on the code host. Use only when the user explicitly asks to yeet, or to commit and push everything; never on your own initiative.
write-docs
Write or update documentation from the code: gather facts, pick the shape for the reader, write it plain, and prove every command and path in it. Use when asked to document a repo, module or feature, or to bring stale docs up to date.
why
Find why code is shaped the way it is (design rationale, trade-offs, regressions, odd thresholds) from history, tickets, docs and chat, citing every claim and stating its confidence. Use for 'why does X work this way', 'why did we pick Y', or before changing code whose purpose is unclear.
verify
Prove a change works with the check that matches its type, do the read-back, and log the pass against the exact tree. Use when a change is ready to call done, before review, commit or stopping, and whenever ven-decisions end refuses an unverified tree.
unslop
Cut AI writing tells (filler, model vocabulary, metaphor nouns, hedging, formatting tics) from text while keeping every fact. Use when editing or checking any prose before it ships: docs, PR bodies, reports, skill text.
type-discipline
Apply when designing types or data shapes, reviewing a signature, or handling outside data, in any language. Make wrong states fail early: in the compiler for typed languages, in validated runtime contracts for untyped ones.