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.
The body is a lean, well-sequenced five-step workflow with concrete metric checklists, scenario/catalyst templates, and a defined output format, with essentially no wasted tokens. It falls just short of top marks on actionability and workflow clarity for lacking a worked example and any explicit verification step.
Suggestions
Add a worked example — e.g., one filled bull-scenario row or a sample catalyst checklist entry — so the output format is unambiguous and copy-paste ready.
Specify how to source the options-implied move (e.g., a concrete web search string, matching the one already provided for earnings reaction history).
Add an explicit verification checkpoint before writing the output, such as confirming the earnings date and estimate freshness from a second source.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is directive rather than explanatory — 'Pull consensus estimates via web search (revenue, EPS, key segment metrics)', sector-specific metric checklists, and template tables with no conceptual padding. No section explains things Claude already knows, so nothing could be trimmed without losing guidance; this matches the 'lean and efficient, every token earns its place' anchor. | 5 / 5 |
Actionability | Guidance is concrete and executable: a five-step workflow, a ready-made search string ('search for "[company] earnings reaction history"'), scenario and catalyst table templates, and a defined one-page output format. It falls short of the top anchor because there is no worked example (e.g., a filled scenario row or sample catalyst entry) and the sourcing of the options-implied move mentioned in the output spec is never specified. | 4 / 5 |
Workflow Clarity | The five steps (Gather Context, Key Metrics Framework, Scenario Analysis, Catalyst Checklist, Output) are clearly sequenced, and partial checkpoints exist ('always note the source and date of estimates', 'compare to your scenarios' for calibration). No explicit validation step is present (e.g., confirming the earnings date or estimate freshness before writing), which keeps it at 'clear sequence with most checkpoints present' rather than the top anchor. | 4 / 5 |
Progressive Disclosure | A single self-contained, well-organized file with clearly labeled step sections; the workflow needs no external references and nothing is inlined that clearly belongs in a separate file. Navigation is trivial, matching the 'well-organized sections' standard for a lean single-file skill. | 5 / 5 |
Total | 18 / 20 Passed |