morph-ppt

Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style continuous motion, shapes that grow / move / rotate as the slide advances. Trigger on: 'morph', 'morph transition', 'smooth transition', 'continuous animation across slides', 'Keynote-style transition', 'animated slide sequence', 'shape continuity across slides'. Output is a single .pptx. This skill is a scene layer on top of officecli-pptx — inherits every pptx v2 rule (visual floor, grid, palettes, connector canon, Delivery Gate 1–5a). 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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, operator-grade skill body with executable recipes, a thorough validation Gate, and strong defer-to-base discipline. Its main weaknesses are repeated re-statements of the ghost-accumulation rule across several sections and reliance on reference/ files that are not bundled with the skill.

Suggestions

Consolidate the ghost-accumulation / M-2 rule into one canonical section and reference it ('→ see §Ghost Discipline') from the other locations instead of restating it in Mental Model, What is Morph, Pitfalls, and Known Issues.

Bundle the referenced reference/ files (decision-rules.md, pptx-design.md, morph-helpers.py/.sh, styles/INDEX.md) or note explicitly that they live in the sibling officecli-pptx skill, so the progressive-disclosure pointers resolve to real files.

Trim the deck-length rhythm and good-enough-variety heuristics, which overlap with the stricter Gate 5b-morph-2 assertions, into a single 'creative guidance vs. gate' note to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body defers aggressively to pptx v2 ('→ see pptx v2 §X') and avoids re-teaching known concepts, but the CRITICAL ghost-accumulation / M-2 rule and the x=36cm ghost discipline are restated across four-plus sections (Mental Model, What is Morph, Ghost Discipline, Pitfalls, Known Issues), which is more than minor padding.	3 / 5
Actionability	Recipes a–d and the Gate loops are fully executable, copy-paste bash/python with exact officecli props, jq pipelines, and concrete edge-case handlers (ghost-leak loops, name-mismatch checks, raw-set M-4 example), covering the common cases.	5 / 5
Workflow Clarity	The build flow (Morph Pair Planning table → build → Delivery Gate 1–5b-morph-1..4 → validate → live-viewer motion check) is a clear sequence with explicit validation checkpoints and a real feedback loop ('If any Gate prints REJECT, fix and re-run — never deliver with a known-open gate').	5 / 5
Progressive Disclosure	In-file structure is excellent with clearly signaled one-level-deep pointers (reference/decision-rules.md, pptx-design.md, morph-helpers.py/.sh, styles/INDEX.md, skills/officecli-pptx/SKILL.md), but the referenced reference/ bundle directories are not actually present in the skill bundle, which keeps it below a 5.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary activation description: concrete capabilities, an explicit natural-language trigger list, clear what/when coverage, and explicit negative routing against sibling skills. The only nit is mild second-person framing, which matches the rubric's recommended 'Use when...' pattern rather than the penalized 'You can use this' phrasing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'smooth cross-slide animation', 'PowerPoint Morph transitions', 'shapes that grow / move / rotate', plus the inherited rule surface (visual floor, grid, palettes, connector canon, Delivery Gate) — giving comprehensive coverage rather than 1-2 actions.	5 / 5
Completeness	It explicitly answers 'what' (produces a single .pptx with morph transitions; scene layer on officecli-pptx) and 'when' (a 'Use this skill when...' clause plus a concrete trigger list and negative routing), which is the clearest anchor.	5 / 5
Trigger Term Quality	An explicit 'Trigger on:' list supplies eight natural phrases a user would actually say ('morph', 'smooth transition', 'continuous animation across slides', 'Keynote-style transition', etc.) alongside the .pptx extension, matching the comprehensive-synonyms anchor.	5 / 5
Distinctiveness Conflict Risk	It carves a narrow niche (cross-slide morph motion only) and explicitly de-scopes against sibling skills ('DO NOT invoke for a generic deck, pitch deck, or board review... route those to officecli-pptx base or officecli-pitch-deck'), minimizing conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (537 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Team-Commonly/commonly
Path: backend/commonly-bundled-skills/officecli/skills/morph-ppt/SKILL.md
Commit: e701dba

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.