Content
82%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, token-efficient instruction skill that gives a complete IC memo template with sensible balance and consistency guardrails. Its main gaps are the absence of concrete examples (a sample financial or returns table) and validation steps placed as notes rather than explicit checkpoints in the workflow sequence.
Suggestions
Add a short worked example inline or in a reference file — e.g., a sample returns table (scenario, IRR, MOIC) and one example investment-thesis pillar — to make the financials guidance copy-paste concrete.
Move the tie-out check into the workflow as an explicit final step, e.g., 'Step 4: Verify — check that EBITDA bridges, sources & uses, and returns math tie before delivering; fix and re-check if not', so validation is sequenced rather than a side note.
Consider externalizing the full section-by-section memo template (Sections I–IX) into a references/template.md file, keeping SKILL.md as a tighter overview of the workflow, given the body is ~84 lines.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean bullet-list guidance that assumes Claude's competence — it uses IRR, MOIC, quality-of-earnings, sources & uses, and EBITDA bridges without explaining any of them, and every bullet carries task-specific content. Not 4 because there is no over-explanation or padding to trim; each line is part of the deliverable spec. | 5 / 5 |
Actionability | The section-by-section template ("I. Executive Summary" through "IX. Recommendation") with page counts and per-section content lists is directly actionable, and output rules are concrete ("Word document (.docx)", "Include tables for financials and returns, not just prose"). Not 5 because there are no concrete worked examples — e.g., a sample returns table, a sensitivity table format, or an example thesis pillar — leaving minor gaps between instruction and execution; not 3 because the guidance is concrete and complete enough to execute without guesswork on structure. | 4 / 5 |
Workflow Clarity | A clear three-step sequence (gather inputs → draft structure → output format) with an explicit input checklist in Step 1 and validation guidance ("Financial tables should tie — check that EBITDA bridges, S&U balances, and returns math is consistent"; "Ask for missing inputs rather than making assumptions"). Not 5 because the tie-out check and missing-input loop live in 'Important Notes' rather than as explicit sequenced checkpoints with a fix-and-recheck cycle; not 3 because the sequence is complete and validation is present, just not embedded in the step flow. | 4 / 5 |
Progressive Disclosure | Well-organized single-file skill with clean headers (Workflow, Important Notes) and no bundle files to reference; all content is needed on every invocation, so inline placement is mostly appropriate. Not 5 because at ~84 lines of body it exceeds the under-50-line simple-skill case, and the full section-by-section memo template could optionally live in a references/ template file to keep SKILL.md as a tighter overview; not 3 because nothing is misfiled or buried — the structure is coherent and navigable. | 4 / 5 |
Total | 17 / 20 Passed |