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 content is a well-engineered operational playbook: an explicit phased workflow with validation feedback loops, concrete commands, and exact formatting specs. Its main weaknesses are notable repetition of the placeholder anti-patterns across multiple sections and a broken reference layer — the body heavily relies on four reference files that are absent from the evaluated bundle.
Suggestions
Consolidate the placeholder/anti-pattern guidance, which currently appears in four or more places (Critical Anti-Patterns, Placeholder vs. Production table, MUST Requirements, Common Failures, Final Quality Checklist), into one authoritative section with brief pointers to it.
Ship the four reference files (formatting-standards.md, slide-templates.md, xml-reference.md, calculation-standards.md) with the skill, or inline the critical content — as evaluated, every 'see reference/...' link is a dead path and the instructed 'read all reference files at task start' cannot be performed.
Move the detailed quick-reference tables (bullet symbols, hierarchy levels, rounding) into the referenced formatting/calculation files once they exist, keeping SKILL.md as a lean overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and domain-specific with no padding about concepts Claude already knows, but the placeholder/anti-pattern rules are repeated across at least four sections (Critical Anti-Patterns, the Placeholder vs. Production summary table, MUST Requirements, Common Failures, and the Final Quality Checklist), and cross-slide consistency is stated three times. This is more than the 'minor instances' of anchor 4 — the document could be meaningfully tightened by consolidating — but it is not 'severely verbose' padding, so it sits at anchor 3. | 3 / 5 |
Actionability | The body provides copy-paste-ready commands ('soffice --headless --convert-to pdf presentation.pptx', 'pdftoppm -jpeg -r 150 presentation.pdf slide'), exact numeric specs (footnote widths of 32.5cm/24cm, font-size ranges, rounding examples like '18.5 → $19bn'), and exact escalation strings ('[LOGO NOT PROVIDED - please supply company logo]'). However, the core population mechanics (how to actually edit the pptx) are delegated to xml-reference.md, leaving a minor gap in executable guidance within the body itself, which keeps it below anchor 5. | 4 / 5 |
Workflow Clarity | A decision tree routes task types, a 5-phase workflow is explicitly sequenced with a copyable progress checklist, Phase 4 is a validate → fix → repeat feedback loop with a capped 3-cycle escalation protocol, and error-handling sections cover conversion failures, data conflicts, and calculation mismatches, plus a final quality checklist. This matches the anchor-5 example of explicit validation steps, feedback loops, and checklists for a complex process. | 5 / 5 |
Progressive Disclosure | The structure is well designed: a reference-file table with per-file purposes, clearly signaled one-level-deep links with section anchors, and appropriate inline quick-reference content. However, the four referenced files (reference/formatting-standards.md, slide-templates.md, xml-reference.md, calculation-standards.md) do not exist in the evaluated bundle (no reference/ or references/ directory is present), so 'Read all reference files at task start' points at unresolvable paths. Against the actual bundle structure this is a real navigation failure, not the 'minor organization gaps' of anchor 4, placing it at anchor 3 — though the in-document organization itself is good. | 3 / 5 |
Total | 15 / 20 Passed |