Content
85%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 strong, dense skill document: it leads with critical Slides-specific pitfalls and exact failure signatures, gives a well-sequenced two-phase build workflow with batch validation feedback loops, and pushes detail into six real, clearly-signaled reference files. The only notable weaknesses are moderately padded prose in the Design Thinking and speaker-notes sections and build helpers living entirely in references rather than inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Nearly all content is non-obvious, Slides-specific knowledge Claude could not know (the (240,240) appendChild offset bug, opaque SLIDE_GRID/SLIDE_ROW nodes, the exact createPage TypeError text), so most tokens earn their place. The Design Thinking and speaker-notes sections run somewhat discursive ('decide what it should *feel* like', extended prose on what good notes look like) and could be trimmed, keeping this below the lean anchor of 5. | 4 / 5 |
Actionability | The body provides copy-paste-ready JS (the getSlideGrid listing script, the font-loading text-extraction script, the SLIDE_ROW rename snippet) and concrete numbers (3-5 slides per use_figma call, ~3s validation). It stops short of anchor 5 because the core build machinery — the color-constant preamble, addFrame/addText/addRect helpers, and the batch validation script — is only pointed to in slide-gotchas.md rather than shown inline, and design guidance is necessarily qualitative. | 4 / 5 |
Workflow Clarity | The two-phase deck-building workflow is explicitly sequenced (plan with slide-by-slide layout descriptions, shared constants, layout-variety check; then batch builds of 3-5 slides) with explicit validation checkpoints and feedback loops: 'Validate every batch... If the check passes, proceed without a screenshot. If it fails, screenshot the affected slides and fix before continuing.' Batch operations carry validation, so the workflow cap does not apply; the gear-selection guidance (edits vs. structural additions vs. new decks) adds an upfront decision checkpoint. | 5 / 5 |
Progressive Disclosure | The SKILL.md body is a well-organized overview that keeps detail in six one-level-deep reference files — all verified to exist, with the inline anchors (slide-gotchas.md#position-after-appendchild-critical, slide-gotchas.md#batch-validation-script, slide-properties.md#supported-formatting) resolving to real headings. A 'Reference Docs' section gives a one-line description of each file and instructs 'Load only the references your task needs', making navigation easy. | 5 / 5 |
Total | 18 / 20 Passed |