Content
81%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-structured, terse instruction skill whose gate workflow embodies exactly the validation discipline it prescribes, with concrete enums and a copy-paste output template. The main defects are a dangling spec.json reference and slight duplication between the Gate Function and Stop/Escalate rules.
Suggestions
Remove or resolve the instruction "Use the language specified in `spec.json`" — no spec.json exists in the skill bundle, so the line is unactionable and lowers both actionability and conciseness.
Deduplicate the scope-mismatch rule: Gate Function step 5 ("Reject claims that are broader than the evidence") and the NOT_VERIFIED bullet ("The claim exceeds the evidence") state the same rule twice; keep it in one place and cross-reference from the other.
Consider moving the Claim-Specific Rules detail into a short reference file (or trimming it into the gate steps) so the ~126-line body stays a lean overview, strengthening progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence: no concept re-teaching, terse sections, and a high-value "Common Rationalizations" table. It is not a 5 because there is mild redundancy — "Reject claims that are broader than the evidence" (Gate Function step 5) restates "The claim exceeds the evidence" (Stop / Escalate) — and the dangling "Use the language specified in `spec.json`" line adds a token that earns no place. | 4 / 5 |
Actionability | Guidance is mostly executable: exact claim-type enums (TASK/FIX/TEST_OR_BUILD/FEATURE_GO), a verbatim "Output Format" template, and per-claim-type requirement checklists. It falls short of fully copy-paste-ready anchor 5 because "Use the language specified in `spec.json`" references a file that does not exist in the skill, an instruction the executor cannot resolve. | 4 / 5 |
Workflow Clarity | The "Gate Function" is a numbered 7-step sequence with explicit validation checkpoints (fresh evidence, exit codes, failure counts, skipped scope), a rejection rule for scope mismatch, and explicit escalation (MANUAL_VERIFY_REQUIRED), while "Stop / Escalate" defines error-recovery outcomes for each failure mode. This matches the anchor for a clear sequence with explicit validation steps and feedback loops for error recovery. | 5 / 5 |
Progressive Disclosure | The single file is well-organized with clear section headers, logical ordering, and no nested references, and no bundle files exist to misstructure. It does not earn 5: at ~126 lines it exceeds the under-50-line simple-skill case where sections alone suffice, and "spec.json" is a referenced path with no corresponding file — a minor navigation defect consistent with anchor 4's minor organization gaps. | 4 / 5 |
Total | 17 / 20 Passed |