Youtube Content

by nousresearch25a71a744cb9MIT252K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

YouTube transcripts to summaries, threads, blogs.

Includes scriptsWriting & Content
AI-generated overview

Fetches YouTube transcripts and reformats them into summaries, chapters, threads, or blog posts.

What it does
The skill retrieves transcripts from YouTube videos using a bundled Python helper script that accepts standard URLs, short links, shorts, embeds, live links, or raw video IDs. It can output JSON with metadata, plain text, or timestamped text, and supports a language fallback chain. It then transforms the transcript into requested formats such as chapters, summaries, chapter summaries, Twitter/X threads, blog posts, or notable quotes. It also handles long transcripts by chunking and merging summaries.
When to use it
Use this skill when a user shares a YouTube URL or video link and asks for a summary, transcript, or reformatted content. It is also suitable when the user wants to extract and restructure content from any YouTube video into chapters, threads, blog posts, or quotes.
Requirements
Requires a Python environment prepared through the Hermes package management workflow with the youtube extra installed, including the youtube_transcript_api package. The skill ships an executable helper script, scripts/fetch_transcript.py, and a reference file, references/output-formats.md. Network access is needed to fetch transcripts from YouTube.

YouTube Content Tool

When to use

Use when the user shares a YouTube URL or video link, asks to summarize a video, requests a transcript, or wants to extract and reformat content from any YouTube video. Transforms transcripts into structured content (chapters, summaries, threads, blog posts).

Extract transcripts from YouTube videos and convert them into useful formats.

Setup

Use terminal with the Python from a PM-prepared Hermes source checkout. The youtube extra declares the helper's dependency; do not install packages into Hermes with raw pip or project-discovering uv run.

From that checkout, first follow the isolated development-home setup in Package Management, then prepare the extra and reactivate before running the helper:

bash
source ./activatepython -c "import pm; pm.sync_venv(['youtube'], explicit=True)"source ./activatepython -c "import youtube_transcript_api; print(youtube_transcript_api.__file__)"

On Windows, use . .\activate.ps1 instead of source ./activate. If the terminal runs on a different host or in a sandbox, use an explicitly isolated helper environment there, not the agent's production environment. Run every command below with the interpreter whose import check succeeded.

Helper Script

SKILL_DIR is the directory containing this SKILL.md file. The script accepts any standard YouTube URL format, short links (youtu.be), shorts, embeds, live links, or a raw 11-character video ID.

bash
# JSON output with metadatapython SKILL_DIR/scripts/fetch_transcript.py "https://youtube.com/watch?v=VIDEO_ID"
# Plain text (good for piping into further processing)python SKILL_DIR/scripts/fetch_transcript.py "URL" --text-only
# With timestampspython SKILL_DIR/scripts/fetch_transcript.py "URL" --timestamps
# Specific language with fallback chainpython SKILL_DIR/scripts/fetch_transcript.py "URL" --language tr,en

Output Formats

After fetching the transcript, format it based on what the user asks for:

  • Chapters: Group by topic shifts, output timestamped chapter list
  • Summary: Concise 5-10 sentence overview of the entire video
  • Chapter summaries: Chapters with a short paragraph summary for each
  • Thread: Twitter/X thread format — numbered posts, each under 280 chars
  • Blog post: Full article with title, sections, and key takeaways
  • Quotes: Notable quotes with timestamps

Example — Chapters Output

00:00 Introduction — host opens with the problem statement03:45 Background — prior work and why existing solutions fall short12:20 Core method — walkthrough of the proposed approach24:10 Results — benchmark comparisons and key takeaways31:55 Q&A — audience questions on scalability and next steps

Workflow

  1. Fetch the transcript using terminal and the prepared Python with --text-only --timestamps.
  2. Validate: confirm the output is non-empty and in the expected language. If empty, retry without --language to get any available transcript. If still empty, tell the user the video likely has transcripts disabled.
  3. Chunk if needed: if the transcript exceeds ~50K characters, split into overlapping chunks (~40K with 2K overlap) and summarize each chunk before merging.
  4. Transform into the requested output format. If the user did not specify a format, default to a summary.
  5. Verify: re-read the transformed output to check for coherence, correct timestamps, and completeness before presenting.

Error Handling

  • Transcript disabled: tell the user; suggest they check if subtitles are available on the video page.
  • Private/unavailable video: relay the error and ask the user to verify the URL.
  • No matching language: retry without --language to fetch any available transcript, then note the actual language to the user.
  • Dependency missing: repeat PM preparation and reactivation above, then verify the helper uses that Python. Do not repair the selected generation with pip.

Source and attribution

Source:nousresearch/hermes-agentinskills/media/youtube-contentat commit25a71a7

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal