AGENT SKILL

template

暂无简介

License 许可
MIT
最近更新
2026-11-15
Stars
★ 0
Forks
0

02 资源文件 2

03 SKILL.md 正文

SKILL.md Template

The single source of truth for the SKILL.md skeleton every created skill uses. Copy this shape; fill the placeholders. The body is always exactly three sections in this order: # <Skill Name>, ## Rules, ## Routing.

---
name: <skill-name>
description: <what + when, third person, trigger terms. ≤ ~60 chars for the index display; ≤ 1,024 for the parser.>
when-to-use: "Use when <trigger conditions and context>."
argument-hint: "<arg> [--flag] <other-arg>"
---

# <Skill Name>

You <one paragraph: what the agent does when this skill loads>.

## Rules

Rules that apply to every step. Reference files cite these; they never restate them.

| ID | Rule | Why | Check |
|----|------|-----|-------|
| R1 | <Rule name>. <the rule, stated once — this row is its single home; detail beyond a few lines moves to a reference and the row points to it.> | <why the rule exists> | <how to check compliance> |

## Routing

| File | Purpose |
|------|---------|
| [`references/<file>.md`](references/<file>.md) | <when this reference is read>. |

How to fill each section

  • Frontmatter — name, description, when-to-use, argument-hint are the four mandatory keys. Optional keys (user-invocable, disable-model-invocation, paths, ...) are target-dependent; the full table is in references/improve/step-3-frontmatter-keys.md.
  • Rules — one named row per cross-step rule; the row is the single home for that fact. Task-conditional content belongs in a reference, not here (Rules: budget for permanent cost).
  • Routing — one table row per reference file the skill ships; the reference cell links to references/<file>.md. A single-file skill with no references omits the section.

Completion

  • SKILL.md matches this skeleton exactly: four mandatory frontmatter keys, then # <Skill Name> / ## Rules / ## Routing and nothing else in the body.

04 同仓库更多 Skills