Content
75%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 an efficient, well-targeted set of operating rules with concrete parameter mappings and an explicit pre-save validation checkpoint. Its central flaw is that the primary reference file (references/report-formatting.md) is missing from the bundle, which both breaks navigation and hollows out the skill's detailed content.
Suggestions
Add the missing references/report-formatting.md to the bundle (or inline its essential conventions) so the body's core instruction — 'Read that guide for the requested report' — resolves to real content.
Add a short error-recovery loop after the inspection step (e.g., 'if inspection reveals broken formats or wrong values, revert or fix before re-inspecting') to lift workflow clarity.
Include one or two example MCP tool invocations (e.g., setting a header row's format via the correct control) so guidance is fully executable rather than deferring everything to the tool schemas.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 18-line body is lean and assumes Claude's competence: no explanation of what Excel or MCP is, no padding; every sentence carries operational content such as 'Preserve values, formulas, units, identifiers, existing layouts, and unrelated sheets'. The one borderline line ('it is not another required skill') still earns its place by preventing over-loading, so the anchor-5 fit holds rather than 4. | 5 / 5 |
Actionability | Concrete guidance is present: a style precedence order, and an exact parameter mapping — 'Use `table` styles for Tables, `chart_config` for charts, and `pivottable_field` for PivotTable number formats; do not apply `range_format` to Table or PivotTable cells'. Not a 5 because it contains no example tool invocations and defers specifics to 'the MCP tool schemas' and the (missing) guide; better than 3 since the instructions given are specific and executable, not pseudocode. | 4 / 5 |
Workflow Clarity | There is a discernible sequence — resolve style precedence, apply control-specific formats, preserve values, then 'Inspect the affected formats and calculated outputs before saving the authorized result' — so a validation checkpoint exists and no destructive-operation cap applies. Not a 5 because steps are not enumerated and there is no error-recovery loop after the inspection step; better than 3 because the pre-save checkpoint is explicit, not implicit. | 4 / 5 |
Progressive Disclosure | The body delegates its core detail to '[formatting guide](references/report-formatting.md)', but the bundle contains no references/, scripts/, or assets/ directories — the referenced path is dangling, so Claude following the instruction hits a dead end and the promised detailed material does not exist. Not a 3 (the reference is clearly signaled, but 'references present' fails — the file is absent); not a 1 because the body itself is well organized rather than a monolithic wall of text. | 2 / 5 |
Total | 15 / 20 Passed |