Content
75%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.
A well-built instruction-only skill body: concrete commands, a validated dry-run-then-apply transaction workflow with hash-pinned approval, fail-closed handling of corrupt configuration, and clearly signaled references. The main improvements are deduplicating the repeated no-migration guarantees, specifying the actual repair command for invalid mode.json, and showing how the approval hash is derived.
Suggestions
State the no-migration guarantee once (e.g., in the intro) and reference it thereafter; it is currently repeated across the intro, the routing section, and the Change mode section.
Replace "repair it through a reviewed configuration operation" with the concrete command or procedure to run when .vault-meta/mode.json is invalid, since the fail-closed path is currently unactionable.
Show how approved_plan_sha256 is obtained from the dry-run preview output (e.g., which field to copy), completing the copy-paste chain for the apply command.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and command-first with useful tables, but the no-migration guarantee is repeated three times ("It does not write knowledge pages or move existing notes", "Never bulk-create folders, move notes...", "switching mode never rewrites existing notes" plus the migration-needs-a-plan statement appearing twice), and the advisory Checkpoint section is mildly padded. This is efficient-with-minor-trim, matching anchor 4 rather than the every-token-earns-its-place lean of anchor 5. | 4 / 5 |
Actionability | Concrete, mostly copy-paste-ready bash commands cover get/config/route and the dry-run-then-apply mode change with full flags and hash pinning. Two gaps hold it below anchor 5: the invalid-mode.json path says only "repair it through a reviewed configuration operation" with no command, and how "approved_plan_sha256" is obtained from the preview is not shown. | 4 / 5 |
Workflow Clarity | The mode change is a numbered six-step sequence with explicit checkpoints: dry-run preview first, pinned UTC timestamp and operation ID, "Copy its approved_plan_sha256 only after review", and apply by regenerating the exact plan — validation is present, so the destructive/batch cap does not apply. It falls short of anchor 5 because there is no explicit error-recovery loop (e.g., what to do on hash mismatch or a failed apply) and the fail-closed repair procedure is left vague. | 4 / 5 |
Progressive Disclosure | A well-sectioned ~116-line overview with clearly signaled, one-level-deep references (seven template links and the operation-transactions contract), each annotated with when to use it. No bundle files exist in references/scripts/assets to back the referenced paths, and the transaction-workflow detail is inlined, which leaves minor organization gaps consistent with anchor 4 rather than the fully well-split structure of anchor 5. | 4 / 5 |
Total | 16 / 20 Passed |