Content
88%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 is a tight, actionable playbook: explicit sequencing, built-in checkpoints, concrete dialogue prompts, and a quick-reference file map, with no padding or explanations of known concepts. The one real defect is a stray trailing "enough-tooltip-text" metadata block after the Quick reference table, which costs both conciseness and structure.
Suggestions
Delete or relocate the stray trailing block ("---" followed by "enough-tooltip-text: \"…\"") after the Quick reference table — it is misplaced metadata, not body content, and is the main thing holding back both conciseness and progressive_disclosure.
If the tooltip text is genuinely needed, move it into the YAML frontmatter as a proper field so the body ends cleanly at the Quick reference table.
Tighten the intro's design flavor ("The folder is the memory; the user can disappear for weeks or years and pick up where they left off") to a single clause.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and imperative with no explanations of concepts Claude already knows, but minor extras — the design-flavor intro ("The folder is the memory; the user can disappear for weeks or years and pick up where they left off") and a stray trailing "enough-tooltip-text:" block after the Quick reference — keep it just below the every-token-earns-its-place anchor. | 4 / 5 |
Actionability | Fully executable guidance for an instruction-only skill: the exact opening question ("Where is the project folder, or should I create one?"), concrete filenames and 10 KB caps, specific unsticking prompts ("a sensory pull — smell, sound, light, weather, what they were wearing"), and a worked revision-note example ("rev 2: tightened opening, removed Aunt Beth per user"). | 5 / 5 |
Workflow Clarity | Every phase is explicitly sequenced — session-start inventory with empty/non-empty branching, numbered intake, synthesis, and the optional draft pipeline — with real checkpoints: "Summarize where things stand in one or two sentences," "List gaps and contradictions for the user to resolve," and "Pause for review between draft files. Revise on request." No destructive or batch operations, so the workflow-clarity cap does not apply. | 5 / 5 |
Progressive Disclosure | A self-contained, well-sectioned single-file skill with a Quick reference table and no external files needed; docked one point for the stray trailing "--- / enough-tooltip-text:" block — misplaced metadata in the body that breaks an otherwise clean structure (and at ~87 lines it falls outside the under-50-line simple-skill exception). | 4 / 5 |
Total | 18 / 20 Passed |