muapi-storyboard

Generate N keyframes for a short story or scene sequence (image only, no video).

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./library/visual/storyboard/SKILL.md

Quality

Content

72%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 lean, well-structured, and gives mostly executable guidance, but the batch keyframe-generation workflow lacks validation checkpoints and an error-recovery loop, capping workflow_clarity at 3. Progressive disclosure is excellent given the skill's compact single-file scope.

Suggestions

Add an explicit validation step after the parallel run, e.g. confirm every keyframe request succeeded via `muapi predict wait` and re-issue any failures before returning asset ids.

Provide a copy-paste-ready example of constructing one `muapi image generate` node/CLI call rather than only describing it as a 'node' in a 'plan'.

Trim minor padding such as 'these are reference keyframes, not finals' to tighten conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence (Inputs table, terse numbered steps, concrete commands), with only minor trimmable padding such as 'these are reference keyframes, not finals' and the illustrative robot prompt, matching 'Efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	It gives concrete, mostly-executable guidance — a `muapi image generate` node with model=nano-banana-2 and aspect_ratio=16:9, a prompt template, and a full curl fallback — but the 'plan'/'node' abstraction is not given as copy-paste CLI, leaving minor gaps per 'Mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	Steps 1-4 are clearly sequenced (decompose beats, create nodes, run parallel, return asset ids), but this is a batch operation (N parallel keyframes) with no validation that all generations succeeded and no error-recovery feedback loop, so per the batch-operation cap workflow_clarity cannot exceed 3.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files and no need for external references, and content is organized into clearly labeled sections (Inputs, Steps, Notes, Trigger Keywords, Notes for the Executing Agent), meeting the simple-skill exception for a top progressive_disclosure score.	5 / 5
	Total	16 / 20 Passed

Description

53%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 is specific and well-bounded for its niche but omits any explicit 'Use when' trigger guidance, which caps completeness at 3. Trigger-term coverage is reasonable but lacks the 'storyboard' synonym and other natural variations.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants a storyboard, keyframes, or scene panels for a story.'

Surface the term 'storyboard' in the description itself rather than only in the body's Trigger Keywords section.

Optionally note 1-2 additional concrete actions (e.g. 'with consistent characters across frames') to lift specificity toward 4-5.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action — 'Generate N keyframes for a short story or scene sequence' — with the boundary qualifier '(image only, no video)', but it lists only a single action rather than comprehensive coverage, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'.	3 / 5
Completeness	It clearly states the 'what' (generate N keyframes, image only) but provides no 'Use when...' trigger guidance; per the judging guidelines a missing explicit trigger clause caps completeness at 3, matching 'Has a clear what but when is missing or only weakly implied'.	3 / 5
Trigger Term Quality	It includes relevant natural terms ('keyframes', 'short story', 'scene sequence') but misses common variations and the primary synonym 'storyboard' (which only appears later in the body), aligning with 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The storyboard keyframe niche is clear and the '(image only, no video)' boundary separates it from video skills, leaving only minor overlap with general image-generation skills, matching 'Mostly distinct; minor overlap risk with closely related skills'.	4 / 5
	Total	13 / 20 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
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/visual/storyboard/SKILL.md
Commit: 3b62f78

Reviewed: 6 days 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.