CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-drone-style-video

Generate aerial drone-perspective footage — sweeping bird's-eye views, orbit shots, and flyover sequences for landscapes, architecture, and events.

Quality

79%

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

Quality

Content

85%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 tight, executable recipe: exact prompt templates per shot type, explicit model selection logic, and a raw-endpoint fallback make it directly actionable. The only real flaws are minor duplication and unspecified CLI argument syntax.

DimensionReasoningScore

Conciseness

The body is lean — a compact inputs table, one generation step, and brief notes — with no explanations of concepts Claude already knows. Not 5 because the description is restated verbatim as a bold line under the H1 and the trigger-keywords section largely duplicates routing information.

4 / 5

Actionability

Concrete commands throughout: named CLI models ('veo3.1-text-to-video', 'veo3.1-image-to-video'), literal prompt templates for all four shot types, and a copy-paste curl fallback with polling. Not 5 because the exact argument syntax for 'muapi video generate' (how prompt and aspect_ratio are passed) is never shown, leaving a minor gap.

4 / 5

Workflow Clarity

This is a simple single-purpose skill and the flow is unambiguous: gather inputs, branch on the presence of 'reference_image', build the prompt from the shot_type table, submit, then offer follow-ups — with auth setup and a polling fallback explicitly handled in the agent notes. No destructive or batch operations exist to require validation checkpoints, so the simple-skill exception applies.

5 / 5

Progressive Disclosure

The body is well under 50 lines, has no external reference files, and no content that needs splitting out — inputs, workflow, notes, and agent instructions are cleanly sectioned. Per the guideline, a short skill with no need for external references and well-organized sections scores 5.

5 / 5

Total

18

/

20

Passed

Description

66%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 clear, specific description of what the skill generates, using natural trigger language for the drone-footage niche. Its main weakness is the missing 'Use when...' guidance, which caps completeness at 3 and leaves routing intent implicit.

Suggestions

Append a trigger clause such as 'Use when the user asks for drone, aerial, bird's-eye, overhead, or flyover footage of a location or event' to satisfy the completeness requirement.

Fold one or two additional natural synonyms (e.g. 'overhead video', 'top down shot') into the description so trigger coverage doesn't depend solely on the body's keyword list.

Optionally mention the post-generation options (ambient audio, upscaling) in the description so the stated capabilities match the skill's actual scope.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — "sweeping bird's-eye views, orbit shots, and flyover sequences" — plus named subject domains ("landscapes, architecture, and events"), matching the 'several specific actions; minor gaps' anchor. Not 5 because coverage is generation-only with no mention of post-processing (audio, upscaling) that the skill actually offers.

4 / 5

Completeness

Has a clear 'what' ("Generate aerial drone-perspective footage... orbit shots, and flyover sequences") but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the 'when' is entirely absent, not merely weak.

3 / 5

Trigger Term Quality

"drone-perspective footage", "bird's-eye", "flyover", and "aerial" are natural phrases a user would say, giving good keyword coverage. Not 5 because common variations like "overhead video" or "top down" appear only in the body's trigger list, not the description.

4 / 5

Distinctiveness Conflict Risk

The drone/aerial niche is distinct with clear triggers ("drone-perspective", "bird's-eye views"), creating minimal conflict risk with most skills. Not 5 because it could still overlap with generic video-generation skills for landscape or event footage requests.

4 / 5

Total

15

/

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/drone-style-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.