Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, concise skill body with a strong sequenced workflow and explicit viewport-fit validation gate. Its main weaknesses are that all executable implementation detail is deferred to a non-existent STYLE_PRESETS.md and no concrete starter code is provided inline, leaving the build step more descriptive than actionable.
Suggestions
Add an inline executable starter — a viewport-safe CSS base block and a minimal JS presentation-controller (keyboard/wheel/touch + Intersection Observer) — so the build step is copy-paste ready rather than deferred.
Provide the missing STYLE_PRESETS.md bundle file (preset catalog, mandatory CSS block, density limits) so every 'read STYLE_PRESETS.md' reference resolves; currently all of them point to an absent file.
Include a short python-pptx extraction snippet (text, images, notes) in the PPT/PPTX section to make the conversion fallback workflow actionable instead of merely naming the library.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and well-organized; it does not explain HTML/CSS/JS basics Claude already knows, and every section earns its place (density table, validation sizes, anti-patterns). Could not go below 3 since no padding or concept re-explanation is present. | 3 / 3 |
Actionability | It names what to include ('keyboard navigation', 'reveal-on-enter animation triggers', 'height: 100vh; height: 100dvh; overflow: hidden') and a preferred library ('python-pptx'), but provides no executable code or copy-paste starter (CSS base, JS controller, extraction snippet), deferring all implementation to a STYLE_PRESETS.md that is not in the bundle. Not score 1 because some concrete CSS rules are present; not score 3 because the guidance stays descriptive rather than executable. | 2 / 3 |
Workflow Clarity | A clear 7-step sequence (Detect → Discover Content → Discover Style → Build → Enforce Viewport Fit → Validate → Deliver) with an explicit validation checkpoint at Step 6 across five viewport sizes and a hard gate in Step 5; PPT conversion includes a fallback branch. Not below 3 because validation and feedback are explicit. | 3 / 3 |
Progressive Disclosure | The body is sectioned and references STYLE_PRESETS.md with clear one-level-deep signaling, but no references/ assets/ or scripts/ bundle exists, so the repeatedly-cited STYLE_PRESETS.md is a broken reference. Not score 1 because the SKILL.md itself is well organized; not score 3 because the referenced detail file does not resolve. | 2 / 3 |
Total | 10 / 12 Passed |