morph-ppt-3d

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

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./backend/commonly-bundled-skills/officecli/skills/morph-ppt-3d/SKILL.md

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 skill body is highly actionable with clear sequenced workflows and validation checkpoints, but it is a monolithic single file padded with verbose conversational discovery guidance, and it points to a styles reference that does not exist. Splitting the discovery guidance into a reference file and fixing or removing the broken '../../styles/INDEX.md' path would improve both conciseness and progressive disclosure.

Suggestions

Move the lengthy Model Discovery Flow (Steps 1–7) into a references file (e.g. model-discovery.md) and keep only the gate rule inline, to cut tokens from the main body.

Remove or correct the '../../styles/INDEX.md' reference — it does not exist on disk, so it is currently a broken pointer.

Tighten the license/token-cost reminder blocks, which repeat guidance the model already knows, to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Most content earns its tokens (commands, tables, coordinates), but the Model Discovery Flow bloats the file with multi-step conversational scripts (Steps 5–7), license reminders, and token-cost warnings that over-explain and could be tightened or externalized.	2 / 3
Actionability	The body is packed with copy-paste-ready officecli commands, a runnable Python build loop, exact model-position tables, and concrete property tables — fully executable guidance throughout.	3 / 3
Workflow Clarity	Phases are explicitly sequenced (Setup, Compatibility Gate, Discovery, Build, Verification) with validation checkpoints — Phase 4 verification, the area-ratio check, and per-slide coordinate verification form clear feedback loops.	3 / 3
Progressive Disclosure	No bundle files (references/scripts/assets) exist, so everything is inlined into one ~560-line file; the one external pointer, '../../styles/INDEX.md', does not exist on disk, making it a broken reference rather than a clean one-level-deep navigation.	2 / 3
	Total	10 / 12 Passed

Description

60%

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 concretely names the skill's capabilities but omits any explicit 'when to use' trigger guidance and relies on jargon ('morph-ppt', 'cinematographic camera') over natural user phrasing. Adding a 'Use when...' clause with plain-language triggers would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants a PowerPoint with a 3D .glb model and Morph transitions.'

Replace jargon with natural user phrasing such as '3D presentation', 'Morph transition', and 'embed a 3D model in slides'.

Make the description self-contained rather than assuming the reader already knows what 'morph-ppt' is.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions — 'GLB model insertion, cinematographic camera, model-content layout, and enriched visual design system' — matching the anchor that lists multiple specific concrete actions.	3 / 3
Completeness	It clearly answers 'what does this do' but never states 'when should Claude use it'; per the guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	It includes relevant keywords ('3D Morph PPT', 'GLB model', 'Morph') but is missing common natural variations a user would say ('3D presentation', 'Morph transition', '3D model in slides'), and contains no explicit 'Use when...' trigger phrasing.	2 / 3
Distinctiveness Conflict Risk	The 3D-GLB-Morph niche is fairly specific, but framing it as an extension of 'morph-ppt' and the lack of explicit triggers mean it could still overlap with the base morph-ppt skill for borderline requests.	2 / 3
	Total	9 / 12 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 (568 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-3d/SKILL.md
Commit: 69b6005

Reviewed: about 19 hours 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.