Content
88%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.
An exceptionally operational skill body: exact tool calls, file names, attributes, and naming rules, sequenced into a clear pipeline with an explicit pre-save verification checklist and failure-reporting path. The only weaknesses are minor redundancy with the frontmatter description in the intro and reliance on an external skill for installation details.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with operational rules and explains no concepts Claude already knows, but the opening paragraph restates the frontmatter description ("Use this skill when the input asks to apply an existing platform template...") and "Do not load `slide-template-maker`. This skill only applies an existing platform template" duplicates the description's exclusion. These minor trimmable instances match the efficient-with-minor-over-explanation anchor rather than the every-token-earns-its-place anchor. | 4 / 5 |
Actionability | Fully actionable instruction-only guidance: exact tool calls (`install_slides_template` with the exact `template_code`, `ask_user` with enumerated choice strings), exact files to read (`template.json`, `theme.css`, `visual-spec.md`), concrete attributes (`data-width`, `data-ppt-step`, `data-ppt-effect`), and a worked naming example (`季度汇报-商务蓝-2.html`) with collision rules. Specific examples cover the common deck/slide/page-range cases. | 5 / 5 |
Workflow Clarity | The sections sequence a complete pipeline (input validation → save mode → install → apply → verify and report), and the Verify section is an explicit pre-save checklist (slide count, page scope, canvas size, content presence, resource references, step-count diff requiring explanation) for what are destructive/batch file edits. Error recovery is specified: on failure, do not silently overwrite and report the concrete failure plus retry/recovery path. | 5 / 5 |
Progressive Disclosure | The body is well-sectioned with no monolithic wall, and the one external pointer ("Reuse the installation and resource rules from `slide-template`") is clearly signaled with the key steps still enumerated inline. It falls short of 5 because the file is ~60 lines (past the simple-skill threshold where sections alone suffice) and the installation details live in another skill rather than a local reference, a minor organization gap. | 4 / 5 |
Total | 18 / 20 Passed |