Content
86%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 tight, well-structured overview that respects the token budget and sequences work clearly with pre-draft and pre-delivery checkpoints. It falls just short of top marks on actionability and workflow clarity because it offers no worked examples or templates and no explicit error-recovery loop after the Quality Gate.
Suggestions
Add one compact worked example (e.g., a sample use-of-funds table or a filled-out one-pager skeleton) so the asset guidance is copy-ready rather than purely descriptive.
Extend the Quality Gate with an explicit recovery loop: what to do when a check fails (fix the source of truth, re-run the cross-check, then re-verify before delivery).
Give the cross-check step a concrete mechanism, such as a checklist of which documents to diff against the source-of-truth inventory.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with zero padding: "If conflicting numbers appear, stop and resolve them before drafting" and the Quality Gate checklist instruct rather than explain, and no concept Claude already knows is restated. Every token earns its place. | 5 / 5 |
Actionability | Guidance is concrete (a numbered 12-slide deck flow, "bear / base / bull cases when useful", explicit red flags), but no worked examples, templates, or sample numbers are provided to make the guidance copy-ready. Fits the "mostly executable with minor gaps" anchor, not 5. | 4 / 5 |
Workflow Clarity | The Core Workflow is clearly sequenced and has a pre-draft conflict checkpoint ("stop and resolve them before drafting") plus a Quality Gate checklist, but there is no explicit loop back if the Quality Gate fails and "cross-check every number" lacks a verification mechanism. Minor validation gaps keep it at 4 rather than 5. | 4 / 5 |
Progressive Disclosure | The skill is self-contained with no bundle files and no content that clearly belongs in separate files; sections (When to Activate, Golden Rule, Core Workflow, Asset Guidance, Red Flags, Quality Gate) are well organized and the one external pointer (`frontend-slides`) is clearly signaled. Nothing is buried or nested. | 5 / 5 |
Total | 18 / 20 Passed |