Content
100%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 model of dense, high-value operational guidance: a task-routing table, mandatory recalculation with explicit validation and error-recovery loops, precise formula-selection rules, and environment-specific gotchas, all backed by real script files in the bundle. Nothing scored below the top anchor on any dimension.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section carries non-obvious, environment-specific knowledge Claude cannot be assumed to know: recalc exit-code semantics ("errors_found exits 0, so never treat a clean exit as a clean workbook"), the `_xlfn.` prefix list, spill-function truncation, and `data_only` pitfalls. There is no padding and no explanation of concepts Claude already knows; the only candidate for trimming (the external-link paragraph) delivers a distinct actionable fact per sentence. | 5 / 5 |
Actionability | Guidance is fully executable: the exact command `python scripts/recalc.py output.xlsx [timeout_seconds]`, concrete formula strings (`sheet['B10'] = '=SUM(B2:B9)'`, `='Assumptions Inputs'!$B$5`), explicit color RGB values, number-format strings (`$#,##0;($#,##0);-`), and a decision table routing each task type to an approach. | 5 / 5 |
Workflow Clarity | The workflow has explicit validation with feedback loops: recalc JSON output interpretation ("Fix what it names and run it again"), a hard ship gate ("Never ship while recalc.py reports errors_found"), a pre-build checkpoint ("Write 2–3 formulas first and check they pull the values you expect, before building out a grid"), and guidance to verify inherited vs. introduced errors. The destructive/batch cap at 3 does not apply because validation is pervasive and explicit, so the top anchor fits. | 5 / 5 |
Progressive Disclosure | The body is a well-sectioned overview whose referenced bundle files (`scripts/recalc.py`, `scripts/office/soffice.py`) exist in the bundle and are clearly signaled ("Script paths below are relative to this skill's directory"), one level deep with no nested reference chains. All inline content (gotchas, requirements, conventions) is core operational guidance that appropriately lives in SKILL.md rather than separate files. | 5 / 5 |
Total | 20 / 20 Passed |