| name | guide-authoring |
| description | Authoring OR reviewing a learn/ guide (learn/benefits/*.md, learn/agentos/*.md). Enforces the grounding discipline (memory-mine + use-the-subsystem's-tools before writing), the rich-narrative + benefits + lived-voice content bar, render-verified TD Mermaid, conceptual-vs-reference separation, the never-hand-edit-generated-files rule, and a no-rubber-stamp reviewer gate. |
Guide Authoring Skill
If you are authoring OR reviewing a learn/ guide (learn/benefits/*.md, learn/agentos/*.md), you MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/guide-authoring/references/guide-authoring-bar.md before writing the first sentence or posting a review verdict.
A guide is held to a 9/10 bar: written by using the system (not inference), narrative + benefits-driven with lived voice, render-verified diagrams, reference extracted-not-inlined, and reviewed against the WHOLE bar (not the narrow required-action delta). Skipping it is the higher-cost path — MemoryCore took ~7 cycles and KnowledgeBase a rubber-stamp reversal precisely because this discipline was skipped (the operator rejects 75%+ of guides that miss it).
