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.
A strong, well-structured skill body: concrete rules with exact failure signatures, executable scripts, an explicitly validated build workflow, and exemplary one-level-deep reference organization. The main weakness is verbosity in the Design Thinking and Speaker Notes sections, which could be tightened or offloaded to references.
Suggestions
Trim the four 'Design Thinking' principles to a compact checklist and move the design philosophy detail into slide-design.md, keeping only the decision rules (inherit vs. full design mode, reference-file interpretation) in the body.
Compress the Speaker Notes section (~50 lines) to the trigger conditions and formatting constraints (speakerNotes accepts markdown; supported/unsupported syntax link), moving the craft guidance into a reference or the properties file.
The 'Sections' subsections (Naming + scoping, Renaming a section) could merge into a single tighter section since each is only 2-4 sentences.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The critical rules, gotchas, and two-phase workflow are dense, non-inferable domain knowledge, but the multi-paragraph 'Design Thinking' principles ('take a position', 'give it a signature') and ~50 lines of speaker-notes craft guidance are noticeably padded and partly inferable. It sits between anchor 3 and 4: the over-explanation spans whole sections rather than minor instances. | 3 / 5 |
Actionability | Executable inspection scripts (including correct mixed-fontName handling), a rename snippet, exact error signatures ('TypeError: figma.createPage no such property'), and anchored links to concrete helper and validation scripts. Guidance is copy-paste ready and covers the common cases. | 5 / 5 |
Workflow Clarity | The two-phase deck-building workflow sequences planning and batch execution with explicit validation checkpoints ('Validate every batch with the deterministic batch validation script... in ~3 seconds'), an error-recovery feedback loop ('If it fails, screenshot the affected slides and fix before continuing'), and screenshot checkpoints after the first and final batches. | 5 / 5 |
Progressive Disclosure | The body is a clear overview with a 'Reference Docs' section listing all six real, one-level-deep reference files with one-line descriptions, plus inline anchored links (e.g. slide-gotchas.md#position-after-appendchild-critical) that resolve to actual sections. Navigation is easy and content is appropriately split between the overview and references. | 5 / 5 |
Total | 18 / 20 Passed |