youtube-apify-transcript

Fetch YouTube transcripts via APIFY API. Works from cloud IPs (Hetzner, AWS, etc.) by bypassing YouTube's bot detection. Free tier includes $5/month credits (~714 videos). No credit card required.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/research-tools/capabilities/youtube-apify-transcript/SKILL.md

Quality

Content

68%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 copy-paste commands and a real backing script, but marketing filler hurts conciseness and the batch mode lacks validation/verification steps, capping workflow clarity.

Suggestions

Strip marketing filler ("Perfect for personal use", "(saves money!)", "FREE!", "(less than 1 cent!)") to tighten the token budget.

Add a validation/verification step to batch mode, e.g. reporting per-URL success/failure and a final summary before declaring completion.

Move the APIFY Actor input schema and output-format reference into a short references file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational guidance, but padded with marketing commentary like "Perfect for personal use", "(less than 1 cent!)", "(saves money!)", and "FREE!" that add tokens without aiding execution.	3 / 5
Actionability	Copy-paste-ready commands cover the common cases (basic, --json, --output, --lang, caching, --batch) and reference a real, present script, giving fully executable guidance.	5 / 5
Workflow Clarity	The basic fetch workflow is clear and setup is sequenced, but the batch mode (a batch operation) has no validation/verification steps for partial failures, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-sectioned body with a single one-level-deep reference (scripts/fetch_transcript.py, which exists) and easy navigation; short of 5 because inline API/output reference material could be split out and the body runs ~159 lines.	4 / 5
	Total	15 / 20 Passed

Description

53%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 concrete and well-scoped to a distinct niche, but it omits an explicit "Use when..." trigger clause and lacks synonym coverage (captions/subtitles), capping completeness and trigger quality at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. "Use when you need YouTube transcripts, captions, or subtitles, especially from cloud IPs that YouTube blocks."

Include common synonyms ("captions", "subtitles", "video transcript") so natural user phrasings match the skill.

Move operational/pricing detail (free tier, no credit card) to the body to keep the description focused on capability and triggers.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("Fetch YouTube transcripts via APIFY API", "bypassing YouTube's bot detection") but offers only a single capability rather than a comprehensive list of actions.	3 / 5
Completeness	The "what" is clear ("Fetch YouTube transcripts via APIFY API") but there is no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Contains the natural primary term "YouTube transcripts" but misses common synonyms a user might say such as "captions" or "subtitles"; "APIFY API" is technical jargon, not a user trigger.	3 / 5
Distinctiveness Conflict Risk	"Fetch YouTube transcripts via APIFY API" is a clear, narrow niche with minimal overlap risk; falls just short of 5 because no explicit trigger phrase reinforces the distinctiveness.	4 / 5
	Total	13 / 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: gooseworks-ai/goose-skills
Path: skills/research-tools/capabilities/youtube-apify-transcript/SKILL.md
Commit: 2523432

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