CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-ai-fight-scene

Generate a high-cut-density action / fight scene by first composing a 16-cell storyboard image, then driving Seedance 2.0 image-to-video off that storyboard. Stacks GPT-Image-2 (character sheet + storyboard), Nano-Banana-2 (environment concept), and Seedance 2.0 i2v.

Quality

80%

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/ai-fight-scene/SKILL.md
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 well-structured, highly actionable skill body: concrete prompts, named models, phased workflow with approval checkpoints and regeneration/recovery loops, and genuinely non-obvious craft knowledge (identity drift, cheap draft passes). The main weaknesses are minor — CLI commands never shown as complete invocations, and some duplication between the summary, pipeline diagram, and notes.

DimensionReasoningScore

Conciseness

The body is dense and nearly every section carries non-obvious, skill-specific guidance (asymmetric character details, cheap 480p draft pass, cell-by-cell regeneration strategy), matching 'efficient; minor instances of over-explanation that could be trimmed'. Not 5 because the bolded summary line repeats the frontmatter description verbatim and the ASCII 'Pipeline at a Glance' partially restates the phase structure; not 3 because nothing explains concepts Claude already knows — the model-comparison rationale is genuinely skill-specific.

4 / 5

Actionability

Each phase gives concrete, near-copy-paste artifacts: full prompt templates with {{input}} placeholders, model IDs ('gpt-image-2-text-to-image', 'nano-banana-2', 'seedance-v2.0-i2v'), aspect ratios, and a curl fallback — matching 'mostly executable guidance; concrete code or commands with minor gaps'. Not 5 because the actual `muapi` CLI invocations are described but never shown as complete command lines (flags/argument syntax are unspecified), so nothing is literally copy-paste ready.

4 / 5

Workflow Clarity

Phases A–D are clearly sequenced with explicit checkpoints after each generation ('Present the character sheet and confirm identity details look right before proceeding', 'Present for approval', 'Confirm: the 16 shots read clearly...') and explicit feedback loops for recovery ('If a panel reads poorly, regenerate just the storyboard with that cell's note bolded', 'regenerate Phase D first (cheaper than rebuilding the storyboard)'). This matches 'clear sequence with explicit validation steps; feedback loops for error recovery'.

5 / 5

Progressive Disclosure

No bundle files (references/, scripts/, assets/) exist, and the single SKILL.md is well-sectioned (Inputs, Steps, Notes, Trigger Keywords, Pipeline) with the full prompt templates appropriately kept inline — matching 'good structure; most content is appropriately placed; minor organization gaps'. Not 5 because at ~125 lines the prompt templates or the long-fight chaining note could reasonably live in a references/ file, and the duplicated Notes/summary content adds navigational noise.

4 / 5

Total

17

/

20

Passed

Description

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

A specific, distinctive description that clearly conveys the multi-model pipeline, held back mainly by the absence of any explicit 'Use when...' trigger guidance and a reliance on model jargon over natural user phrasing. The 'what' is excellent; the 'when' is entirely implicit.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks for a fight scene, action sequence, or cinematic combat video, or wants to storyboard shots before generating video.'

Add natural-language synonyms users would actually say (e.g. 'action video', 'combat choreography', 'make a fight scene') so the description matches beyond model jargon like 'Seedance 2.0 i2v'.

Move the model-stack sentence ('Stacks GPT-Image-2...') or trim it, keeping the description focused on user-facing capability and triggers rather than internal architecture.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'composing a 16-cell storyboard image', 'driving Seedance 2.0 image-to-video off that storyboard' — and names the specific models and their roles ('GPT-Image-2 (character sheet + storyboard), Nano-Banana-2 (environment concept), and Seedance 2.0 i2v'). Coverage of the full pipeline is comprehensive; it cannot sit at 4 because there are no gaps in the action list.

5 / 5

Completeness

The 'what' is clear and concrete (storyboard-then-i2v pipeline with named models), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3 ('Has a clear what but when is missing or only weakly implied').

3 / 5

Trigger Term Quality

Natural phrases a user would say are present — 'action / fight scene', 'storyboard', 'image-to-video' — which matches 'good keyword coverage; a few natural terms missing'. It falls short of 5 because common user phrasings like 'action video', 'fight choreography', or 'make a combat video' are absent while model jargon ('Seedance 2.0 i2v') dominates the second sentence.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — storyboard-driven fight-scene video generation — and the named model stack makes it unlikely to fire for generic image-generation skills, matching 'mostly distinct; minor overlap risk'. Not 5 because 'fight scene'/'action' generation could still overlap with other general video-production or image-storyboard skills.

4 / 5

Total

16

/

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/ai-fight-scene/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.