Content
77%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 well-organized, actionable skill body with an unusually strong mandatory validation/feedback loop and concrete design data, weakened mainly by progressive-disclosure references (editing.md, pptxgenjs.md) that point to files absent from the bundle, leaving the two core workflows under-detailed in the main file.
Suggestions
Add the missing editing.md and pptxgenjs.md files (or inline their key steps into SKILL.md) so the '阅读 [editing.md]' and '阅读 [pptxgenjs.md]' references resolve to real content.
Expand the core editing workflow from the terse '解包 → 操作幻灯片 → 编辑内容 → 清理 → 打包' arrow chain into per-step commands, mirroring the explicitness of the reading section.
Consider moving the large color-scheme/font-pairing tables into a reference file referenced from the design section to tighten the main SKILL.md, keeping only the guidance principles inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with concrete, skill-specific data (exact hex palettes, font pairings, pt sizes, inch margins) rather than concept explanations Claude already knows; the lengthy design/avoid sections earn their place but could be trimmed slightly. Not a 5 because the design guidance section is long enough that a few tokens don't earn their place. | 4 / 5 |
Actionability | Provides copy-paste executable commands ('python -m markitdown presentation.pptx', 'python scripts/thumbnail.py …', 'python scripts/office/unpack.py …', the soffice/pdftoppm pipeline, a ready-to-use subagent visual-check prompt); minor gaps because the editing and from-scratch workflows delegate to editing.md/pptxgenjs.md, which are referenced but not present in the bundle. | 4 / 5 |
Workflow Clarity | The mandatory 质量检查 section gives an explicit validate→fix→re-verify feedback loop with a content check (markitdown + grep for placeholder residue), a visual subagent check, and a 'do not declare success before one fix-verify cycle' rule — matching the checklist/feedback-loop anchor. The core editing arrow-flow is terse but the validation loop, which is the fragile part for document manipulation, is excellent. | 5 / 5 |
Progressive Disclosure | Good top-level structure (quick-reference table, clearly signaled one-level references to editing.md and pptxgenjs.md), but those referenced files do not exist in the bundle, so the split is non-functional and the detailed content is unreachable — references present and signaled but broken against the actual file listing. | 3 / 5 |
Total | 16 / 20 Passed |