CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-ai-clipping

Turn a long video into N viral-ready short clips with a single managed API call. Wraps muapi.ai's `/ai-clipping` endpoint, which handles transcription, highlight ranking through a virality framework (hook / emotional peak / opinion bomb / revelation / conflict / quotable / story peak / practical value), overlap dedupe, and vertical face-tracking auto-crop server-side. No local Whisper, no local LLM, no GPU.

Quality

69%

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-ai-clipping/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 highly actionable with executable commands, a complete schema, error-recovery guidance, and explicit done criteria. Its main weaknesses are padding in the server-side taxonomy section, an inconsistent and unresolvable script path, and no per-item validation for the batch pattern.

Suggestions

Trim the eight-bullet virality-framework breakdown (or move it to a reference file) — the agent cannot tune those knobs and the ranking rationale already comes back in the output's virality_reason field.

Use one consistent, existing script path throughout (Step 3 uses 'library/edit/ai-clipping/scripts/run-ai-clipping.sh' while the patterns call a bare 'run-ai-clipping.sh') and ship the script in the bundle.

Add a validation checkpoint for the batch pattern (e.g., check each run's exit status or result count before continuing with xargs).

DimensionReasoningScore

Conciseness

The body is mostly efficient tables and commands, but the eight-bullet virality-framework taxonomy under 'What Happens Server-Side' explains server internals the agent cannot influence (redundant with mistake #4, "those knobs aren't exposed"), and the 'no ffmpeg / no local Whisper / no GPU' point is repeated across the intro and Step 2. This matches the 'mostly efficient but includes some unnecessary explanation' anchor, below level 4's 'minor instances'.

3 / 5

Actionability

The skill provides copy-paste-ready bash invocations, a complete input flag table, a concrete JSON output schema, and per-case patterns (defaults, batch, async, local file, coords-only). It is not a 5 because the script path is inconsistent — "library/edit/ai-clipping/scripts/run-ai-clipping.sh" in Step 3 versus bare "run-ai-clipping.sh" in the patterns — and the script file does not exist in the bundle.

4 / 5

Workflow Clarity

A clear sequence exists (collect inputs → verify prerequisites → run → done criteria) with failure-mode recovery loops (re-fetch by request_id, bump --poll-timeout, upload then retry). It falls short of 5 because the batch pattern (xargs -a urls.txt) lacks per-item failure validation and verification is implicit ('the file exists and parses') rather than an explicit validate step.

4 / 5

Progressive Disclosure

The single-file body is well-organized with clear, well-signaled sections (When to Use, Execution Protocol, Output Schema, Failure Modes, Done Criteria) and no nested references, which suits a single-purpose API-wrapper skill. Minor gaps: the referenced script is absent from the bundle, and content like the aspect-ratio picker and server-side taxonomy could live in a reference file.

4 / 5

Total

15

/

20

Passed

Description

58%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 clearly and concretely states what the skill does in third person, but it omits any 'when to use' trigger guidance and lacks common platform keywords (Shorts, TikTok, Reels, highlights). The framework taxonomy enumeration adds verbosity without improving triggering.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to turn a video, podcast, or stream into shorts, clips, or TikTok/Reels/YouTube Shorts highlights.'

Include natural synonyms users would say — 'shorts', 'TikTok', 'Reels', 'highlights', 'viral clips', '.mp4' — to raise trigger term coverage.

Trim the eight-item virality-framework enumeration from the description; keep only transcription, highlight ranking, dedupe, and auto-crop, and drop the buzzword 'viral-ready' in favor of a concrete outcome statement.

DimensionReasoningScore

Specificity

The description names concrete actions — "handles transcription, highlight ranking ... overlap dedupe, and vertical face-tracking auto-crop" — in third person ("Wraps muapi.ai's /ai-clipping endpoint"). It falls short of a 5 because the eight-term virality-framework enumeration pads the description without adding agent-facing capabilities, and "viral-ready" is mild over-claiming.

4 / 5

Completeness

The 'what' is clear and concrete ("Turn a long video into N viral-ready short clips with a single managed API call"), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. It is not a 2 because the 'what' is explicit rather than vague.

3 / 5

Trigger Term Quality

Natural phrases like "long video", "short clips", "viral", "transcription", and "auto-crop" are present, but common user phrasings such as "Shorts", "TikTok", "Reels", "highlights", and ".mp4" are absent. This matches the anchor for some relevant keywords missing common variations, rather than the level-4 'only a few terms missing'.

3 / 5

Distinctiveness Conflict Risk

"Wraps muapi.ai's /ai-clipping endpoint" and the long-video-to-shorts conversion define a clear niche with distinct triggers. Minor overlap remains with generic video-editing or transcription skills, so it fits the 'mostly distinct; minor overlap risk' anchor rather than the level-5 minimal-conflict anchor.

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

.opencode/skills/muapi-ai-clipping/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.