Skip to content

sergebulaev/youtube-skills / .codex-marketplace/youtube-skills/skills/yt-content-planner

yt-content-planner

Verified

Build a weekly YouTube upload plan: long-form vs YouTube Shorts mix, posting cadence, per-slot title and thumbnail pairing, hook angle, community-tab posts between uploads, and a goal balance across CTR, retention, and subscribes. Maps Shorts as top-of-funnel that points at long-form, and long-form as the loyalty and watch-time engine. Use to plan a week or a content calendar instead of shipping ad hoc. Not for writing a single title, description, or hook (use the dedicated yt skills).

FileKindSize
SKILL.mdskill md5.0 KB
references/example-week.mdmarkdown3.0 KB
references/pillars-framework.mdmarkdown3.0 KB

references/pillars-framework.md

View on GitHub
# Pillars Framework

How to turn a niche into 3 to 5 content pillars and a balanced long-form vs
Shorts mix.

## What a pillar is

A pillar is a recurring topic lane your channel owns. 3 to 5 is the right number:
fewer and the channel feels thin, more and the audience cannot predict what you
do. Each video lives in exactly one pillar.

## Finding your pillars

| Source | Question |
|---|---|
| Expertise | what can you teach that most of your audience cannot? |
| Demand | what do people in your niche search for and click? |
| Differentiation | what angle is yours that competitors do not own? |
| Sustainability | what can you make every week without burning out? |

Pick the 3 to 5 lanes that sit where all four overlap.

## Example pillar sets

**A solo dev / build-in-public channel:**
- Build logs (shipping a real product on camera)
- Tool teardowns (a deep look at one tool)
- Mistakes and lessons (what broke and why)
- Quick tips (Shorts territory)

**An editing / creator-education channel:**
- Tutorials (how to do a specific technique)
- Gear and software comparisons
- Channel audits / teardowns
- 60-second technique Shorts

## Long-form vs Shorts: the two jobs

| Format | Job | What it earns | Measure with |
|---|---|---|---|
| **Long-form** | depth, loyalty, watch-time, revenue | returning viewers, session time, subscribes that stick | average view duration, returning viewers |
| **Shorts** | reach, discovery, top-of-funnel | new eyeballs, swipe-throughs, channel visits | views, swipe-away rate, loop rate |

Shorts bring people in; long-form keeps them. A Shorts-only channel grows
subscribers that watch little. A long-form-only channel grows slowly. Use both,
with a through-line: Shorts tease or excerpt the long-form library.

## Sizing the mix by stage

| Stage | Suggested weekly mix | Note |
|---|---|---|
| **New (0 to 1k subs)** | 1 long-form + 4 to 5 Shorts | Shorts for discovery while you find your packaging |
| **Growing (1k to 50k)** | 1 long-form + 3 Shorts | long-form starts to compound; keep Shorts feeding it |
| **Established (50k+)** | 1 to 2 long-form + 2 to 3 Shorts | long-form is the engine; Shorts top up reach |

These are starting points. The real rule: pick a cadence you can hold for 12
weeks. Consistency trains both the audience and the algorithm.

## The through-line

Every Short should have a reason to exist relative to the library:

- A 60-second excerpt of a long-form's best moment, ending "full breakdown on the
  channel".
- A standalone tip that proves you are worth subscribing to for the long-form.
- A tease of an upcoming long-form.

A Short with no through-line earns views that never convert to watch-time.

## Goal balance across the week

Tag each slot with its primary goal and make sure the week is not all one note:

- **CTR-first** pieces (broad, curiosity-driven) bring new viewers.
- **Retention-first** pieces (deep, satisfying) build watch-time and loyalty.
- **Subscribe-first** pieces (a clear "more like this is coming" payoff) convert.

A healthy week has all three. All CTR-bait grows shallow; all deep tutorials grow
slow.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall