Content
86%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 lean, well-structured instruction-only skill body with concrete script invocations, an explicit safety section, and exemplary progressive disclosure to real bundle files. The only gaps are a missing code example for the primary python-pptx extraction path and a dangling requirements.txt reference.
Suggestions
Ship the referenced requirements.txt (or change the line to 'pip install defusedxml') so 'Install defusedxml from requirements.txt' is not a dangling reference.
Add a minimal 3–5 line python-pptx snippet for the primary extraction contract to make the main path copy-paste ready like the OOXML commands already are.
Briefly state what to do when validate_package.py reports malformed XML or broken relationships (e.g., record the exception in the manifest and fall back to targeted unpack inspection).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 43-line body is telegraphic and dense — 'compact prompt context: slide count and size, text summaries, shape counts, styles, brand signals' — with zero explanation of concepts Claude already knows and no padding. Every line carries actionable information. | 5 / 5 |
Actionability | The OOXML section gives concrete, executable commands ('scripts/inspect.py <deck.pptx>', 'scripts/validate_package.py <deck.pptx> --output <report.json>', 'scripts/unpack.py <deck.pptx> <output-dir>'), but the primary 'Contract' path offers no code example for the task-local python-pptx extraction, and 'Install defusedxml from requirements.txt' references a requirements.txt that does not exist in the bundle. Not 3 because the provided commands are complete and runnable. | 4 / 5 |
Workflow Clarity | A clear numbered 1–4 sequence exists with a validation tool (validate_package.py) and a conditional gate ('only when raw-package evidence is necessary'), plus a manifest checkpoint ('Record inspected parts and parsing exceptions'). It misses 5 because no validate-then-fix feedback loop is described for malformed XML or broken relationships; the read-only, non-destructive nature means the destructive-cap does not apply. | 4 / 5 |
Progressive Disclosure | The body is a genuine overview that pushes output shapes, documentation-only patterns, and OOXML part maps to three real reference files (all verified to exist), each named with its purpose in a final pointer line, plus three real bundled scripts referenced inline in the workflow. References are one level deep and clearly signaled. | 5 / 5 |
Total | 18 / 20 Passed |