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

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, code-first skill with verified references and a real backing script; its weak spots are verbosity around billing/marketing and missing validation feedback for batch fetching. Tightening prose and adding a per-URL success/retry check would lift the lower dimensions.

Suggestions

Add an explicit batch validation step, e.g. after processing, report failed URLs and retry them once before declaring done, to introduce a feedback loop.

Move the cost/free-tier/billing detail into a short pointer or omit it; keep the SKILL.md focused on what to run.

Consider splitting the full options/caching/batch reference into a separate file referenced one level deep to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and code-driven, but sections like 'Why APIFY?' and 'Free Tier' restate marketing/billing context ('Perfect for personal use', '$0.007 per video (less than 1 cent!)') that doesn't earn its tokens for executing the task.	2 / 3
Actionability	Every usage path is given as copy-paste-ready, executable commands with real flags, and the actor input/output field table makes the contract concrete — fully actionable guidance.	3 / 3
Workflow Clarity	Setup and usage are sequenced, but batch operations lack validation checkpoints (e.g. verifying each fetch succeeded or a retry-on-failure loop), and the guidelines cap workflow clarity at 2 when feedback loops are missing for batch work.	2 / 3
Progressive Disclosure	Structure is clean with a single real script (scripts/fetch_transcript.py) and all body references resolve to it, but the SKILL.md inlines the full options/caching/batch reference rather than splitting detail one level deep, so it is more monolithic than the top anchor.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 distinct but stops short of explicit trigger guidance, landing it in the middle band on most dimensions. Adding a 'Use when...' clause and natural synonym coverage would lift completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when fetching transcripts/captions for YouTube videos, especially from cloud or server IPs that YouTube blocks.'

Include natural synonyms users say — 'captions', 'subtitles', 'video transcript' — to improve trigger-term coverage.

Trim the billing detail ('$5/month credits (~714 videos)', 'No credit card required') from the description; it is context, not capability.

Dimension	Reasoning	Score
Specificity	It names the domain and the concrete action ('Fetch YouTube transcripts via APIFY API') plus a key constraint ('Works from cloud IPs'), but the action set is narrow — a single capability rather than the multiple concrete actions the top anchor calls for.	2 / 3
Completeness	It clearly answers 'what does this do' but has no explicit 'Use when...' trigger clause, and the guidelines state a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant natural terms appear ('YouTube transcripts', 'cloud IPs') and 'APIFY' is a recognizable proper noun, but common user variations like 'captions', 'subtitles', or 'video text' are missing, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The pairing of 'YouTube transcripts' with the 'APIFY' actor and 'cloud IP / bypass bot detection' niche is a clear, distinct trigger unlikely to collide with other skills.	3 / 3
	Total	9 / 12 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: 8866b2a

Reviewed: 1 day 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.