Content
70%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 provides dense, executable, domain-specific guidance — exact colors, formats, formula patterns, and LBO-specific pitfalls (plugs, circularity, odd-dimension sensitivity tables) — wrapped in an exceptionally clear gated workflow with validation, feedback loops, and checklists. Its weaknesses are repetition (recalc command, template mandate, and checkpoint rules each stated multiple times), a dangling intro line about MCP passages that were removed, and zero progressive disclosure: everything is inlined in one file while the paths it references don't exist in the bundle.
Suggestions
Deduplicate repeated guidance: state the recalc command once in the verification section, collapse the TEMPLATE REQUIREMENT triple-mandate into one instruction, and fold the 'Work section by section' Core Principle into the WORKING WITH THE USER checkpoints section.
Remove or rewrite the 'Data sources' opener 'Many passages below say "use the S&P Kensho MCP / Daloopa MCP / FactSet MCP"' — no such passages exist in this adapted version, so it confuses more than it informs.
Move the ~75-line verification checklist and common-errors table to a one-level-deep reference file (e.g., references/verification.md) linked from SKILL.md, and either ship examples/LBO_Model.xlsx in the bundle or drop the instruction to copy it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with domain-specific guidance and never explains concepts Claude already knows, but redundancy is beyond minor: the recalc command appears three times ("Recalculate before delivery: `python /path/to/excel-author/scripts/recalc.py ./out/model.xlsx`", "run the `excel-author` skill's `recalc.py` helper before delivery", "```python /path/to/excel-author/scripts/recalc.py model.xlsx```"), the template mandate is stated three ways in TEMPLATE REQUIREMENT ("you MUST use it as your template - do not build from scratch" / "Never decide to 'build from scratch' when a template is provided"), and the section-by-section rule appears in both Core Principles ("Work section by section, verify with user at each step") and the full WORKING WITH THE USER section. The line "Many passages below say 'use the S&P Kensho MCP / Daloopa MCP / FactSet MCP'" dangles, referencing passages that don't exist in this adapted version. | 3 / 5 |
Actionability | Concrete, executable guidance throughout: exact formula patterns ("`=-MAX(0,B4)`", "`=Assumptions!B5`", "`=B5*B6`"), exact hex colors ("#1F4E79", "#BDD7EE"), number-format strings ("`$#,##0;($#,##0);"-"`", "`0.0"x"`"), mixed-reference syntax ("`$A5` for row input, `B$4` for column input"), a symmetric axis example ("[8.0x, 9.0x, 10.0x, 11.0x, 12.0x]"), and a runnable validation command. Not a 5 because the command paths are placeholders ("`/path/to/excel-author/scripts/recalc.py`") and "`examples/LBO_Model.xlsx`" is absent from the bundle, so commands aren't literally copy-paste ready and there's no complete openpyxl code example. | 4 / 5 |
Workflow Clarity | Clear gated sequence with explicit validation, feedback loops, and checklists: "TEMPLATE ANALYSIS PHASE - DO THIS FIRST" → "Clarify Requirements First" → a three-step fill hierarchy → section gates ("After Sources & Uses → show the balanced table, confirm the plug is correct, get sign-off before building the operating model" through "After Sensitivity Tables") → "VERIFICATION CHECKLIST - RUN AFTER COMPLETION". Validation is explicit ("Must return success with zero errors") with a feedback loop ("If errors are found during verification, fix them before moving to the next section") and an extensive per-section checklist. This matches the anchor 5 example's validate-fix-retry pattern; the mild duplication of checkpoint guidance is a conciseness issue, not a sequence gap. | 5 / 5 |
Progressive Disclosure | Good in-file structure with clearly labeled sections ("DO THIS FIRST", "RUN AFTER COMPLETION"), but it's a single ~275-line monolith with no bundle: no references/, scripts/, or examples/ exist, and the referenced paths ("Copy `examples/LBO_Model.xlsx` as your starting point", the excel-author recalc script) are unresolvable in this bundle. The ~75-line verification checklist and the common-errors table are inlined where separate one-level-deep reference files would fit — matching the anchor 3 pattern of inline content that should be separate; not a 2 because section headers make the file genuinely navigable. | 3 / 5 |
Total | 15 / 20 Passed |