CtrlK
BlogDocsLog inGet started
Tessl Logo

morph-ppt-3d

3D Morph PPT — extends morph-ppt with GLB model insertion, cinematographic camera, model-content layout, and enriched visual design system.

58

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/morph-ppt-3d/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

The body is highly actionable with concrete commands and well-sequenced validation-backed workflows, but it is a long monolith that inlines reference-grade material (palettes, fonts, model-discovery scripts) that would be better split into bundle files. Trimming the chatty discovery-flow dialogue would improve token efficiency.

Suggestions

Move the color-palette table, font-pairing table, and Model Discovery Flow into separate reference files (e.g. references/palettes.md, references/model-discovery.md) and link to them from SKILL.md.

Trim the conversational scripts and token-cost/license reminders in the discovery flow to concise directives; the chatty prose is the main source of padding.

Condense redundant restatements of the no-clone rule and the area-ratio rule, which appear in both the insertion and layout sections.

DimensionReasoningScore

Conciseness

The core 3D sections (insertion rules, camera language, layout) are lean and earn their tokens, but the ~180-line Model Discovery Flow with conversational scripts, token-cost reminders, and license reminders, plus the inlined 10-palette/8-font design system, add noticeable padding.

3 / 5

Actionability

Fully executable throughout — copy-paste officecli commands with exact props, coordinate tables, a complete Python build loop, and concrete verification commands covering the common cases.

5 / 5

Workflow Clarity

Clear multi-step sequences (Compatibility Gate, 7-step Discovery Flow, Phase 2/3/4 integration) with explicit validation checkpoints — per-slide coordinate verification, a Phase 4 verification checklist, and recovery steps for the destructive clone-model case.

5 / 5

Progressive Disclosure

Good section headers and one clearly-signaled external reference (../morph-ppt/reference/styles/INDEX.md), but no bundle files exist and large reference material (10 color palettes, 8 font pairings, the full discovery flow) is inlined in a 568-line monolith rather than split into separate files.

3 / 5

Total

16

/

20

Passed

Description

58%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.

The description conveys concrete capabilities and a clear niche, but omits any 'Use when…' trigger guidance and leans on technical terms over natural user phrasings. Adding an explicit trigger clause with common synonyms would raise completeness and trigger-term quality.

Suggestions

Add a 'Use when…' clause naming natural triggers, e.g. 'Use when the user wants a PowerPoint with a .glb 3D model and Morph transitions.'

Include everyday synonyms and file extensions users actually say — 'PowerPoint', '.pptx', '3D model', '.glb' — alongside 'morph-ppt'.

Replace buzzwordy phrasing like 'cinematographic camera' and 'enriched visual design system' with concrete actions such as 'camera shot/rotation control' and 'color palettes and font pairings'.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — 'GLB model insertion, cinematographic camera, model-content layout, and enriched visual design system' — though 'cinematographic camera' and 'enriched visual design system' are slightly high-level, keeping it just below comprehensive.

4 / 5

Completeness

A clear 'what' is stated but there is no 'Use when…' trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant terms (3D Morph PPT, GLB model, morph-ppt) are present but skewed toward technical jargon; common user phrasings like 'PowerPoint with 3D model', '3D presentation', '.pptx', or '.glb' are missing.

3 / 5

Distinctiveness Conflict Risk

The 3D-Morph-PPT niche is distinct with specific triggers, but because it explicitly 'extends morph-ppt' there is minor overlap risk with that closely related skill.

4 / 5

Total

14

/

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 (568 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.