CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-one-shot-video

Generate a single continuous cinematic shot video — no cuts, one seamless flowing scene with dramatic lighting and motion.

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/one-shot-video/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.

The body is an efficient, actionable single-purpose skill: concrete model IDs, a prompt template, input handling, and a fallback path for models without CLI aliases. Main gaps are minor — a complete literal CLI invocation example, a success-check step before presenting the video, and small duplicated text.

Suggestions

Show one complete executable command, e.g. `muapi video generate --model veo3.1-text-to-video --prompt "..." --aspect-ratio {{aspect_ratio}} --duration {{duration}}`, so the flag syntax is copy-paste ready.

Add an explicit status step (e.g. `muapi predict wait <request_id>` and only present the video on success) before the 'present the video' step.

Remove the duplicated tagline under the title and the 'Emphasize "no cuts, no transitions"' note, since the prompt template already encodes that.

DimensionReasoningScore

Conciseness

The body is lean — an inputs table, one generation step, short notes, and agent notes — with no explanation of concepts Claude already knows. Minor trimming is possible: the tagline duplicates the frontmatter description verbatim, and the note 'Emphasize "no cuts, no transitions" in the prompt' repeats guidance already baked into the prompt template. This fits 'minor instances of over-explanation that could be trimmed' rather than 5's 'every token earns its place'.

4 / 5

Actionability

Concrete guidance throughout: named CLI commands with model IDs ("muapi video generate (model=veo3.1-image-to-video)"), a literal prompt template with {{placeholders}}, an auth precondition, and a fallback curl command with polling. Not 5 because the exact full command line with its flags (how prompt/aspect_ratio/duration are passed to `muapi video generate`) is never shown as a single executable invocation — the sub-bullets imply but do not spell out the syntax.

4 / 5

Workflow Clarity

The sequence is clear and unambiguous for a simple skill: gather inputs, configure auth if unset, pick the model based on whether reference_image is provided, generate, then present with follow-up suggestions. Not 5 because there is no checkpoint between submission and presenting (e.g. confirming the prediction succeeded via `muapi predict wait` in the main path, not only the fallback), leaving a minor validation gap.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and none exist (references/, scripts/, assets/ are absent and the body points to no other files). Sections are well organized (Inputs, Steps, Notes, Trigger Keywords, agent notes), which per the rubric's simple-skill guideline earns a 5 with just well-organized sections.

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 is concrete and appropriately concise, clearly stating what the skill produces, but it omits any 'when to use' trigger guidance, which limits its discoverability and caps completeness. Adding a 'Use when...' clause with synonyms like 'single take' or 'one shot' would raise both completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a one-shot video, single take, or continuous uncut footage.'

Include natural synonyms such as 'single take' or 'one take' alongside 'no cuts' and 'seamless' so common user phrasings match.

Mention the supporting capabilities (e.g. aspect ratio, duration, reference-image anchoring) briefly to broaden the 'what' beyond a single action.

DimensionReasoningScore

Specificity

Phrases like "Generate a single continuous cinematic shot video" name the domain and one concrete action, but the rest ("no cuts, one seamless flowing scene with dramatic lighting and motion") describes output qualities rather than additional capabilities. It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' — not 2 because the language is concrete rather than generic, and not 4 because no several specific actions are listed.

3 / 5

Completeness

The 'what' is clear (generate a single continuous cinematic video), but there is no 'Use when...' clause or equivalent trigger guidance; per the judging guidelines this caps completeness at 3. It is not 2 because the 'what' is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Natural terms present include "single continuous cinematic shot video", "no cuts", and "seamless", which a user asking for this would plausibly say. A few common variations ("single take", "one take", "one shot") are missing from the description itself — matching 'Good keyword coverage; a few natural terms missing' rather than 5.

4 / 5

Distinctiveness Conflict Risk

The one-shot/no-cuts framing carves a clear niche ("no cuts, one seamless flowing scene") that distinguishes it from general video-generation skills, with only minor overlap risk against a generic video generation skill. Not 5 because the boundary from a general 'generate a video' skill is not reinforced with distinct trigger phrases.

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/one-shot-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.