Content
78%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, lean instruction skill with a clear sequenced workflow and good progressive disclosure to a real reference file. The main improvement room is making validation checkpoints explicit within the workflow rather than leaving them implicit.
Suggestions
Add an explicit verification checkpoint in the workflow (e.g., a step to confirm sources are primary and the saved Markdown renders with working source links before declaring the report complete).
Surface 1-2 of the report-framework's screening/analysis checklist items inline so the core action is executable without first opening the reference.
Tighten framing lines like 'Act as a senior investment banker: evidence-driven, structurally skeptical, and clear about uncertainty' into the Objective sentence to recover a few tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient and assumes Claude's competence — no padding about what an industry chain is — with tight bulleted steps; it falls just short of 'lean, every token earns its place' because a few framing phrases ('Act as a senior investment banker: evidence-driven, structurally skeptical...') could be trimmed. | 4 / 5 |
Actionability | Concrete, executable guidance for an instruction-only skill — 'Save under the current project's markdown/ directory', a concrete filename example, 'at least three useful visuals', 'State data cut-off date' — but the detailed company-screening/analysis checklist is delegated to the reference rather than fully specified inline, leaving minor gaps. | 4 / 5 |
Workflow Clarity | A clear six-step sequence (clarify → gather → map → select → analyze → write) with an insufficient-evidence feedback loop ('say what is missing and write a narrower report instead of inventing coverage'); validation checkpoints are mostly implicit rather than explicit, so it sits at 'clear sequence with minor validation gaps' rather than the explicit-checkpoint 5. | 4 / 5 |
Progressive Disclosure | The body is a concise overview that clearly signals one-level-deep detail in a real bundle file — 'Read references/report-framework.md before writing the report. Use it for the report structure, company screening logic, analysis checklist, visuals, and risk language.' — matching the well-signaled one-level-deep reference anchor. | 5 / 5 |
Total | 17 / 20 Passed |