CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

video-transcript-downloader

Download, transcribe, inspect, summarize, or convert video and audio sources. Use when the user wants transcripts, subtitles, audio extraction, or media downloads from a video source.

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/content-publishing/video-transcript-downloader/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is a well-organized, concise operating contract with a genuine validation feedback loop, but it contains zero executable guidance — no commands, tools, or wrapper syntax for downloading or transcribing media — so Claude cannot act on it concretely. Additionally, its progressive-disclosure pointer targets a path absent from the bundle while the actual reference files go unmentioned.

Suggestions

Add concrete executable guidance for the core modes: the actual wrapper or tool invocations for downloading media (e.g., the repo's documented download command) and extracting transcripts/subtitles, with one copy-paste-ready example per common case.

Fix progressive disclosure to match the bundle: either point to the actual files present (references/contract.yaml, references/evals.yaml, references/task-profile.json) or correct the archived-context path so deferred content resolves, and briefly say what each file is for.

Make the workflow checkpoints concrete by naming the "narrowest real validator" for this skill (e.g., a specific transcript-format check or file-existence/size assertion) instead of the abstract "Run the narrowest real validator or command path available."

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows and no padded prose; the generic "Philosophy" section is the main content that could be trimmed. It is not 5 because a few sections (Philosophy, parts of Avoid/Anti-Patterns) restate generic operating posture rather than skill-specific knowledge; not 3 because there is no genuine over-explanation.

4 / 5

Actionability

There is not a single executable command, tool name, or code example — no download/transcription wrapper invocation, no concrete validator. Guidance like "Inspect 2-3 focused surfaces" and "Run the narrowest real validator or command path available" stays at the hint level, matching the anchor of minimal concrete guidance with missing specific steps. It is not 3 because even pseudocode-level specifics of how to download or transcribe are absent; not 1 because the Inputs/Outputs/Workflow lists do provide real structural guidance.

2 / 5

Workflow Clarity

Steps 1-5 form a coherent sequence with an explicit fail-fast gate ("Stop at the first failed gate or blocker and report exact evidence") and a fix-then-rerun feedback loop ("Rerun the relevant validation after fixes before claiming completion"). It is not 5 because the checkpoints never name what to actually run — no concrete validator, command, or check is specified, leaving the sequence abstract.

4 / 5

Progressive Disclosure

The body is well-sectioned and states a load-only-what's-needed posture, but its single deferred-content pointer ("Infrastructure/references/deferred-skill-context/content-publishing-video-transcript-downloader/") does not exist in the bundle, and the actual bundle files (references/contract.yaml, references/evals.yaml, references/task-profile.json) are never referenced from the body. Scored against the actual bundle structure, this is structure present but references not clearly signaled. It is not 4 because the one pointer given does not resolve to a real bundle path and the real references are invisible to a reader.

3 / 5

Total

13

/

20

Passed

Description

88%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 strong description: explicit what-and-when structure with multiple concrete actions and natural trigger terms in third-person voice. The only gaps are missing synonyms (e.g., "captions") and platform/extension terms that would push trigger coverage to comprehensive.

DimensionReasoningScore

Specificity

The description lists five concrete actions ("Download, transcribe, inspect, summarize, or convert video and audio sources") plus concrete deliverables ("transcripts, subtitles, audio extraction, or media downloads"), giving comprehensive coverage of the domain's capabilities. It is not 4 because the action coverage shows no gaps for this skill's scope.

5 / 5

Completeness

It explicitly answers both questions: the "what" ("Download, transcribe, inspect, summarize, or convert video and audio sources") and the "when" ("Use when the user wants transcripts, subtitles, audio extraction, or media downloads from a video source") with concrete trigger phrases, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Natural trigger phrases like "transcripts, subtitles, audio extraction, or media downloads from a video source" cover the core vocabulary users would say. It is not 5 because common synonyms and specifics are missing (e.g., "captions", "rip audio", platform names like YouTube, or file extensions like .srt/.mp3); not 3 because the key natural phrases are all present.

4 / 5

Distinctiveness Conflict Risk

The video/audio transcription-and-download niche is mostly distinct with clear triggers. It is not 5 because broad verbs like "inspect" and "summarize" invite minor overlap with general media-processing or summarization skills; not 3 because the dominant triggers (transcripts, subtitles, audio extraction from a video source) are specific to this skill.

4 / 5

Total

18

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/content-publishing/video-transcript-downloader/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.