CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, fully actionable, well-sequenced recipe with explicit validation checkpoints and error-recovery loops, and it is appropriately self-contained given there are no bundle files to reference.

DimensionReasoningScore

Conciseness

The body is lean and purposeful: it conveys only non-obvious domain knowledge (the cut-density insight, why Nano-Banana-2's spatial reasoning, why a storyboard image beats text) and avoids filler about concepts Claude already knows, matching the 'every token earns its place' anchor.

3 / 3

Actionability

Each phase gives concrete executable commands (muapi image generate / image edit / video from-image) with model IDs, full copy-paste prompts with {{placeholders}}, aspect ratios, multi-reference wiring, and a curl fallback — fully executable, not pseudocode.

3 / 3

Workflow Clarity

A clear Phase A→B→C→D sequence with explicit validation checkpoints ('Present... and confirm identity details', 'Present for approval', 'Confirm: 16 shots read clearly') and feedback loops ('If a panel reads poorly, regenerate...', 'If cut density feels too low, regenerate Phase D first'), matching the anchor-3 example.

3 / 3

Progressive Disclosure

No bundle files exist, so the skill is a single self-contained file organized into clean sections (Inputs, phased Steps, Notes, Trigger Keywords, Pipeline diagram, Notes for the Executing Agent) with no nested references — well-organized structure as the guideline allows for self-contained skills.

3 / 3

Total

12

/

12

Passed

Description

67%

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 is specific, distinctive, and uses third-person voice, but it is missing an explicit 'when to use' trigger clause and leans on product jargon over the natural phrasings a user would actually say.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a fight scene, action sequence, cinematic combat, or wants to turn a storyboard into video.'

Lead the description with natural user-facing terms ('fight scene', 'action sequence', 'storyboard to video') before the model-stack detail, so trigger coverage reaches the full anchor-3 set.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Generate a high-cut-density action / fight scene', 'composing a 16-cell storyboard image', 'driving Seedance 2.0 image-to-video' — and names the specific stacked models, matching the 'multiple specific concrete actions' anchor rather than the partial domain+actions anchor at 2.

3 / 3

Completeness

Clearly answers 'what' (compose storyboard → drive i2v, named model stack) but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Description includes some natural terms a user would say ('fight scene', 'storyboard') but mixes them with product jargon ('Seedance 2.0 i2v', 'Nano-Banana-2') and lacks the broader natural-term coverage seen at anchor 3.

2 / 3

Distinctiveness Conflict Risk

'high-cut-density action / fight scene' plus '16-cell storyboard' and 'Seedance 2.0 i2v' form a clear narrow niche with distinct triggers unlikely to fire for the wrong skill.

3 / 3

Total

10

/

12

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
SamurAIGPT/Generative-Media-Skills
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.