Content
60%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body delivers exceptionally concrete, executable gbrain guidance with genuine validation checkpoints and consent gating for paid/destructive operations, but it is a 31KB monolith. Deep system-internal detail (dream-cycle config knobs, migration repair, heartbeat ops) is inlined instead of split into reference files, and version-numbered notes are scattered rather than isolated, hurting token efficiency and navigation.
Suggestions
Split the dream-cycle section (~150 lines of triage/rescue/cooldown/quote-verify detail) into a references/dream-cycle.md file, keeping only the invocation patterns and the Iron Law quality bar in SKILL.md.
Move the Heartbeat Integration and 'Fix a half-migrated install' sections into separate reference files and keep one-line pointers in the main body, cutting the main file to a scannable overview.
State the embedding-consent procedure once (e.g., in an 'Embedding freshness' section) and reference it from Weekly maintenance instead of repeating the commands, and consolidate version-specific notes (v0.36.4.0, v0.23, v0.11.x) into a single versioned changelog/deprecations reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | At 567 lines the body inlines ~150 lines of dream-cycle internals (triage gates, rescue knobs, cooldown semantics, issue IDs #6377/#6753) that read as system documentation rather than maintenance instructions, repeats the embedding-consent procedure verbatim in two sections, and scatters time-sensitive version numbers (v0.36.4.0, v0.23, v0.11.1+) outside any deprecated section — noticeably verbose with several padded sections. | 2 / 5 |
Actionability | Guidance is fully executable throughout: exact commands with flags and placeholders ("gbrain doctor --remediate --yes --include-repairs --expect <plan_hash> --max-usd 5"), concrete exit-code semantics (0/1/2 for autopilot, 3 for consent, 11 for budget, 17/18 for alerts), specific config keys, and copy-paste bash snippets covering the common cases. | 5 / 5 |
Workflow Clarity | The manual path is numbered with real checkpoints (health before/after, preview→consent→apply for paid repairs, exit-code gating, dry-run before embed) and a 'When it fails' recovery section, matching the clear-sequence anchor. It is not a 5 because the hierarchy is muddled: step '2. Check each dimension' is followed by dozens of same-level '###' sections never numbered as steps, and the periodic workflows (Benchmark Testing, Heartbeat Integration) sit outside any explicit sequence. | 4 / 5 |
Progressive Disclosure | No bundle files exist at all (no references/, scripts/, or assets/), and the body inlines large blocks that clearly belong in separate files — the dream-cycle configuration reference, the heartbeat integration procedures, and the half-migrated-install repair — while the few doc links point at repo-relative paths rather than organized skill references. This matches the 'content that clearly belongs in separate files is inlined' anchor. | 2 / 5 |
Total | 13 / 20 Passed |