Setting the file. One moment.
Use this layout when one coherent policy, checklist, or procedure fits directly in SKILL.md.
23.10
Example Hook Backed Skill
- the skill has one dominant path
- every invocation needs roughly the same instructions
- deep optional knowledge is not the main problem
- Keep the body small enough to scan in one read.
- Put all universal steps in
SKILL.md.
- Add references only if a real branch or lookup need appears.
- most invocations need only a subset of a large knowledge base
- scripts or validators carry important runtime behavior
- routing or iterative validation is central to the skill
references/layout-inline-skill.md