CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with a clearly sequenced, well-validated workflow, but it is long for the context budget with recurring redundancy, and its progressive disclosure is undermined by references to bundle files that are not actually provided.

Suggestions

Dedupe the M-2 ghost-accumulation rule: state it once in §Ghost Discipline & Actor Lifecycle and have the Pitfalls table and Known Issues M-2 point to it instead of re-explaining the same guidance.

Provide the referenced bundle files (reference/decision-rules.md, reference/morph-helpers.py/.sh, reference/styles/INDEX.md, and the inherited skills/officecli-pptx/SKILL.md) or remove the dangling references so navigation targets are real.

Move the verbose Gate 5b jq/loop snippets and the full pitfall table into a reference file, leaving SKILL.md as a lean overview with one-level pointers.

DimensionReasoningScore

Conciseness

Largely additive and good about deferring inherited material ('→ see pptx v2 §X'), but ~530 lines with notable redundancy — the M-2 ghost-accumulation rule and the per-slide re-ghosting guidance each recur across §Mental Model, §Ghost Discipline, the Pitfalls table, and Known Issues M-2 — so it could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready bash and python blocks with exact officecli commands and real props (e.g. `--prop 'name=!!scene-ring' --prop x=5cm`), jq readback snippets, and concrete raw-set examples — no pseudocode.

3 / 3

Workflow Clarity

Clear pre-code sequence (Setup → Help-First → pair-planning table → recipes) with explicit validation checkpoints in the Delivery Gate (Gate 1–5b OK/REJECT, COUNT-then-if/else pattern) and feedback loops (REJECT → fix → re-run) for batch/destructive operations.

3 / 3

Progressive Disclosure

References are well-signaled in prose ('→ see pptx v2 §X', a References section), but the actual bundle directories (reference/, scripts/, assets/) and the cited files (decision-rules.md, morph-helpers.py, styles/INDEX.md, skills/officecli-pptx/SKILL.md) are not present in the bundle, and the ~530-line body keeps Gate loops, recipes, and pitfalls inline where they could be split.

2 / 3

Total

10

/

12

Passed

Description

100%

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

A strong, well-targeted description: it states concrete capabilities, lists natural user trigger phrases, answers both 'what' and 'when' explicitly, and disambiguates from sibling skills via explicit routing. Written in third person with no fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'smooth cross-slide animation', 'PowerPoint Morph transitions', 'shapes that grow / move / rotate as the slide advances' — rather than vague language; matches the anchor for listing several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (a single .pptx with smooth cross-slide animation / shape continuity) and when ('Use this skill when the user wants...', 'Trigger on:'), with an explicit trigger clause rather than implying it.

3 / 3

Trigger Term Quality

Provides a rich set of natural trigger phrases a user would say ('morph', 'smooth transition', 'continuous animation across slides', 'Keynote-style transition', 'animated slide sequence', 'shape continuity across slides'), giving good coverage of natural phrasings.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche and adds explicit anti-triggers ('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'), making a wrong-skill trigger unlikely.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.