agentleFS
allthriveaiallthriveai/amplify/.claude/skills/youtube-description/SKILL.md

youtube-description

Skill0 starsChanged 3 months agoMITView on GitHub

Writes YouTube video descriptions optimized for search, engagement, and click-through. Use when the user runs /youtube-description, shares a video topic, or asks for help writing a YouTube description. Applies humanizer rules to all prose.

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use youtube-thumbnail.

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.

The file

Show its rules and text

We split this skill into the rules it gives an agent

21 rules. 0 are common, 21 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 21

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write a YouTube video description that serves two audiences: the algorithm and the human viewer.

    line 10
  2. Distinctive:

    Ask the user for:

    line 14
  3. Distinctive:

    If the user provides a script, voiceover text, or video file, use that as the source material instead of asking.

    line 19
  4. Distinctive:

    Read Voice.md from the vault if it exists.

    line 21
  5. Distinctive:

    Write like a hook, not a summary

    line 30
  6. Distinctive:

    Never start with "Hey everyone", "Welcome back", "In this video I..."

    line 31
  7. Distinctive:

    Never start with the channel name

    line 32
  8. Distinctive:

    Use line breaks between every section

    line 71
  9. Distinctive:

    Every link needs a one-line reason to click

    line 74
  10. Distinctive:

    Before presenting the final description, check for and remove:

    line 80
  11. Distinctive:

    If the user provides a video URL, offer to write timestamps based on the content.

    line 95
  12. Distinctive:

    Never keyword stuff (repeating the same phrase 5+ times)

    line 99
  13. Distinctive:

    Never use more than 5 hashtags (YouTube ignores ALL hashtags if you exceed 15, and more than 5 looks spammy)

    line 100
  14. Distinctive:

    Never write a wall of text with no line breaks

    line 101
  15. Distinctive:

    Never copy-paste identical descriptions across videos

    line 102
  16. Distinctive:

    Never include irrelevant hashtags for reach

    line 103
  17. Distinctive:

    Never bury the primary link at the bottom

    line 104
  18. Distinctive:

    Never use clickbait that doesn't match the video content

    line 105
  19. Distinctive:

    Never write "Like and subscribe!" as filler

    line 106
  20. Distinctive:

    Never use the rule of three ("informative, engaging, and transformative")

    line 107
  21. Distinctive:

    Never use negative parallelisms ("It's not just X.

    line 108

“Common” is measured: kept by at least 6 in 10 of the 5 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 Description

Instructions

Write a YouTube video description that serves two audiences: the algorithm and the human viewer. The description must feel like it was written by the creator, not assembled by a tool.

Step 0: Gather Context

Ask the user for:

  1. What is the video about? (topic, angle, key takeaway)
  2. Who is it for? (audience)
  3. What is the one thing you want viewers to do after watching? (primary CTA: visit a site, subscribe, download something, watch another video)

If the user provides a script, voiceover text, or video file, use that as the source material instead of asking.

Read Voice.md from the vault if it exists. Match the creator's tone.

Step 1: Write the Hook (First 150 Characters)

This is the most important part. These characters appear in YouTube search results, Google search results, and above the "Show more" fold.

Rules:

  • Include the primary keyword in the first 25 words
  • Answer: "What is this video about?" and "Why should I watch?"
  • Write like a hook, not a summary
  • Never start with "Hey everyone", "Welcome back", "In this video I..."
  • Never start with the channel name
  • Be specific about the outcome or value

Present the hook to the user for approval before continuing.

Step 2: Write the Full Description

Structure (in this order):

[HOOK: 2-3 lines] — above the fold
  Primary keyword in first 25 words
  Specific outcome or value promise

[VALUE: 3-5 lines] — what the viewer gets
  Key points covered in the video
  Natural keyword variations (not stuffing)

[PRIMARY CTA + LINK] — one main action
  One line explaining why to click
  The link

[WATCH NEXT] — internal link
  Link to a related video on the channel

[TIMESTAMPS] — if video is over 5 minutes
  0:00 Introduction
  X:XX Keyword-rich section labels

[RESOURCES] — tools, links, references mentioned
  Each link gets a one-line reason to click
  No bare URLs without context

[HASHTAGS] — 3-5 at the end
  1 broad, 2 mid-tier, 1-2 niche

Rules:

  • Total length: 150-300 words (800-1,500 characters)
  • Use line breaks between every section
  • Format for mobile first
  • Include the primary keyword 3-4 times naturally, never more
  • Every link needs a one-line reason to click
  • One primary CTA per description, placed after the value section
  • Match the description to actual video content. If the video doesn't cover it, don't mention it

Step 3: Apply Humanizer Rules

Before presenting the final description, check for and remove:

  • AI vocabulary (delve, landscape, crucial, leverage, robust, innovative, tapestry, multifaceted, holistic, comprehensive, pivotal, groundbreaking, paradigm, foster, encompasses)
  • Significance inflation ("stands as a testament to", "reflects broader themes of")
  • Filler phrases ("It's worth noting that", "Interestingly", "In today's X")
  • Em dash overuse. Use commas, colons, or periods
  • Sycophantic language
  • Promotional/brochure tone
  • Generic positive conclusions

The description should sound like the creator talking, not a marketing department.

Step 4: Present and Revise

Show the full description to the user formatted exactly as it would appear on YouTube. Ask if anything needs adjusting.

If the user provides a video URL, offer to write timestamps based on the content.

What NOT to Do

  • Never keyword stuff (repeating the same phrase 5+ times)
  • Never use more than 5 hashtags (YouTube ignores ALL hashtags if you exceed 15, and more than 5 looks spammy)
  • Never write a wall of text with no line breaks
  • Never copy-paste identical descriptions across videos
  • Never include irrelevant hashtags for reach
  • Never bury the primary link at the bottom
  • Never use clickbait that doesn't match the video content
  • Never write "Like and subscribe!" as filler
  • Never use the rule of three ("informative, engaging, and transformative")
  • Never use negative parallelisms ("It's not just X; it's Y")

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.