CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-social-media-video

Brand-aware social media video creator. Reads brand-identity.md, ICP.md, and messaging.md to write a post/storyboard, craft an optimized Seedance 2.0 Director prompt, generate reference frames with the best available image model, and produce platform-ready video.

Quality

76%

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

Quality

Content

71%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 well-structured, highly actionable pipeline skill with concrete commands, templates, decision tables, and a complete worked example. Its weaknesses are the absence of any external reference files (forcing all lookup material inline in a long SKILL.md) and the lack of post-generation validation or error-recovery steps. Referenced script paths also don't resolve within this bundle.

Suggestions

Move the Platform Specs table, Camera Language Reference, and FPV/drone prompt-enrichment blocks into a references/ file (e.g. camera-and-platform-specs.md) and link to them from the workflow steps.

Add an explicit validation/error-recovery step after Step 5 — e.g. what to check in the generated video (duration, aspect ratio, brand consistency) and what to do if the script fails.

Document the --duration flag in the run-social-video.sh invocation block and verify the referenced script paths (core/media/generate-image.sh) are reachable from the skill's location.

DimensionReasoningScore

Conciseness

The body is dense and efficient — tables for brand files, modes, image models, and platform specs, plus a Director Brief template, with almost no explanation of concepts Claude already knows. It is not 5 because 'Prompt Quality Checklist' and 'Common Mistakes to Avoid' partially repeat each other (sound direction, vague adjectives, generic prompts), which could be trimmed.

4 / 5

Actionability

Guidance is mostly executable: concrete script invocations with flags, mode-selection tables, image-model recommendations by use case, and a full worked example with prompt text. It is not 5 because the referenced scripts (core/media/generate-image.sh, library/social/social-media-video/scripts/run-social-video.sh) do not exist in this bundle, and the example uses an undocumented '--duration 11' flag — minor gaps that keep it from copy-paste-ready throughout.

4 / 5

Workflow Clarity

The five-step Agent Execution Protocol is clearly sequenced with input-gap handling ('If a file is missing, proceed with what's available and note the gap') and a pre-flight Prompt Quality Checklist. It is not 5 because there is no validation or error-recovery after generation — no instruction on what to do if a script fails or how to verify the output video meets platform specs.

4 / 5

Progressive Disclosure

Sections are well-organized, but no bundle files exist — the ~100 lines of platform specs and camera-language lookup tables, plus the FPV/drone prompt-enrichment blocks, are inlined in a 270-line SKILL.md where they belong in reference files. It is not 4 because content that clearly should be separate (lookup/reference material) is inline; not 2 because headers and structure make it navigable.

3 / 5

Total

15

/

20

Passed

Description

71%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 highly specific, capability-rich description that clearly communicates the end-to-end pipeline from brand files to platform-ready video. Its main weakness is the absence of any 'Use when...' trigger guidance, which caps completeness and limits discoverability. Trigger terms are good but omit the platform names users would naturally mention.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to create a social media video, Reel, TikTok, Short, or product video for a brand.'

Include platform names (Instagram, TikTok, YouTube Shorts) and synonyms like 'short-form video' so natural user requests match the description.

Clarify what 'best available image model' means or drop the qualifier to avoid an unbacked claim.

DimensionReasoningScore

Specificity

The description lists multiple concrete, chained actions — 'Reads brand-identity.md, ICP.md, and messaging.md to write a post/storyboard, craft an optimized Seedance 2.0 Director prompt, generate reference frames... and produce platform-ready video' — with comprehensive coverage of the pipeline. It is not 4 because no significant capability is left unnamed; the full input-to-output flow is explicit.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent trigger guidance — the rubric explicitly caps this at 3. It is not 4 because 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Natural terms like 'social media video', 'post', 'storyboard', 'Seedance 2.0', and 'reference frames' are present, but platform names users would actually say (Instagram Reel, TikTok, YouTube Shorts) and synonyms like 'short-form video' are missing. It is not 5 because a few common natural trigger phrases are absent; not 3 because existing coverage goes well beyond generic keywords.

4 / 5

Distinctiveness Conflict Risk

The Seedance 2.0 Director prompt framing and named brand files give it a clear niche with distinct triggers, but it could overlap with generic video-generation or marketing skills. It is not 5 because the phrase 'social media video creator' alone is broad; not 3 because the technical specificity keeps conflict risk minor.

4 / 5

Total

16

/

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

.opencode/skills/muapi-social-media-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.