CtrlK
BlogDocsLog inGet started
Tessl Logo

video-transcript-downloader

yt-dlp downloads: video, audio, subtitles, transcripts, clips, playlists.

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/video-transcript-downloader/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

83%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 tight, highly actionable CLI reference with excellent conciseness and copy-paste commands. Its main gap is the absence of verification steps for batch/playlist downloads, which caps workflow clarity.

Suggestions

Add a brief verification step after downloads (e.g., check the output file exists/plays or list the output dir) to satisfy the batch-operation validation expectation.

Consider moving the extended yt-dlp pass-through arg examples and format-id selection into a short referenced doc so SKILL.md stays a lean overview.

Make the transcript fallback sequence explicit as numbered steps with a retry/checkpoint rather than two bullet points.

DimensionReasoningScore

Conciseness

The body is lean command-reference prose with no padding or explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Provides copy-paste-ready executable commands for transcript, download, audio, subs, and formats, covering the common cases including extra yt-dlp args after '--'.

5 / 5

Workflow Clarity

Setup and per-subcommand usage are clear and the transcript fallback is documented, but playlist/batch downloads have no verification checkpoint, so the batch-operation cap of 3 applies.

3 / 5

Progressive Disclosure

Well-organized into labeled sections with a single real one-level-deep script reference (./scripts/vtd.js); not a 5 because all content is inline with no signaled split for the format/arg details.

4 / 5

Total

17

/

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.

The description is specific and tool-scoped with good natural keywords, but it omits any explicit "when to use" trigger guidance, which caps completeness. Adding a Use-when clause would lift the weaker dimensions.

Suggestions

Append a 'Use when...' clause naming concrete triggers (e.g., downloading video/audio/subtitles, fetching a transcript, grabbing a playlist or clip).

Add the synonym 'captions' alongside 'subtitles' to broaden trigger-term coverage.

Mention common file extensions or output forms (e.g., .mp4, .m4a, .srt) to improve distinctiveness and trigger matching.

DimensionReasoningScore

Specificity

Lists six concrete download types ("video, audio, subtitles, transcripts, clips, playlists") tied to a named tool, matching the comprehensive-coverage anchor.

5 / 5

Completeness

The "what" is clear (yt-dlp downloads of listed media types) but there is no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Natural terms like "video", "audio", "subtitles", "transcripts", and "playlists" are present, but synonyms such as "captions" and file extensions are missing.

4 / 5

Distinctiveness Conflict Risk

The yt-dlp niche and media-type list are largely distinct, with only minor overlap risk against generic download skills; not a 5 because no explicit trigger phrases sharpen the niche.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
steipete/agent-scripts
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.