Content
72%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 concise and well-structured for a simple operating/extension skill, but it names commands without showing how to invoke them and gives principles rather than a validated workflow, which caps actionability and workflow clarity at the mid-anchor.
Suggestions
Add one or two concrete example invocations for the key slash commands (e.g. `/branch <session> <name>` or `/compact --threshold`) so the guidance is executable rather than just enumerated.
Turn Operating Guidance into an explicit sequenced workflow with validation checkpoints (e.g. verify the branch was created before making high-risk changes; confirm compaction preserved session state).
Briefly state how to detect and recover from a failed operation (e.g. a corrupt session file or failed branch) so the workflow has a feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean ~30 lines of capability bullets and terse rules with no concept explanations or padding, matching the 'lean and efficient; assumes Claude's competence; every token earns its place' anchor. | 5 / 5 |
Actionability | Concrete slash commands are named ("/model", "/load", "/branch", "/compact", "/export") but no example invocations, parameters, or worked usage are given, and the Operating Guidance stays high-level ("Keep sessions task-focused"), matching the 'some concrete guidance but incomplete; missing key details' anchor. | 3 / 5 |
Workflow Clarity | A rough numbered sequence exists (1-4 in Operating Guidance) with an implicit checkpoint ("Branch before high-risk changes") but no explicit validation or feedback loop; because branching/compacting are potentially destructive session operations, the rubric's destructive-operation cap at 3 applies. | 3 / 5 |
Progressive Disclosure | The skill is under 50 lines with no bundle files and no need for external reference docs, and is well-organized into clearly headed sections (Capabilities, Operating Guidance, Extension Rules), satisfying the simple-skill exception that lets progressive disclosure score 5 on organization alone. | 5 / 5 |
Total | 16 / 20 Passed |