Content
92%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, execution-focused skill body: a clearly sequenced five-step pipeline with validation and visual-review checkpoints, copy-paste-ready commands at every step, and a clean overview-to-references split verified against the actual bundle. The only weakness is minor redundancy (repeated viewport instructions, duplicated placeholder markup, and a scripts table that restates workflow commands).
Suggestions
State the 960x540 viewport requirement once (Step 2) and have Step 4 and the Troubleshooting table reference it instead of repeating the full command.
Trim the Scripts table to script name and purpose (the full invocation commands already appear in the workflow steps), and drop the duplicated placeholder HTML example from the Key constraints list since the Placeholder System section shows it.
Note that `open` is macOS-specific (e.g., suggest `xdg-open` on Linux) and add `jq` to the Prerequisites block, since both are used in the pipeline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and command-driven with no explanations of concepts Claude already knows, but contains trimmable redundancy: the viewport-setting instruction appears in Step 2, Step 4, and the Troubleshooting table; the placeholder HTML snippet is duplicated; and the Scripts table repeats full command lines already shown in the workflow steps. Not 5 because not every token earns its place; not 3 because the padding is minor and the material is otherwise tightly written. | 4 / 5 |
Actionability | Every step ships exact, copy-paste-ready commands ('agent-browser set viewport 960 540', 'cat $SKILL_DIR/scripts/validate.js | agent-browser eval --stdin --json', 'node $SKILL_DIR/scripts/build-pptx.js …'), with the {title} directory convention explained and exact numeric constraints given. The only nits (macOS-only `open`, `jq` unlisted in prerequisites) do not leave common cases without executable guidance. | 5 / 5 |
Workflow Clarity | The five-step pipeline is explicitly sequenced with an early validation gate ('Returns { "valid": true/false }. Fix any errors before proceeding'), mandatory visual checkpoints ('You MUST run `open` after each screenshot'), and a symptom/cause/fix troubleshooting table for error recovery. This matches the top anchor's explicit validation, feedback loops, and recovery guidance; not 4 because checkpoints are explicit rather than implied. | 5 / 5 |
Progressive Disclosure | The body is a genuine overview that inlines only key constraints and delegates detail to three clearly signaled, one-level-deep references (html-rules.md, slide-templates.md, pptxgenjs.md — all verified present with the promised content) plus four bundled scripts, with a closing Reference Files section for navigation. Not 4: no content that belongs in a reference is inlined and no organization gaps observed. | 5 / 5 |
Total | 19 / 20 Passed |