CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-cinema-director

Direct high-fidelity cinematic video with AI — translates creative intent into technical cinematographic directives for Veo3, Kling, and Luma video models via muapi.ai

Quality

64%

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 ./.opencode/skills/muapi-cinema-director/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 well structured with useful intent-mapping tables and a prompt-expansion formula, but every dimension lands at the middle anchor: it defines concepts Claude already knows, its example command is syntactically broken, the workflow lacks validation/error-handling checkpoints, and it references scripts that are missing from the bundle.

Suggestions

Fix the bash example by adding '\' line continuations (or putting it on one line) and show the expected output including the request_id, so the invocation is copy-paste executable.

Ship the referenced scripts (scripts/generate-film.sh, core/platform/check-result.sh) in the bundle or remove/correct the references — currently the core workflow points to nonexistent files.

Replace the glossary-style definitions of standard camera/lens terms with the model-specific syntax they should produce, and give one worked example of a raw prompt expanded via the Technical Infusion formula.

Make Step 3 concrete: include the actual check-result.sh polling command, expected completion response, and what to do on failure or timeout.

DimensionReasoningScore

Conciseness

Mostly efficient tables and formulas, but it defines standard cinematography terms Claude already knows ('Dolly In/Out: Physical camera movement on a track...', 'Shallow DOF: Background blur (Bokeh)') and the 'Core Competencies' section duplicates content from the Intent Mapping Table and Prompt Optimization Protocol.

3 / 5

Actionability

There is a concrete bash invocation with flags, but the example command is broken as written (multi-line invocation missing '\' continuations), references scripts absent from the bundle, and provides no example of an expanded prompt or expected script output — matching 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The three-step protocol (define brief → invoke script → poll result) has a clear sequence, but Step 1 is vague ('Provide the agent with a subject and a Director's Intent'), and Step 3 gives no polling command, interval, or failure handling, leaving checkpoints implicit.

3 / 5

Progressive Disclosure

Sections are well organized with clear headers, but the body references 'scripts/generate-film.sh' and 'core/platform/check-result.sh' — neither file exists in the bundle (no scripts/ directory), so the core workflow is unverifiable and navigation is broken.

3 / 5

Total

12

/

20

Passed

Description

65%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 distinct, specific description that clearly states what the skill does and which models it targets, but it entirely lacks a 'when to use' trigger clause and misses common user phrasings like 'generate video' or 'text-to-video'. Adding explicit trigger guidance would lift its two lowest-weighted dimensions.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks to generate, direct, or create cinematic video with AI, or mentions Veo3, Kling, Luma, or muapi.ai' — the missing trigger clause currently caps completeness at 3.

Include natural user phrasings such as 'generate video', 'text-to-video', and 'AI video generation' as trigger synonyms alongside the model names.

Enumerate a couple more concrete actions (e.g., 'maps emotional intent to framing, movement, and lighting; expands raw prompts into technical shot directives') to raise specificity from 1-2 actions toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('high-fidelity cinematic video') and 1-2 concrete actions ('translates creative intent into technical cinematographic directives'), but does not enumerate several specific actions like shot composition, prompt expansion, or model selection that would reach anchor 4.

3 / 5

Completeness

The 'what' is clear (translating creative intent into cinematographic directives for named video models), but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the judging guideline.

3 / 5

Trigger Term Quality

Includes strong natural triggers — 'cinematic video', 'Veo3', 'Kling', 'Luma', 'muapi.ai' — that users would actually say when requesting AI video generation, though common variations like 'generate video', 'text-to-video', or 'AI video' are missing.

4 / 5

Distinctiveness Conflict Risk

Naming three specific video models (Veo3, Kling, Luma) and the muapi.ai platform carves a clear niche with distinct triggers and minimal overlap risk against generic video or media skills.

5 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

SamurAIGPT/Generative-Media-Skills

Path

.opencode/skills/muapi-cinema-director/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.