Content
56%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 SKILL.md is well-organized with a clear workflow, useful tables, and a genuinely good progressive-disclosure design — but the bundle undercuts it: all four referenced detail files are missing, so the actual instructions the skill promises cannot be loaded. Redundant sections (duplicated file lists, Do/Don't repeats, time estimates) also dilute token efficiency.
Suggestions
Add the missing bundle files (methodology.md, adversarial.md, reporting.md, patterns.md) or inline the essential per-phase steps into SKILL.md — as shipped, the decision tree and links point to files that cannot be read.
Remove the duplicated file listing ('Supporting Documentation' repeats the Decision Tree entries) and merge the 'Tips for Best Results' Do/Don't lists into the Quality Checklist and Red Flags sections.
Drop the wall-clock time estimates in Example Usage ('~30 minutes', '~6-8 hours') — they are not actionable for Claude and add tokens without guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient (compact tables for risk levels, size strategy, rationalizations), but includes several sections that could be tightened: the referenced-file list is duplicated in both the Decision Tree and 'Supporting Documentation', the Do/Don't lists largely repeat the Quality Checklist and Red Flags, and wall-clock estimates like 'Time: ~30 minutes' and 'Time: ~6-8 hours' add no actionable value. This fits the anchor of 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trimming anchor of 4. | 3 / 5 |
Actionability | Some guidance is concrete — the risk-level trigger table, codebase-size thresholds ('SMALL (<20 files)'), red-flag escalation rules, and the executable issue-writer command — but the phase-by-phase instructions the workflow depends on are delegated to methodology.md, adversarial.md, reporting.md, and patterns.md, none of which exist in the bundle. Key execution details are therefore missing, matching the 'some concrete guidance but incomplete; missing key details' anchor rather than the mostly-executable anchor of 4. | 3 / 5 |
Workflow Clarity | The workflow is clearly sequenced ('Pre-Analysis → Phase 0: Triage → ... → Phase 6: Report'), the decision tree routes users to the right phase, the Quality Checklist provides verification checkpoints before delivery, and Red Flags define explicit escalation triggers. It is not a 5 because per-phase steps and error-recovery loops are not in the body — they are promised in files absent from the bundle, leaving minor validation gaps. | 4 / 5 |
Progressive Disclosure | References are clearly signaled, one level deep, and duplicated in the Decision Tree and Supporting Documentation sections — structurally a 4. However, scoring against the actual bundle, none of the four referenced files (methodology.md, adversarial.md, reporting.md, patterns.md) exist; only an unreferenced assets/trail-of-bits-mark.svg is present. The claimed file split does not exist, so the structure fails to deliver on its navigation promises. | 3 / 5 |
Total | 13 / 20 Passed |