Content
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is lean, highly actionable, and structured as a clear sequenced workflow with a validation checkpoint. Its only weak spot is progressive disclosure: everything lives in one file with no references, though the inline checklists are arguably appropriate for an audit reference.
Suggestions
Consider moving the detailed model-type-specific bug lists (3g DCF/LBO/Merger/3-stmt) into a references file (e.g. model-bugs.md) linked from the main body, leaving a concise summary inline to enable progressive disclosure.
Add a short 'Quick start' or overview block at the top summarizing the four-step flow before the detailed tables, so the structure is navigable at a glance.
If the skill is expected to be used programmatically, include one or two concrete detection snippets (e.g. a formula or script to scan for #REF!/#DIV/0! or hardcoded constants) to lift actionability further.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with actionable checklists in tables and assumes Claude's competence — it never explains basic concepts like what a balance sheet or DCF is — so every token earns its place despite the length. | 3 / 3 |
Actionability | Concrete test equations ('Total Assets = Total Liabilities + Equity', 'CF Ending Cash = BS Cash') and specific bug patterns ('Discount rate applied to wrong period (mid-year vs end-of-year)') give precise guidance; as an instruction-only skill it is not penalized for lacking code. | 3 / 3 |
Workflow Clarity | The four steps (scope → formula checks → model-integrity checks → report) are clearly sequenced with an explicit validation checkpoint: 'If BS doesn't balance... nothing else matters until this is fixed.' | 3 / 3 |
Progressive Disclosure | Sections are well-organized, but the skill is a single monolithic file over 50 lines with no external references, and the detailed model-type-specific bug lists (DCF/LBO/Merger/3-stmt) are inline reference material that could be split into a deeper file; it falls short of the clear one-level-deep reference structure at the top anchor. | 2 / 3 |
Total | 11 / 12 Passed |