youtube-marketing

Files (42)

• marketplace.json · .agents/plugins/
• marketplace.json · .claude-plugin/
• plugin.json · .claude-plugin/
• plugin.json · .codex-plugin/
• .codexignore
• .env.example
• dependabot.yml · .github/
• hol-plugin-scanner.yml · .github/workflows/
• verify-references.yml · .github/workflows/
• .gitignore
• AGENTS.md
• CLAUDE.md
• LICENSE
• README.md
• SECURITY.md
• SKILL.md
• hero.png · assets/
• icon.svg · assets/
• social-preview.jpg · assets/
• __init__.py · lib/
• _env.py · lib/
• approval.py · lib/
• backend_selector.py · lib/
• pixfaro_client.py · lib/
• publora_client.py · lib/
• url_parser.py · lib/
• youtube_client.py · lib/
• algorithm-heuristics.md · references/
• hook-formulas.md · references/
• thumbnail-principles.md · references/
• untrusted-content.md · references/
• voice-profile.md · references/
• voice-rules.md · references/
• requirements-lock.txt
• requirements.txt
• check_frontmatter.py · scripts/
• check_markdown_references.py · scripts/
• check_no_secrets.py · scripts/
• check_security_boundaries.py · scripts/
• check_text_encoding.py · scripts/
• check_untrusted_rule.py · scripts/
• sync_codex_marketplace.py · scripts/

SKILL.md (first lines)

# YouTube Marketing Skills

A bundle of 9 focused skills for YouTube content ops in 2026, covering both
long-form and YouTube Shorts. Each skill is single-purpose, follows the draft
then approval then publish pattern, and uses the [Publora API](https://publora.com/?utm_source=github&utm_medium=skill&utm_campaign=youtube-skills)
for uploading and scheduling the video you supply.

## When to use this bundle

- **Writing high-CTR titles** (curiosity, number, how-I, comparison) with A/B variants -> use `yt-title-optimizer`
- **Writing the description** (first-150-char hook, chapters, keywords, links) -> use `yt-description-writer`
- **Scripting the first 30 seconds for retention** (or the first 3 seconds of a Short) -> use `yt-hook-scripter`
- **Briefing a thumbnail** (text overlay, face/emotion, contrast) plus the upload flow -> use `yt-thumbnail-brief`
- **Writing a community-tab post or poll** -> use `yt-community-post-writer`
- **Planning a week of uploads** (long-form vs Shorts mix, title/thumbnail pairing) -> use `yt-content-planner`
- **Repurposing off-platform content** (a blog post, thread, or LinkedIn post) into a YouTube community post or a video brief -> use `yt-repurposer`
- **Auditing and rewriting the channel page** (banner, trailer, About, playlists, section order) to convert viewers into subscribers -> use `yt-channel-optimizer`
- **Reading your audience from the comments (who commented, themes, superfans, trending)** -> use `yt-audience-insights`

## Core pattern

Every action-taking skill follows three steps:

1. **Parse the input.** If the user gives a YouTube URL, the skill uses
   `lib/url_parser.py` to extract the video id, Short id, channel, or handle.
2. **Draft the content.** The skill applies 2026 research (title and hook
   formulas, CTR x retention heuristics, thumbnail principles, voice rules) and
   shows the draft to the user.
3. **Wait for approval.** The user replies "publish", "yes", or suggests edits.
   Only after explicit approval does the skill upload and schedule via Publora.

## Why YouTube is video-first (read this once)

YouTube is a **video-only platform**: every published post requires a single
video file, which the user supplies. The skills write the title, description,
hook script, and thumbnail brief; you bring the .mp4. On approval the upload
follows the documented Publora flow:

1. `create-post` with no scheduledTime -> creates a **draft**, returns a `postGroupId`
2. `get-upload-url` -> a pre-signed S3 URL
3. PUT your video to S3
4. `update-post/:postGroupId` -> set the scheduledTime (and any youtube settings)

A custom thumbnail is set **after** the draft exists, via `update-post` (the
thumbnail upload needs the `postGroupId`), never on `create-post`. YouTube
community-tab posts have no Publora endpoint, so `yt-community-post-writer`
always returns a copy-paste block.

## Prerequisites

**Three tiers - pick one.**

### Tier 0 - Draft only (default, no setup)

The skills work out of the box. No API keys, no signup. Every approved draft is
returned as a copy-paste block (title + description, hook script, thumbnail
brief, or community post) for you to use in YouTube Studio. Great for trying the
skills before committing to any backend.

### Reading YouTube data (orthogonal to the tiers above)

`yt-audience-insights` and the planner read comments, video and channel stats
and trending through the YouTube Data API v3, gated on `YOUTUBE_API_KEY`. That
is Google's API, not Apify, so **there is no connector path**: the sibling
bundles can be read on claude.ai through Apify's MCP server, and this one
cannot. On claude.ai, ask the user to paste titles, stats or comments and say
why. With neither key nor paste, do not estimate the numbers.

### Tier 1 - Publora auto-upload (recommended, ~2 min)

On approval, the writer skills upload and schedule the video you supply via the
[Publora API](https://publora.com/?utm_source=github&utm_medium=skill&utm_campaign=youtube-skills).

1. Sign up free: **https://app.publora.com/signup?utm_source=github&utm_medium=skill&utm_campaign=youtube-skills**
2. Connect your YouTube channel in Publora (Channels then Add Channel, Google OAuth)
3. Copy your API key from Publora's API panel
4. Drop into `.env`:
   ```
   PUBLORA_API_KEY=sk_...
   YOUTUBE_PLATFORM_ID=youtube-UC...
   ```
5. Run `pip install -r requirements.txt`

Why Publora: uploading to YouTube on the native Data API means a Google OAuth
flow, the resumable-upload protocol, and quota tracking. Publora does the draft,
the S3 upload, the schedule, and the metadata in a handful of REST calls. We
built on top of it so we did not have to reimplement the upload chain.

### Tier 2 - Build your own uploader (advanced)

Prefer not to SaaS it? Ask Claude Code or Codex to build a custom uploader on the
YouTube Data API. Set `YOUTUBE_SKILLS_CUSTOM_POSTER=<your command>` and the
skills invoke it on approval. Publora is the 2-minute path.

### Note on community posts

YouTube community-tab posts and polls have no Publora endpoint, and there is no
public API for them. So `yt-community-post-writer` always returns its draft as a
copy-paste block for you to post in the Community tab yourself. Videos and Shorts
upload and schedule through Publora normally.

## Voice rules (baked into every skill)

1. Em dashes (`—`) capped at about 1 per 100 words (at most one in a title or community post; `..` in a spoken line); replace the excess with a comma, colon or line break, never a period. No en dashes between clauses, no double dashes.
2. Use `..` as a soft pause in a script line when rhythm calls for it.
3. Capitalize all personal, company, and product names.
4. Specific numbers beat adjectives. "in 28 days" beats "fast".
5. Title is a promise, not a summary. Curiosity plus a concrete payoff.
6. Title and thumbnail are a pair. They never repeat the same words.
7. The first 30 seconds (or 3 on a Short) is the real algorithm. No intro.
8. Title caps at 100 chars (sweet spot 40 to 60). Description caps at 5,000, first 150 visible.
9. Avoid AI vocabulary clusters: one 2026 marker (`leverage`, `significant`, `streamline`, `foster`) in a paragraph is English, three in one paragraph reads as AI and the paragraph gets rewritten; in a one-line title any marker goes. No sincerity openers ("let me be honest", "not gonna lie").
10. Do not keyword-stuff. Natural language with the real search phrase once.

(Canonical reference: `references/voice-rules.md`. See also
`references/hook-formulas.md`, `references/algorithm-heuristics.md`, and
`references/thumbnail-principles.md`.)

## How YouTube URLs map

From sergebulaev/youtube-skills, MIT.

More from sergebulaev/youtube-skills