Conciseness

Mostly dense, load-bearing operational content (CLI quirks, gates, tables) with no re-teaching of concepts Claude knows, but substantial internal duplication inflates the token budget: the per-slide ghost/re-ghost rule appears in four places (Mental Model bullets, §Ghost Discipline & Actor Lifecycle, pitfall table M-2 row, Known Issues M-2), the spatial-variety thresholds (≥5cm / ≥15° / ≥30%) in four places, and the renderer caveat in four. Not 2 — sections are individually tight and non-padded; not 4 — the cross-section repetition of three core rules is a real tightening opportunity in a 539-line file.

Actionability

Fully executable throughout: copy-paste-ready bash and Python recipes with exact props ('set "/slide[N]" --prop transition=morph', 'transition=morph-slow'), grep-verified flag claims against 'officecli help', runnable jq verification loops, and a complete Gate 2-morph leak-grep. Specific examples cover the common cases (4 recipe patterns plus adjustments).

Workflow Clarity

Clear sequence (read pptx v2 → brief.md planning table BEFORE code → recipes → Gate 1–5a + 5b-morph-1..4 → outputs/delivery) with explicit validation checkpoints and feedback loops: every gate prints OK/REJECT, the COUNT-then-if/else enforcement pattern is taught, and 'never deliver with a known-open gate' plus re-verify-after-swap guidance close the loop.

Progressive Disclosure

References are clearly signaled and one level deep (§References lists decision-rules.md, pptx-design.md, morph-helpers.py/.sh, styles/INDEX.md with purpose annotations), but none of the referenced files exist in the skill's bundle, and the 539-line body inlines substantial content that clearly belongs in separate reference files (the 52-style library lookup workflow, the full pitfall and known-issue tables). Not 4 — missing bundle targets plus monolithic inline bulk are more than minor gaps; not 2 — the §References section is explicit, well-organized, and not buried.

Specificity

Concrete capability statement ('wants a .pptx with smooth cross-slide animation', 'shapes that grow / move / rotate as the slide advances', 'Output is a single .pptx') with inherited-rule enumeration, but it defines one core capability rather than a comprehensive list of multiple concrete actions. Not 3 because it goes well beyond 1-2 actions; not 5 because coverage is narrow relative to the 'multiple specific actions' anchor.

Completeness

Explicitly answers both what (single .pptx with PowerPoint Morph transitions, Keynote-style continuous motion, shapes that grow/move/rotate) and when ('Use this skill when the user wants...', full trigger list, plus a negative boundary 'DO NOT invoke for a generic deck, pitch deck, or board review without cross-slide motion').

Trigger Term Quality

Explicit trigger list with natural user phrasings and synonyms — 'morph', 'morph transition', 'smooth transition', 'continuous animation across slides', 'Keynote-style transition', 'animated slide sequence', 'shape continuity across slides' — plus the .pptx file extension. Comprehensive natural-term coverage.

Distinctiveness Conflict Risk

Clear niche (cross-slide morph motion on top of a base pptx skill) with explicit de-confliction routing — 'DO NOT invoke for a generic deck, pitch deck, or board review without cross-slide motion — route those to officecli-pptx base or officecli-pitch-deck'. Minimal conflict risk.