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 well-organized, token-efficient instruction skill with a clear golden rule, per-asset guidance, and a pre-delivery quality gate. The gaps are in concrete anchoring: no worked examples or templates for the asset types, and the cross-check step is named but not operationalized.
Suggestions
Add one compact worked example — e.g., a filled-in use-of-funds table or deck outline with realistic sample numbers — to anchor the abstract directives in 'draft the asset with explicit logic' and 'make the ask precise'.
Operationalize the 'cross-check every number against the source of truth' step: a short procedure (list claims → map each to the source-of-truth entry → flag mismatches) would close the workflow's most explicit gap.
Specify the resolution path when conflicts surface mid-draft (who/what wins, how to update the source of truth) to turn the Golden Rule's 'stop and resolve' into a recoverable feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and efficient — terse bullet lists, zero padding, and no explanations of concepts Claude already knows (e.g., what a pitch deck is). Every section ('Golden Rule', 'Red Flags to Avoid', 'Quality Gate') earns its place with non-obvious, skill-specific guidance. | 5 / 5 |
Actionability | Concrete guidance exists in the 12-step pitch deck flow and the pre-delivery Quality Gate checklist, but some directives remain abstract ('draft the asset with explicit logic', 'make the ask precise') with no worked examples, templates, or sample numbers to anchor execution. Not a 3 (the deck flow and checklists are specific), not a 5 (no example asset demonstrates the expected output). | 4 / 5 |
Workflow Clarity | A clear 5-step core workflow exists with explicit checkpoints — 'If conflicting numbers appear, stop and resolve them before drafting' and a 'Before delivering' quality gate. Not a 5 because the workflow steps themselves are abstract ('inventory the canonical facts', 'identify missing assumptions') with no concrete procedure for the step-5 cross-check or what to do when a mismatch surfaces mid-draft. Not a 3: checkpoints are explicitly present, not implicit. | 4 / 5 |
Progressive Disclosure | A single-file skill with no bundle directories; all ~90 lines are overview-level, appropriately split into well-signaled sections, with nothing that should be offloaded to a separate file and no nested references. The 'frontend-slides' mention is a cross-skill pairing hint, not a bundle path. | 5 / 5 |
Total | 18 / 20 Passed |