oma-video

Short-form, explainer, and demo video generation via a key-optional 3-tier router. Composes scripts, oma-voice narration, oma-image/oma-slide/stock visuals, key-free captions, and a per-run agent-authored Remotion composition (always-latest Remotion + remotion-dev/skills) into reproducible run directories. Routes three modes — shorts/reels (9:16), explainer (16:9 README/code/data), and demo/walkthrough (screen capture from human-recorded video). Use for video, shorts, reels, short-form, demo, explainer, walkthrough, screencast, web capture, video generation, 영상, 숏폼, 쇼츠, 릴스, 데모, 설명 영상.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/oma-video/SKILL.md

Quality

Content

56%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 content is a thorough, actionable specification for a complex multi-mode video router with a clear sequenced workflow and validation. Its main weakness is progressive disclosure: it relies heavily on a resources/ bundle that is not present, leaving the navigation structure non-functional.

Suggestions

Ship the referenced resources/ bundle (execution-protocol.md, vendor-matrix.md, prompt-tips.md, checklist.md, remotion-authoring/, strudel/, mpt/) alongside SKILL.md so the in-body references resolve to real files.

Tighten the music/BGM section (presets, LUFS rationale, normalization-vs-loudnorm aside) into a brief pointer to a resources file, since this detail competes with core routing context.

Make the VERIFY stage validation a scripted, copy-paste command (e.g. an explicit manifest/schema check invocation) rather than a described checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is dense and largely efficient for a complex multi-mode router, but sections like the music BGM presets, LUFS normalization rationale, and repeated clarification guidance include over-explanation that could be trimmed.	3 / 5
Actionability	Concrete, runnable CLI invocations and flag references dominate the Invocation and Canonical command path sections, with only minor gaps (e.g. some Remotion authoring details deferred to resources).	4 / 5
Workflow Clarity	A clear PREPARE/ACQUIRE/ACT/VERIFY/FINALIZE sequence with explicit validation (VERIFY validates asset-bus schemas, manifest hashes, exit code, mp4) and recovery branches is present; only some validation checkpoints are implicit rather than scripted.	4 / 5
Progressive Disclosure	The body references many resources/ paths (execution-protocol.md, vendor-matrix.md, prompt-tips.md, checklist.md, remotion-authoring/, strudel/render.mjs, mpt/driver.py) but the referenced bundle directories (references/, scripts/, assets/, resources/) do not exist alongside SKILL.md, so the navigation points to files that are absent and cannot be navigated as structured.	1 / 5
	Total	12 / 20 Passed

Description

95%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 comprehensive and well-structured, clearly stating what the skill does and when to use it with an extensive bilingual trigger-term list. It is slightly dense with internal tool names, which mildly dilutes plain-language specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Composes scripts, oma-voice narration, oma-image/oma-slide/stock visuals, key-free captions') and three routed modes with aspect ratios, but the dense roster of internal tool names leaves minor gaps in plain-action coverage.	4 / 5
Completeness	Explicitly answers both 'what' (composes scripts/narration/visuals/captions/Remotion into reproducible run directories, routes three modes) and 'when' via a concrete 'Use for ...' trigger clause.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms ('video, shorts, reels, short-form, demo, explainer, walkthrough, screencast, web capture, video generation') plus Korean synonyms and file-format-relevant phrasing, covering common variations.	5 / 5
Distinctiveness Conflict Risk	Clear niche (key-optional 3-tier video router with named modes shorts/explainer/demo) with distinct triggers and explicit sibling-skill boundaries, giving minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: first-fluke/oh-my-agent
Path: .agents/skills/oma-video/SKILL.md
Commit: 7721120

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.