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.
A dense, highly actionable PPTX authoring skill with explicit verification feedback loops and no padding, held back only by the absence of complete copy-paste code examples and a self-contained structure that could optionally split detail into references.
Suggestions
Add one complete executable python-pptx snippet (e.g., slide-size setup + a title/body slide) so common cases are copy-paste ready.
Consider moving the detailed font/autofit/crop rules into a short references file linked from the body, reducing density while keeping the overview lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body assumes Claude knows python-pptx and PowerPoint, giving only constraint-level guidance with specific pt sizes and API names; there is no concept explanation or padding, fitting the 'lean and efficient; every token earns its place' anchor. | 5 / 5 |
Actionability | Guidance is concrete with specific APIs (text_frame.word_wrap, fit_text, add_picture, crop-fraction constraints) and parameters, but there are no complete copy-paste code blocks, leaving it just below the 'fully executable, copy-paste ready' anchor. | 4 / 5 |
Workflow Clarity | The build → local-assertion checklist → verify_artifact → save_artifact sequence has explicit validation checkpoints and a feedback loop ('fix all blockers… rerun local checks, regenerate, reverify; if a blocker remains, stop and explain'), matching the top anchor. | 5 / 5 |
Progressive Disclosure | Content is well-organized into clear sections (Authoring rules, Revisions, Verify and save) with no nested or buried references, but it is a dense self-contained block over 50 lines with no external references, sitting between the 'good structure' and 'clear overview with one-level-deep references' anchors. | 4 / 5 |
Total | 18 / 20 Passed |