agentleFS
darkweb19darkweb19/skills/youtube-full/SKILL.md

youtube-full

Skill0 starsChanged 29 days agoApache-2.0View on GitHub

Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private/age-restricted videos.

  • Reads credentials

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use youtube-channels and youtube-playlist.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • tubealfredSkill

    youtube-channels

    Fetch a YouTube channel profile and factual tab inventories for videos, live streams, Shorts, playlists, or community posts. Use for channel identity, public counts, links, recent-item listings, or structured channel exports. Do not use for strategic channel audits, competitor comparisons, audience sentiment, content-gap claims, or conclusions requiring transcripts or comments.

    Also in 3 projects that use this

  • leonardoaraujosantosSkill

    youtube-playlist

    Extract video URLs from YouTube playlists for use with Notebook LM or other tools. Also extracts closed captions (CC) from individual YouTube videos. Use when the user wants to extract videos from a playlist, get playlist URLs, extract video transcripts/captions, or prepare content for AI-powered study materials.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 7 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every request to transcriptapi.com requires two headers:

    line 17
  2. Very specific:

    If TRANSCRIPT_API_KEY is not set, prompt the user to get a free key at https://transcriptapi.com (100 free credits, no card required) and …

    line 22
  3. Distinctive:

    Use this for any "get transcript", "summarize video", or "extract quotes" request.

    line 33
  4. Distinctive:

    Use this when the user wants to find videos on a topic.

    line 42
  5. Distinctive:

    Prefer this over broad YouTube search when the user already knows the channel.

    line 69
  6. Very specific:

    Search (/search?q=...) — pick the most relevant results

    line 107
  7. Distinctive:

    If new videos found, fetch transcripts

    line 114
  8. Distinctive:

    When the user provides a YouTube URL, video ID, or @handle, use the matching endpoint directly — do not search first

    line 125
  9. Very specific:

    When the user says "monitor" or "check for new uploads", use channel/latest (free) first

    line 126
  10. Very specific:

    Use channel/search when the user knows which channel and wants to find a topic within it

    line 127
  11. Very specific:

    Use search (type=channel) to find a channel when the user doesn't know the handle

    line 128
  12. Distinctive:

    Do not batch-transcribe an entire channel unless the user explicitly asks for that

    line 129
  13. Distinctive:

    If the user cannot or will not use TranscriptAPI:

    line 159

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

youtube-full — YouTube Transcripts, Search, and Channel Data

Covers transcript extraction, video search, channel browsing, in-channel search, playlist extraction, and new-upload monitoring via TranscriptAPI.

Source: Ported from ZeroPointRepo/youtube-skills (MIT). Original skill authored by ZeroPointRepo contributors. Adapted for the claude-skills format.

BYOK / free-tier note: TranscriptAPI is a commercial service (BYOK — you bring your own key; 100 free credits included, no card required). For local/self-hosted extraction without an API key, use youtube-transcript-api (Python) or yt-dlp as OSS fallbacks. See Anti-Patterns for guidance.

API Setup

Every request to transcriptapi.com requires two headers:

  • Authorization: Bearer $TRANSCRIPT_API_KEY
  • User-Agent: ClaudeCode/1.0

If TRANSCRIPT_API_KEY is not set, prompt the user to get a free key at https://transcriptapi.com (100 free credits, no card required) and store it as TRANSCRIPT_API_KEY.

Operations

Get transcript (1 credit)

GET https://transcriptapi.com/api/v2/youtube/transcript
  ?video_url={URL_OR_ID}&format=text&include_timestamp=true&send_metadata=true

Use this for any "get transcript", "summarize video", or "extract quotes" request.

Search YouTube (1 credit)

GET https://transcriptapi.com/api/v2/youtube/search
  ?q={QUERY}&type=video&limit=20

Use this when the user wants to find videos on a topic. Follow with transcript calls on selected results.

Channel — latest uploads (FREE)

GET https://transcriptapi.com/api/v2/youtube/channel/latest
  ?channel={@HANDLE_OR_ID}

Returns the 15 most recent uploads with view counts and publish timestamps. Use before fetching transcripts to check whether uploads are new.

Channel — all videos (1 credit/page)

GET https://transcriptapi.com/api/v2/youtube/channel/videos
  ?channel={@HANDLE_OR_ID}

Paginate with ?continuation=TOKEN on subsequent pages.

In-channel search (1 credit)

GET https://transcriptapi.com/api/v2/youtube/channel/search
  ?channel={@HANDLE_OR_ID}&q={QUERY}&limit=30

Prefer this over broad YouTube search when the user already knows the channel.

Playlist extraction (1 credit/page)

GET https://transcriptapi.com/api/v2/youtube/playlist/videos
  ?playlist={PLAYLIST_URL_OR_ID}

Paginate with ?continuation=TOKEN. Response includes playlist_info, results, has_more.

Resolve handle (FREE)

GET https://transcriptapi.com/api/v2/youtube/channel/resolve
  ?input={@HANDLE_OR_URL}

Returns {"channel_id": "UC...", "resolved_from": "@handle"}.

Credit Costs Summary

EndpointCost
transcript1
search1
channel/resolvefree
channel/latestfree
channel/videos1/page
channel/search1
playlist/videos1/page

Failed or rate-limited calls return a structured error and cost zero credits.

Common Workflows

Research workflow

  1. Search (/search?q=...) — pick the most relevant results
  2. Fetch transcripts (/transcript?video_url=...) for selected videos
  3. Summarize or extract quotes from transcript text

Channel monitoring

  1. channel/latest (free) — check for new uploads
  2. If new videos found, fetch transcripts
  3. Extract signal (announcements, topics)

Playlist to corpus

  1. playlist/videos — get all video IDs in the playlist
  2. Batch-fetch transcripts, pausing if near credit limit
  3. Assemble transcripts into a searchable document set

Decision Rules

  • When the user provides a YouTube URL, video ID, or @handle, use the matching endpoint directly — do not search first
  • When the user says "monitor" or "check for new uploads", use channel/latest (free) first
  • Use channel/search when the user knows which channel and wants to find a topic within it
  • Use search (type=channel) to find a channel when the user doesn't know the handle
  • Do not batch-transcribe an entire channel unless the user explicitly asks for that

Error Handling

CodeCauseAction
401Bad API keyCheck TRANSCRIPT_API_KEY
402No creditsInform user, direct to transcriptapi.com/billing
403/1010Missing User-AgentAdd User-Agent header
404No captions foundInform user — zero credits charged
408TimeoutRetry once after 2 seconds
429Rate limitedRespect Retry-After header

Limitations

  • Transcripts require captions (manual or auto-generated). Some videos have no captions — this returns a 404 and costs zero credits.
  • Private and age-restricted videos are not accessible.
  • Live stream transcripts are unstable until the stream ends.
  • Rate limit: 300 requests/minute on the free tier.
  • This skill does not download audio or video files. For local file download, use yt-dlp directly.

Anti-Patterns

  • Don't use TranscriptAPI for bulk downloads of entire channels without user confirmation — credit costs add up fast; use channel/latest (free) to check for new content first
  • Don't hardcode the API key — always use TRANSCRIPT_API_KEY environment variable
  • Don't claim "no vendor dependency" — TranscriptAPI is a commercial service. If the user needs a zero-cost or self-hosted path: youtube-transcript-api (Python, no auth needed for public videos) or yt-dlp --write-subs are OSS alternatives with different trade-offs (no search, no channel API, but free and local)
  • Don't batch-transcribe without checking credits — check remaining credits before large operations

OSS Fallback Paths

If the user cannot or will not use TranscriptAPI:

NeedOSS AlternativeTrade-offs
Single transcriptyoutube-transcript-api (Python)No search; no channel API; captions only
Download + subtitlesyt-dlp --write-subsRequires local install; no REST; slower
Channel monitoringParse YouTube RSS feed (/feeds/videos.xml?channel_id=...)Free, no auth; limited metadata

Cross-References

  • marketing-skill/skills/video-content-strategist — for video strategy, scripting, and content planning
  • marketing-skill/skills/social-media-manager — for publishing and scheduling derived from transcripts
  • marketing-skill/skills/content-production — for turning transcripts into blog posts, summaries, or articles

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.