CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-3d-logo-animation

Transform a 2D logo into a premium 3D version and animate it with professional cinematic effects.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./library/motion/3d-logo-animation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, compact recipe: concrete model IDs and prompts, a clear two-phase workflow with a user-approval checkpoint, and no bundle-file bloat. The main gaps are the missing fully-assembled CLI invocation example and the absence of retry/validation guidance for failed generations.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — a compact inputs table, two phases of concrete prompts, and brief agent notes with no concept re-teaching. It misses 5 because the H1 restates the frontmatter description verbatim and the generic curl/fallback notes add slight padding that could be trimmed.

4 / 5

Actionability

Concrete commands with model IDs ('muapi image edit' with model=nano-banana-2-edit, 'muapi video from-image' with veo3.1-fast-image-to-video), full prompt text, reference images, and aspect ratios make the guidance mostly executable. Not 5 because no fully assembled command line is shown and the curl fallback example ends in an opaque '{...}' placeholder.

4 / 5

Workflow Clarity

Phase A → user-approval checkpoint → Phase B is a clearly sequenced two-phase workflow with an explicit checkpoint ('Present the 3D logo to the user for approval'). It stops short of 5 because there is no validation or retry guidance for failed or poor-quality generations; not a destructive/batch operation, so the cap-3 rule does not apply.

4 / 5

Progressive Disclosure

The skill is short (~50 lines), needs no external reference files, and is cleanly organized into Inputs, Steps (Phase A/B), Trigger Keywords, and agent Notes — matching the rubric's exception that short, single-purpose skills with well-organized sections score 5 on progressive disclosure.

5 / 5

Total

17

/

20

Passed

Description

61%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 states a clear, concrete, appropriately niche capability in third person, but omits any explicit 'when to use this' trigger guidance, which caps completeness. Keyword coverage is good but missing natural synonyms that would live in a 'Use when...' clause.

Suggestions

Append a trigger clause, e.g. 'Use when the user wants to turn a flat/2D logo into a 3D version, animate a logo, or create a cinematic logo reveal.'

Fold the body's existing Trigger Keywords ('3d logo', 'logo animation', '2d to 3d logo', 'animated logo', 'cinematic logo') into the description so natural synonyms appear where they trigger skill selection.

Slightly broaden the 'what' with one concrete outcome detail (e.g., 'produces a 3D logo image and a 16:9 animated logo-reveal video') to lift specificity from 2 actions to several.

DimensionReasoningScore

Specificity

The description names the domain and exactly two concrete actions — 'Transform a 2D logo into a premium 3D version' and 'animate it with professional cinematic effects' — which matches the '1-2 concrete actions, but not comprehensive' anchor. It falls short of 4 because no further specifics (material options, output formats, video vs. image output) are given.

3 / 5

Completeness

The 'what' is clear (convert a 2D logo to 3D and animate it), but there is no 'Use when...' clause or equivalent trigger guidance in the description — the rubric explicitly caps completeness at 3 in that case. It is not 2 because the 'what' is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Natural user terms are present ('2D logo', '3D', 'animate', 'cinematic effects'), giving good keyword coverage, but common variations like '3D logo', 'logo animation', or 'animated logo' are absent from the description itself. Not 5 because coverage of synonyms and natural phrasings is incomplete; not 3 because the terms present are ones users would actually say.

4 / 5

Distinctiveness Conflict Risk

The 2D-to-3D logo transformation plus animation niche is clearly distinguishable with distinct triggers, but the phrasing could overlap with generic image-editing or image-to-video skills, so it is 'mostly distinct; minor overlap risk' rather than the fully minimal-conflict anchor at 5.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

SamurAIGPT/Generative-Media-Skills

Path

library/motion/3d-logo-animation/SKILL.md

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.