youtube-clipper

YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/youtube-clipper/SKILL.md

Quality

Content

55%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 a well-structured, extremely lean catalog stub that clearly signals its upstream source, but it contains no executable guidance or step sequence for the clip workflow itself — everything actionable is deferred to an external GitHub repository. As a discoverability advertisement it is clean; as a SKILL.md body it is not self-sufficient.

Suggestions

Inline the core workflow as concrete commands (e.g., yt-dlp download, ffmpeg slice, caption step) so the skill is actionable without the external repo, or vendor the upstream bundle's key script into scripts/ and reference it here.

Add a numbered step sequence for the clip workflow with at least one validation checkpoint (e.g., verify the sliced segment duration before export).

Replace the non-portable `open <url>` command with a curl-able or git-cloneable concrete installation step.

Dimension	Reasoning	Score
Conciseness	The ~25-line body is lean with no padding and no explanation of concepts Claude already knows; every section (What it does, Source, How to use) earns its place. This matches the 5 anchor 'lean and efficient; every token earns its place'.	5 / 5
Actionability	The body only offers high-level hints — "install the upstream bundle into your active agent's skills directory" and "open https://github.com/op7418/Youtube-clipper-skill" — with no concrete steps, commands, or code for actually pulling video, slicing, captioning, or exporting. This fits the 2 anchor 'high-level hints but missing the specific steps'; it avoids a 1 only because a concrete URL and invocation-by-name instruction are provided.	2 / 5
Workflow Clarity	There is a rough sequence for adopting the skill (inspect upstream README, install bundle, invoke by name or trigger phrase) but the actual clip-generation workflow has no steps at all and no validation checkpoints. This matches the 2 anchor 'rough sequence present but many gaps; steps poorly defined; validation absent'.	2 / 5
Progressive Disclosure	No bundle files exist (no references/, scripts/, or assets/ directories), and the body is well-organized into short sections with a single, clearly signaled one-level pointer to the upstream repository. This fits the 4 anchor 'good structure; most content appropriately placed; references mostly clear'; it does not reach 5 because the essential detail lives entirely outside the skill as an external URL rather than an in-bundle reference.	4 / 5
	Total	13 / 20 Passed

Description

70%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 concise, concrete, and domain-specific, listing four pipeline actions in third person without fluff. Its main weakness is the missing explicit 'when to use' guidance, which caps completeness and leaves users to infer triggering conditions.

Suggestions

Append an explicit trigger clause, e.g., "Use when the user wants to create, trim, or caption clips from YouTube videos or build highlight reels from a source video."

Add a few natural synonyms users would say (shorts, trim/cut video, subtitles, .mp4 export) to widen trigger coverage.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions — "pull source video, slice highlights, add captions, and export" — which is several specific actions covering the pipeline, matching the anchor for several specific actions with minor gaps in coverage (no mention of output formats, trimming options, or publishing targets). It falls short of the 5 anchor's 'comprehensive coverage' and clearly exceeds the 3 anchor's '1-2 concrete actions'.	4 / 5
Completeness	The 'what' is clearly stated ("pull source video, slice highlights, add captions, and export"), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, which per the judging guidelines caps completeness at 3. This matches the anchor 'Has a clear what but when is missing or only weakly implied'; it is above the 2 anchor because the what is concrete, not vague.	3 / 5
Trigger Term Quality	Natural terms present include "YouTube", "clip", "video", "highlights", "captions", and "edit", giving good keyword coverage a user would plausibly say. A few natural variations are missing (e.g., 'shorts', 'trim video', 'clip from a video', 'subtitles'), keeping it below the 5 anchor's comprehensive synonym/extension coverage.	4 / 5
Distinctiveness Conflict Risk	"YouTube clip generation and editing with automated workflows" carves out a clear niche with distinct triggers; it is unlikely to fire for unrelated skills. Minor breadth from generic 'editing' is not enough to drop to the 4 anchor's 'minor overlap risk', since the YouTube-specific framing dominates.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/youtube-clipper/SKILL.md
Commit: 1b47e60

Reviewed: 3 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.