891 B
891 B
name, description, when_to_use, when_not_to_use, success_criteria
| name | description | when_to_use | when_not_to_use | success_criteria |
|---|---|---|---|---|
| Audit | Run a structured audit of graph quality, skill quality, and operational consistency. | User asks for review, QA, cleanup, or governance checks. | Simple one-off write/read requests. | Findings are prioritized, concrete, and tied to actionable fixes. |
Audit
Scope
- Node quality: duplicates, vague descriptions, missing dates, weak titles.
- Edge quality: missing links, weak explanations, wrong directionality.
- Dimension quality: drift, overlap, low-signal categories.
- Skill quality: trigger clarity, overlap, dead/unused skills.
Output Format
- Critical issues
- High-impact improvements
- Cleanup actions
- Optional refinements
Rules
- Prefer specific evidence over generic commentary.
- Propose the smallest high-leverage fixes first.
- Separate defects from optional polish.