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.

71

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

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 thorough, highly actionable skill body with strong workflow sequencing and built-in validation gates; its main weakness is verbosity, re-teaching inherited pptx v2 material that could be deferred to the base skill, and progressive-disclosure relies on a reference/ tree that is not present in this bundle.

Suggestions

Trim the 'Inherited from pptx v2 (do NOT re-teach)' bullet block and the Shell & Execution Discipline expansion to one-line pointers — these duplicate the base skill and inflate the body; rely on the `→ see pptx v2 §X` cross-references you already use.

Consolidate the repeated ghost/accumulation warnings (Mental Model, Ghost Discipline, Pitfalls table M-2, Known Issues M-2) into a single canonical section; the same per-slide re-ghost rule is stated four times.

Verify the reference/ bundle files referenced in the body (decision-rules.md, morph-helpers.py, morph-helpers.sh, pptx-design.md, styles/INDEX.md) actually ship alongside SKILL.md, or inline the minimal essentials so progressive-disclosure is self-contained.

DimensionReasoningScore

Conciseness

Mostly efficient with copy-paste-ready recipes and tables, but at 539 lines it re-explains substantial inherited pptx v2 detail (the 'Inherited from pptx v2' bullet block, the Shell & Execution Discipline expansion, repeated caveats) that could be trimmed or deferred to the base skill.

3 / 5

Actionability

Fully executable, copy-paste-ready bash and python blocks cover the common morph cases; commands, prop names, readback queries, and jq filters are all specific and runnable, and the helper signatures are pointed to concretely.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation checkpoints (pre-code Morph Pair Planning table, Delivery Gate 1–5a plus Gate 5b-morph-1..4 proof loops, COUNT-then-if/else gate pattern, and fix-and-revalidate feedback loops).

5 / 5

Progressive Disclosure

Good structure with clearly signaled one-level-deep references to reference/ files (decision-rules.md, morph-helpers.py/.sh, styles/INDEX.md, pptx-design.md) and to the pptx base skill; the directory is absent from the bundle, so the in-file content carries more than an ideal overview would, preventing a 5.

4 / 5

Total

17

/

20

Passed

Description

95%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 excellent, trigger-rich description that crisply states what the skill produces and when to use it, with strong negative boundary guidance to avoid routing conflicts. Third-person voice is maintained throughout; the only minor gap is that the concrete action list leans on inherited-behavior framing rather than enumerating every primitive.

DimensionReasoningScore

Specificity

Names the morph domain and several concrete capabilities ('cross-slide shape-name binding', 'ghost discipline', '52-style visual library lookup') with minor coverage gaps (does not enumerate the morph animation primitives as directly as the score-5 anchor's full action list).

4 / 5

Completeness

Explicitly answers both what ('a .pptx with smooth cross-slide animation … PowerPoint Morph transitions') and when ('Use this skill when the user wants … Trigger on …') with concrete trigger phrases and a DO NOT / route-to clause for negative boundary guidance.

5 / 5

Trigger Term Quality

Comprehensive natural-keyword coverage including synonyms and variations ('morph', 'morph transition', 'smooth transition', 'continuous animation across slides', 'Keynote-style transition', 'animated slide sequence', 'shape continuity across slides') that a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (cross-slide morph motion only) with 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') minimizing conflict with sibling skills.

5 / 5

Total

19

/

20

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 (540 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
iOfficeAI/OfficeCLI
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.