YouTube Description Generator

Youtube description

by timscheuerai · MIT license · ★ 37 on GitHub

Youtube description cover

Transcribe a finished YouTube video and generate its description block — a very short 2-sentence description, your fixed CTA, and YouTube chapter timestamps — then write it into your content record. Uses ElevenLabs Scribe for word-level…

---
name: youtube-description
description: Transcribe a finished YouTube video and generate its description block — a very short 2-sentence description, your fixed CTA, and YouTube chapter timestamps — then write it into your content record. Uses ElevenLabs Scribe for word-level timestamps. Use when asked to "write the YouTube description", "generate timestamps / chapters for this video", "describe this YT video", "make the description for <video>", or "/youtube-description".
---

# youtube-description

Turns a finished video cut into a copy-paste-ready YouTube description.
Three parts, always in this order:

1. **Description** — very short, 2 sentences, in your voice.
2. **Fixed CTA block** — your product + social links, verbatim, never edited.
3. **Timestamps** — YouTube chapters derived from the transcript.

The transcription engine is ElevenLabs Scribe (word-level timestamps),
the same one `/video-use` uses. The output is a block you paste into
YouTube yourself (this skill does not touch the live video).

Overview

Turns a finished video cut into a copy-paste-ready YouTube description. Three parts, always in this order:

Manual install (npx, ZIP)
Claude Codenpx skills add timscheuerai/content-vault --skill youtube-description -g -a claude-code
Claude Code (degit)npx degit timscheuerai/content-vault/skills/youtube-description#main ~/.claude/skills/youtube-description
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md6.4 KB
Read SKILL.md here
timscheuerai/main1 file shown
SKILL.md
Show the full text172 lines

youtube-description

Turns a finished video cut into a copy-paste-ready YouTube description. Three parts, always in this order:

  1. Description — very short, 2 sentences, in your voice.
  2. Fixed CTA block — your product + social links, verbatim, never edited.
  3. Timestamps — YouTube chapters derived from the transcript.

The transcription engine is ElevenLabs Scribe (word-level timestamps), the same one /video-use uses. The output is a block you paste into YouTube yourself (this skill does not touch the live video).


SETUP (run this once)

  1. Lock your fixed CTA block by filling the placeholders in step 4: <YOUR_BRAND>, <YOUR_DOMAIN>, <YOUR_LINKEDIN_URL>. After that the CTA is reproduced verbatim on every video, never reworded.
  2. Set ELEVENLABS_API_KEY in your env (or .env). Scribe needs it. /video-use in this vault already uses the same key.
  3. (Optional) Point <YOUR_BRAND_DOC> at your voice rules so the description passes the same slop checks as your other copy.

When to use

Trigger on:

  • "Write the YouTube description for <video>"
  • "Generate chapters / timestamps for this video"
  • "Describe this YT video"
  • User types /youtube-description

Sibling skills (don't confuse):

  • Upload + thumbnails + playlist → /youtube-publisher
  • Edit raw footage into a cut → /video-use
  • Write the script before filming → /youtube-script

Inputs

A finished video. Accept any of:

  • An absolute path to an .mp4 / .mov.
  • An existing ElevenLabs Scribe JSON (a /video-use transcript on disk) — reuse it to skip the API call and the wait. /video-use edits store these under <videos_dir>/edit/transcripts/<stem>.json.

Workflow

1. Get a timestamped transcript

Reuse a /video-use Scribe JSON if one exists (no API call, no wait — Scribe on a 25-min video costs minutes and credits). Otherwise call Scribe once and cache the result.

Either way, build a [M:SS] text transcript — one line per ~20s — and note the total duration (no chapter may land at or past it). The ElevenLabs Scribe endpoint returns word-level start/end times; group words into ~20s buckets and prefix each line with its start timestamp.

Read the whole transcript. It is your only source for both the description and the chapters.

2. Write the description (very short · 2 sentences)

House format for a tutorial:

Learn how to set up a cold email system with Claude Code that can handle 100k+ emails / month. We'll be using Claude Code, <YOUR_BRAND>, and a set of other tools.

Pattern:

  • Sentence 1: Learn how to <outcome> with <concrete spec>. The outcome and the number are the hook. Lead with what the viewer can do.
  • Sentence 2: We'll be using <tool stack>. Lowercase the tool names, end with "and other tools" / "and a set of custom skills" if the list runs long.

Rules: two sentences, no more. No em dashes (use . , : ( ·). No banned words (leverage, seamless, powerful, … full list in <YOUR_BRAND_DOC>). Concrete numerals over adjectives. It must read like you typed it, not like a SaaS template.

3. Build the chapters

From the transcript, pick chapter boundaries at real topic shifts and title each. Hard YouTube rules:

  • First chapter is 0:00. Always. Without it YouTube shows no chapters.
  • At least 3 chapters; each at least 10s after the previous.
  • Use the timestamp format the transcript prints (M:SS, or H:MM:SS past an hour).
  • Titles: terse, descriptive, no numbering, no em dashes. Lead with the thing the viewer learns ("Connecting your CRM"), not "Part 3".
  • 8–15 chapters for a 20–30 min tutorial is the right density. Don't make one per transcript line.
4. Assemble the block

Exactly this structure. The fixed CTA block sits between the description and the timestamps and is reproduced verbatim — never reword, never drop a line, never change the handle:

<description · sentence 1>
<description · sentence 2>

Try <YOUR_BRAND> for free:
<YOUR_DOMAIN>

Connect with me on LinkedIn:
<YOUR_LINKEDIN_URL>

Timestamps:
0:00 <first chapter title>
<m:ss> <title>
<m:ss> <title>
...
5. Write it into your content record

Put the assembled block where your content lives so it's tracked and copy-pasteable:

  • Markdown content vault: add or replace a ## YouTube description section in the video's .md file. Wrap the block in a fenced ```text code block so line breaks survive the paste into YouTube. The section is idempotent — replace the existing one, don't append a second.
  • Notion Content DB: paste the block into the video row's body / a "YouTube description" property.

Report back where you wrote it and the chapter count. Show the assembled block in chat too.


Definition of done

  1. A timestamped transcript exists for the video.
  2. A 2-sentence description in your voice (no em dashes, no banned words).
  3. The fixed CTA block, verbatim, between description and timestamps.
  4. Chapters starting at 0:00, none past the printed duration.
  5. The whole block written into your content record as an idempotent section, inside a copy-paste-ready code block, and the location reported.

Don'ts

  • Don't pad the description. Two sentences. (This is the opposite of the terse-CTA-only rule in /youtube-publisher; here you explicitly want the short description + timestamps. But "short" still means two sentences.)
  • Don't edit the CTA block. Verbatim, including the LinkedIn URL (use your canonical profile — no tracking params).
  • Don't invent chapter times. Every timestamp comes from the transcript.
  • Don't push to the live YouTube video. The content record only, unless asked. To set descriptions live, /youtube-publisher's finalize step (--only-descriptions) is the path.
  • Don't burn Scribe on an existing transcript. Check for a /video-use JSON first and reuse it.
1---
2name: youtube-description
3description: Transcribe a finished YouTube video and generate its description block — a very short 2-sentence description, your fixed CTA, and YouTube chapter timestamps — then write it into your content record. Uses ElevenLabs Scribe for word-level timestamps. Use when asked to "write the YouTube description", "generate timestamps / chapters for this video", "describe this YT video", "make the description for <video>", or "/youtube-description".
4---
5 
6# youtube-description
7 
8Turns a finished video cut into a copy-paste-ready YouTube description.
9Three parts, always in this order:
10 
111. **Description** — very short, 2 sentences, in your voice.
122. **Fixed CTA block** — your product + social links, verbatim, never edited.
133. **Timestamps** — YouTube chapters derived from the transcript.
14 
15The transcription engine is ElevenLabs Scribe (word-level timestamps),
16the same one `/video-use` uses. The output is a block you paste into
17YouTube yourself (this skill does not touch the live video).
18 
19---
20 
21## SETUP (run this once)
22 
231. Lock your **fixed CTA block** by filling the placeholders in step 4:
24 `<YOUR_BRAND>`, `<YOUR_DOMAIN>`, `<YOUR_LINKEDIN_URL>`. After that the
25 CTA is reproduced verbatim on every video, never reworded.
262. Set `ELEVENLABS_API_KEY` in your env (or `.env`). Scribe needs it.
27 `/video-use` in this vault already uses the same key.
283. (Optional) Point `<YOUR_BRAND_DOC>` at your voice rules so the
29 description passes the same slop checks as your other copy.
30 
31---
32 
33## When to use
34 
35Trigger on:
36- "Write the YouTube description for <video>"
37- "Generate chapters / timestamps for this video"
38- "Describe this YT video"
39- User types `/youtube-description`
40 
41Sibling skills (don't confuse):
42- Upload + thumbnails + playlist → `/youtube-publisher`
43- Edit raw footage into a cut → `/video-use`
44- Write the script before filming → `/youtube-script`
45 
46---
47 
48## Inputs
49 
50A finished video. Accept any of:
51- An absolute path to an `.mp4` / `.mov`.
52- An existing ElevenLabs Scribe JSON (a `/video-use` transcript on disk) —
53 reuse it to skip the API call and the wait. `/video-use` edits store
54 these under `<videos_dir>/edit/transcripts/<stem>.json`.
55 
56---
57 
58## Workflow
59 
60### 1. Get a timestamped transcript
61 
62Reuse a `/video-use` Scribe JSON if one exists (no API call, no wait —
63Scribe on a 25-min video costs minutes and credits). Otherwise call
64Scribe once and cache the result.
65 
66Either way, build a `[M:SS] text` transcript — one line per ~20s — and
67note the **total duration** (no chapter may land at or past it). The
68ElevenLabs Scribe endpoint returns word-level `start`/`end` times; group
69words into ~20s buckets and prefix each line with its start timestamp.
70 
71Read the whole transcript. It is your only source for both the
72description and the chapters.
73 
74### 2. Write the description (very short · 2 sentences)
75 
76House format for a tutorial:
77 
78> Learn how to set up a cold email system with Claude Code that can handle
79> 100k+ emails / month. We'll be using Claude Code, <YOUR_BRAND>, and a set
80> of other tools.
81 
82Pattern:
83- **Sentence 1:** `Learn how to <outcome> with <concrete spec>.` The
84 outcome and the number are the hook. Lead with what the viewer can do.
85- **Sentence 2:** `We'll be using <tool stack>.` Lowercase the tool names,
86 end with "and other tools" / "and a set of custom skills" if the list
87 runs long.
88 
89Rules: two sentences, no more. No em dashes (use `.` `,` `:` `(` `·`).
90No banned words (`leverage`, `seamless`, `powerful`, … full list in
91`<YOUR_BRAND_DOC>`). Concrete numerals over adjectives. It must read like
92you typed it, not like a SaaS template.
93 
94### 3. Build the chapters
95 
96From the transcript, pick chapter boundaries at real topic shifts and
97title each. Hard YouTube rules:
98- **First chapter is `0:00`.** Always. Without it YouTube shows no chapters.
99- At least **3** chapters; each at least **10s** after the previous.
100- Use the timestamp format the transcript prints (`M:SS`, or `H:MM:SS`
101 past an hour).
102- Titles: terse, descriptive, no numbering, no em dashes. Lead with the
103 thing the viewer learns ("Connecting your CRM"), not "Part 3".
104- 8–15 chapters for a 20–30 min tutorial is the right density. Don't make
105 one per transcript line.
106 
107### 4. Assemble the block
108 
109Exactly this structure. The **fixed CTA block sits between the
110description and the timestamps** and is reproduced **verbatim** — never
111reword, never drop a line, never change the handle:
112 
113```
114<description · sentence 1>
115<description · sentence 2>
116 
117Try <YOUR_BRAND> for free:
118<YOUR_DOMAIN>
119 
120Connect with me on LinkedIn:
121<YOUR_LINKEDIN_URL>
122 
123Timestamps:
1240:00 <first chapter title>
125<m:ss> <title>
126<m:ss> <title>
127...
128```
129 
130### 5. Write it into your content record
131 
132Put the assembled block where your content lives so it's tracked and
133copy-pasteable:
134- **Markdown content vault**: add or replace a `## YouTube description`
135 section in the video's `.md` file. Wrap the block in a fenced
136 ` ```text ` code block so line breaks survive the paste into YouTube.
137 The section is **idempotent** — replace the existing one, don't append
138 a second.
139- **Notion Content DB**: paste the block into the video row's body /
140 a "YouTube description" property.
141 
142Report back where you wrote it and the chapter count. Show the assembled
143block in chat too.
144 
145---
146 
147## Definition of done
148 
1491. A timestamped transcript exists for the video.
1502. A 2-sentence description in your voice (no em dashes, no banned words).
1513. The fixed CTA block, verbatim, between description and timestamps.
1524. Chapters starting at `0:00`, none past the printed duration.
1535. The whole block written into your content record as an idempotent
154 section, inside a copy-paste-ready code block, and the location reported.
155 
156---
157 
158## Don'ts
159 
160- **Don't pad the description.** Two sentences. (This is the opposite of
161 the terse-CTA-only rule in `/youtube-publisher`; here you explicitly
162 want the short description + timestamps. But "short" still means two
163 sentences.)
164- **Don't edit the CTA block.** Verbatim, including the LinkedIn URL (use
165 your canonical profile — no tracking params).
166- **Don't invent chapter times.** Every timestamp comes from the transcript.
167- **Don't push to the live YouTube video.** The content record only,
168 unless asked. To set descriptions live, `/youtube-publisher`'s
169 finalize step (`--only-descriptions`) is the path.
170- **Don't burn Scribe on an existing transcript.** Check for a
171 `/video-use` JSON first and reuse it.
172 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 37
Checked
Source
timscheuerai/content-vault ↗
Creator
timscheuerai · 15 listings
View creator

Similar skills

See all →
SkillYouTube Channel AuditorJakeschincariol/youtube-agent-skill · by JakeschincariolAudit a YouTube channel end to end - packaging, consistency, the first fifteen seconds, and what to fix first. Use for "audit my channel", "why isn't my channel growing", "review my videos", or a pasted channel URL.★ 1.1k GitHub starsSkillYouTube Channel Rewritersergebulaev/youtube-skills · by sergebulaevAudit and rewrite a YouTube channel end-to-end for 2026: name and @handle, banner (2560x1440 with the 1235x338 mobile/TV safe area), profile picture, About plus searchable keywords, trailer for non-subscribers vs featured video for subscribers, sections and playlist layout, watermark, links. Triggers on "optimize my YouTube channel", "rewrite my channel about", "fix my banner", "channel audit", "set my trailer". Converts a viewer into a subscriber. Not for writing a video title (use yt-title-optimizer).★ 36 GitHub starsSkillAd Fatigue Manageraaron-he-zhu/aaron-marketing-skills · by aaron-he-zhuUse when the user asks to "is my ad fatiguing", "why is CTR dropping at scale", or "should I rotate creative / widen the audience"; reads frequency, CTR and CVR decay against an early-flight baseline and returns Rotate-creative / Widen-audience / Hold triggers with a per-ad-set fatigue read. Not for building the replacement creative — use ad-creative-builder; not for the RQS score or vetoes — use ad-account-auditor. 广告疲劳检测/频次管理/换素材还是扩人群★ 2.9k GitHub starsSkillPricing Tier Architectwondelai/skills · by wondelai- Leaders, Fillers, Killers★ 2.2k GitHub starsSkillTitle Thumbnail PackagerJakeschincariol/youtube-agent-skill · by JakeschincariolWrite and lint the title and thumbnail for a YouTube video as one pairing, checking truncation, duplication and vagueness before publish. Use for title ideas", "what should I call this", "thumbnail text", "my CTR is bad", packaging, or any request to rename or repackage an existing video.★ 1.1k GitHub starsSkillYouTube SEO Optimizerkostja94/marketing-skills · by kostja94When the user wants to optimize YouTube videos for search, create video descriptions, or improve channel visibility. Also use when the user mentions "YouTube SEO," "YouTube description," "YouTube tags," "YouTube thumbnail," "YouTube title," "YouTube channel," or "video SEO." For YouTube ads, use youtube-ads.★ 1k GitHub stars

More from timscheuerai

SkillLaunch Video Creatortimscheuerai/content-vault · by timscheueraiBuild a 30-60s motion-graphics launch video for a <YOUR_BRAND> product or feature. Remotion 4 React composition + ElevenLabs AI narration + sound effects + background music, beat-anchored timing, brand-aligned design system. Use when asked to "create a launch video", "make a product video", "video for X feature", "launch a new feature", or "/launch-video".★ 37 GitHub starsSkillLinkedIn Voice Copywritertimscheuerai/content-vault · by timscheueraiDraft LinkedIn posts in YOUR voice. Pulls hook frameworks, structural patterns, and CTA shapes from your real top-performing posts (corpus.md), runs the draft through a strict AI-slop blacklist, and outputs a post that reads like you wrote it. Use when asked to "write a linkedin post", "draft a post about X", "linkedin copy", "post idea", or "/linkedin-copywriter".★ 37 GitHub starsSkillLong-Form Draftertimscheuerai/content-vault · by timscheueraiDraft written long-form content (newsletter issue, blog post, Substack issue) in your voice. 800-2000 words, structured intro + body + CTA, paragraph-by-paragraph not list-by-list. Pulls voice from /linkedin-copywriter's corpus (same author, same register · longer arc). Runs the brand-doc skill checklist before output. Logs the row in the Notion Content DB and (for newsletters) drafts a separate punchy subject line. Use when asked to "write a newsletter", "draft a blog post", "long-form X", "Substack issue about Y", "weekly newsletter", or "/long-form". For spoken video scripts (YouTube longs / shorts) use /youtube-script instead · the cadence is fundamentally different.★ 37 GitHub starsSkillMathematical Animation Pipelinetimscheuerai/content-vault · by timscheueraiProduction pipeline for mathematical and technical animations using Manim Community Edition. Creates 3Blue1Brown-style explainer videos, algorithm visualizations, equation derivations, architecture diagrams, and data stories. Use when users request: animated explanations, math animations, concept visualizations, algorithm walkthroughs, technical explainers, 3Blue1Brown style videos, or any programmatic animation with geometric/mathematical content.★ 37 GitHub starsSkillContent Repurposertimscheuerai/content-vault · by timscheueraiTake one master content piece (Notion row, transcript, video, paragraph, URL) and spin off variants across channels. Hub-and-spoke repurposing engine. Reads the source, identifies key insights / hooks / quotable moments, then creates child rows in the Notion Content DB with drafts already written by calling sub-skills (linkedin-copywriter, x-copywriter, lead-magnet-creator, etc.). Use when asked to "repurpose this", "spin off variants", "turn this into LinkedIn + X + ...", "make derivatives of this webinar / video / post", or "/repurpose".★ 37 GitHub starsSkillContent Idea Pipelinetimscheuerai/content-vault · by timscheueraiThe single idea-generation pipeline for marketing content. Three input modes converging on Notion Status=Idea rows. Trend scan (X + LinkedIn creators + topic search) finds what's hot in the world. Performance scan (your own published rows + their engagement metrics) finds what's working for you so you can double down. Customer scan (HUMAN NOTES DB user-interview transcripts) finds the words, pains, and themes from real customer conversations. Hybrid mode runs all three, dedupes, and outputs a balanced backlog. Use when asked to "find content ideas", "what's working", "what's hot", "what are customers saying", "research", "scan trends", "give me ideas for the week", "/researcher", or proactively when the Notion Idea queue is empty.★ 37 GitHub stars