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

youtube-short

Skill0 starsChanged 3 months agoMITView on GitHub

Creates YouTube Shorts (1080x1920, under 60s) from existing video content. Handles safe zones, title cards, CTA with voiceover, background music, and rendering. Use when the user wants to create Shorts, TikToks, or Reels from existing techniques, stories, or video segments.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    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:

    Every Short follows this structure:

    line 21
  2. Distinctive:

    Don't put text in the top 15% or bottom 25% — YouTube UI covers it

    line 55
  3. Distinctive:

    Don't make the title card longer than 0.5s — viewers skip if the first frame is static too long

    line 56
  4. Distinctive:

    Don't speed up CTA voiceover — it should feel natural and unhurried

    line 57
  5. Distinctive:

    Don't use HeyGen avatar clips in Shorts unless they're already generated — terminal visuals work fine

    line 58
  6. Distinctive:

    Don't forget the bg music ramp at the end — silence on the CTA feels abrupt

    line 59
  7. Distinctive:

    Don't forget to normalize loudness — Shorts from different renders should sound consistent

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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 Short

Instructions

Format Rules

  • Resolution: 1080x1920 (9:16 vertical)
  • Max duration: 60 seconds
  • Safe zones: Content must stay in the middle 60% of the screen
    • Top 15% clear — YouTube overlays title and channel name
    • Bottom 25% clear — YouTube overlays comments, like button, share
  • No text or important visuals in the safe zone margins

Structure

Every Short follows this structure:

  1. Title card (~0.3s / 10 frames) — Just a flash for the cover/thumbnail frame. Shows technique number, title, and Claude Code logo. Must look good as a static image since this is what viewers see before pressing play.
  2. Content — The technique scene with terminal visuals, voiceover audio, and synced captions. Reuses the same shot rendering as the main video.
  3. CTA (~2.5s / 75 frames) — the brand domain from Brand.md, with an ElevenLabs voiceover saying "Full breakdown at {domain}" at natural 1x speed (not 1.1x — CTA should feel unhurried).

Audio

  • Voiceover: ElevenLabs at 1.1x speed for technique content (no HeyGen in Shorts). Captions must be re-timed by dividing timestamps by 1.1.
  • Background music: bg-music-short.mp3 plays throughout at volume 0.05
  • Music ramp at CTA: Background music ramps from 0.05 to 0.2 during the CTA for a natural ending feel
  • CTA voiceover: Separate ElevenLabs clip at 1x speed, plays over the ramping music

Rendering

Render each Short individually:

npx remotion render {ShortCompositionId} --image-format png --video-bitrate 30M --output out/short-1-raw.mp4

Then two-pass loudness normalize to -14 LUFS:

# Pass 1: measure
ffmpeg -i short-1-raw.mp4 -af loudnorm=I=-14:TP=-1:LRA=11:print_format=json -f null -
# Pass 2: apply
ffmpeg -y -i short-1-raw.mp4 -af loudnorm=I=-14:TP=-1:LRA=11:measured_I=X:measured_TP=Y:measured_LRA=Z:measured_thresh=W:offset=O:linear=true -c:v copy short-1.mp4

Save to vault: Stories/{slug}/assets/short-{n}.mp4

What NOT to do

  • Don't put text in the top 15% or bottom 25% — YouTube UI covers it
  • Don't make the title card longer than 0.5s — viewers skip if the first frame is static too long
  • Don't speed up CTA voiceover — it should feel natural and unhurried
  • Don't use HeyGen avatar clips in Shorts unless they're already generated — terminal visuals work fine
  • Don't forget the bg music ramp at the end — silence on the CTA feels abrupt
  • Don't forget to normalize loudness — Shorts from different renders should sound consistent

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.