Content
67%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 well-structured, genuinely actionable behavioral protocol with explicit pre/post-flight checkpoints and concrete commands, and it avoids teaching Claude things it already knows. Its main cost is redundancy: overlapping rules and checklists that restate each other inflate the token budget of a skill that is loaded every session.
Suggestions
Merge the overlapping rules (1 fabrication / 10 evidence / 14 read-before-write share the same 'verify, don't guess' root) into one rule with the strongest examples from each, cutting the always-loaded token cost.
Trim the pre/post-flight checklists to items not already stated verbatim in the rules, or drop the 'what this looks like' example lists for the rules whose failure pattern is self-evident.
Consider moving the per-rule failure examples to a single references/failures.md so the always-resident SKILL.md carries only the rules and checklists.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body uses short, punchy directives and never explains concepts Claude already knows, but at ~350 lines across 15 rules there is real overlap (rule 1 fabrication vs rule 10 evidence vs rule 14 read-before-write; the pre/post-flight checklists restate rules 1-8 nearly verbatim), so it 'could be tightened'. | 3 / 5 |
Actionability | As an instruction-only skill, concrete guidance is strong: a numbered 5-step retry procedure, specific commands ('git status', 'ls', 'journalctl'), a constraint-tracking checklist, and a banned-words list. It stops short of fully copy-paste-ready commands throughout, so it fits 'mostly executable guidance with minor gaps'. | 4 / 5 |
Workflow Clarity | Pre-flight and post-flight checklists plus a session failure escalation section provide explicit validation checkpoints around every action, and rule 9 is a fully sequenced procedure. However, the skill is a rule set rather than an ordered multi-phase workflow, and the checklists partially duplicate the rule bodies. | 4 / 5 |
Progressive Disclosure | A single-file skill with no bundle files; the numbered rule sections, headers, and checklists make it easy to navigate, and keeping an always-loaded protocol in one file is defensible. The per-rule 'what this looks like' example lists could arguably move to a reference file, which is the minor organization gap of the 4 anchor. | 4 / 5 |
Total | 15 / 20 Passed |