CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-character-story-video

Create a multi-part animated story video by first establishing a consistent character and then generating sequential scenes and animating them.

Quality

70%

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/character-story-video/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 an efficiently structured, largely actionable recipe with clear phase sequencing and sensible user-confirmation checkpoints. Its main gaps are the absence of result-validation/retry steps for the batch scene and video generation, and prompt templates that still contain bracketed placeholders rather than fully executable examples.

Suggestions

Add validation checkpoints between phases, e.g. 'After each generation, run `muapi predict result` and retry or adjust the prompt if the output failed or lost character consistency' — this would lift workflow_clarity above the batch-operation cap of 3.

Replace the three near-identical per-scene prompt blocks with one parameterized template plus a short scene-beat table (beginning/middle/end) to remove repeated boilerplate and improve conciseness.

Include one complete executable example of a `muapi image generate` / `muapi image edit` command with real argument syntax so guidance is copy-paste ready.

DimensionReasoningScore

Conciseness

The body uses an efficient inputs table, templated prompts, and short phase descriptions with no explanation of concepts Claude already knows. Minor trimmable redundancy remains: the bold restatement of the description under the H1, the repeated 'Cinematic lighting, Pixar 3D animation style' suffix in every prompt, and the vague 'generated in parallel or sequentially depending on the story flow' note keep it below 5.

4 / 5

Actionability

Concrete guidance is present throughout: named models ('nano-banana-pro', 'flux-kontext-pro-i2i', 'kling-v3.0-pro-image-to-video'), aspect ratios, full prompt templates, and a curl fallback with polling. It is not fully copy-paste ready — prompts contain bracketed '[Describe the beginning of {{story_premise}}]' placeholders and no complete 'muapi' command example with argument syntax is shown.

4 / 5

Workflow Clarity

Phases A/B/C are clearly sequenced with user-confirmation checkpoints, but this is a batch operation (3 scenes plus 3 videos) with no validation or retry steps — nothing instructs checking that generation succeeded (e.g. via 'muapi predict result') before animating. The batch-without-validation guideline caps this at 3 even though the sequence itself is well laid out.

3 / 5

Progressive Disclosure

A single-file skill (~85 lines) with well-organized sections (Inputs, phased Steps, Trigger Keywords, agent notes) and no nested references, so structure is good. It is not 5 because the repetitive per-scene prompt templates are inlined where a small references file (or a single parameterized template) would tighten the main file.

4 / 5

Total

15

/

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 communicates a specific, multi-action capability in third-person voice without fluff, but omits any 'Use when...' trigger guidance and lacks natural synonym coverage. Adding an explicit when-to-use clause and a few common user phrasings would raise completeness and trigger quality.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user asks for a multi-part story video, an animated story with a recurring character, or sequential scene generation.'

Add natural synonyms and variations users would say, such as 'cartoon', 'storyboard', 'character consistency', or 'narrative video', to broaden trigger coverage.

Consider mentioning the optional reference-image input and part-merging capability to make the 'what' more comprehensive.

DimensionReasoningScore

Specificity

The description names the domain and several concrete actions — 'establishing a consistent character', 'generating sequential scenes', and 'animating them' — matching the 'lists several specific actions; minor gaps in coverage' anchor. It falls short of 5 because coverage is not comprehensive (no mention of merging parts, editing images, or handling a reference image).

4 / 5

Completeness

It has a clear 'what' but no 'when' — there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

'multi-part animated story video', 'character', and 'sequential scenes' are natural phrases a user might say, but common variations and synonyms ('cartoon', 'storyboard', 'narrative video', 'character consistency') are missing. It is above 2 because the keywords present are relevant, not generic filler.

3 / 5

Distinctiveness Conflict Risk

The 'first establishing a consistent character' framing gives it a clear niche distinct from generic image- or video-generation skills, leaving only minor overlap risk. It is not 5 because the phrasing could still surface for simpler single-video or character-image requests.

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/character-story-video/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.