youtube-organic
Skill3 starsChanged 46 days agoMITView on GitHub
Use when developing YouTube organic strategy — channel audit, traffic-source diagnosis, title and thumbnail strategy, retention and hook structure, upload cadence, Shorts-to-long-form funnel and subscriber growth. Also use when someone asks "why aren't my videos getting views", wants a content plan for a channel, or needs help choosing video length and series formats. Don't use for YouTube Ads, live-event production, or monetization and sponsorship deals.
In this repository14 other files it gives its agents.
- brandingSkill
- competitor-researchSkill
- geo-ai-seoSkill
- google-ads-diagnosticsSkill
- google-ads-keywordsSkill
- gtm-debuggingSkill
- instagram-organicSkill
- landing-page-funnelSkill
- linkedin-organicSkill
- market-positioningSkill
- meta-ads-creativeSkill
- meta-ads-diagnosticsSkill
- pinterest-organicSkill
- tiktok-adsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 29
Don't use for: YouTube Ads campaigns, live-stream production, monetisation policy, sponsorship negotiation, or editing software tutorials.
- Distinctive: line 33
Ask for (or extract from the conversation):
- Distinctive: line 142
Use the "related video" link on Shorts to point to the long-form
- Distinctive: line 228
Treating low CTR as a thumbnail failure in isolation: Read CTR with impressions.
- Distinctive: line 230
Random uploads: No series means no returning viewers.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
YouTube Organic Strategy
Overview
Build a data-informed plan for a YouTube channel: audit the channel and its recent uploads, diagnose where views come from, fix the two levers that gate distribution (click-through rate from title + thumbnail, and retention), define pillars and series, set a sustainable cadence, and decide how Shorts feed long-form. YouTube is a recommendation engine and a search engine; it rewards videos that get clicked by the people shown them and then keep them watching.
When to Use
- Auditing a channel and its last 20–30 videos
- Diagnosing low views, low CTR or poor retention
- Planning series, cadence and video length
- Building a Shorts strategy that supports long-form
- Optimising titles, thumbnails, descriptions and channel pages
Don't use for: YouTube Ads campaigns, live-stream production, monetisation policy, sponsorship negotiation, or editing software tutorials.
Inputs
Ask for (or extract from the conversation):
- Channel URL and goal (subscribers, watch time, leads, product sales, authority)
- YouTube Studio screenshots (last 28–90 days): traffic sources, impressions and CTR, average view duration and percentage viewed, audience retention curves of 3–5 recent videos, returning vs new viewers, subscribers gained per video, Shorts vs long-form breakdown
- Last 20–30 uploads: title, length, publish date, views, and whether Shorts or long-form
- Production capacity: how many videos per month can realistically be made at what quality
- Niche and competitors the user watches or benchmarks against
Data rules: if you can fetch the channel, record the public data (subscribers, video count, titles, view counts, upload dates, thumbnails as described); if not, say so and ask for screenshots — never estimate CTR or retention. Benchmarks are starting points; Studio's own "typical performance" comparison beats them. YouTube changes limits and features (Shorts up to 3 minutes since Oct 2024, thumbnail Test & Compare, Communities, Hype); if the UI differs, follow the UI and note it.
Audit Workflow
Step 1: Channel analysis
| Metric | Where | Why |
| Subscribers, total views, video count | Channel home / About | Baseline |
| Banner, trailer, About, links | Home | Clarity of promise to a new visitor |
| Last 20–30 uploads | Videos / Shorts tabs | Cadence, formats, topics |
| Views per video vs subscriber count | Videos tab | Health: long-form views at 10–30% of subscribers within a week is normal |
| Top 10 videos all time | Popular sort | What already resonates |
| Playlists and sections | Home layout | Session guidance |
From Studio: traffic sources, impressions CTR, average view duration (AVD) and average percentage viewed, retention curves, returning viewers, subscribers per video.
Step 2: Traffic source diagnosis (the most important read)
| Dominant source | Meaning | Action |
| Browse features (home, subscriptions) > 40% | YouTube is recommending to a warm audience; CTR and retention are strong | Protect cadence and series; raise production on hooks |
| Suggested videos > 30% | Videos sit next to related content | Make sequels and playlists; mirror topics that drive suggestions |
| YouTube search > 40% | Found by intent | Double down on searchable titles, chapters and descriptions; evergreen library |
| Shorts feed dominant | Reach without loyalty unless funnelled | Build the Shorts → long-form bridge (below) |
| External > 20% | Growth depends on other platforms | Fine as a start; build internal discovery so the channel stands on its own |
Step 3: CTR and retention
| Metric | Weak | Typical | Strong |
| Impressions CTR (long-form) | < 3% | 4–6% | > 8% |
| Average percentage viewed (8–15 min video) | < 35% | 40–50% | > 55% |
| Retention at 30 s | < 60% | 65–75% | > 80% |
| Shorts: viewed vs swiped away | < 60% viewed | 65–75% | > 80% |
CTR is relative to who sees the impressions: a broad push lowers CTR without meaning the thumbnail got worse. Read CTR together with impressions and AVD.
Retention curve reading: a cliff in the first 30 seconds = intro problem; a steady slide = pacing; spikes = re-watched moments to repeat; a dip then recovery = a segment to cut.
Step 4: Title and thumbnail audit
| Element | Good | Fix |
| Title | Specific outcome or curiosity gap, ≤ 60 characters visible, no clickbait the video cannot pay off | Add the payoff, remove filler, front-load the keyword for search |
| Thumbnail | One focal subject, high contrast, ≤ 3 words of text, readable at 120 px | Remove clutter; face with emotion or object with contrast |
| Title + thumbnail | Complementary (title says what, thumbnail shows why or the stakes) | Never repeat the same words in both |
| Consistency | Recognisable style per series | Template per series |
| Testing | Use Test & Compare (up to 3 thumbnails) on new uploads | Test one variable at a time |
Strategy Formulation
Content pillars and series (3–5)
| Pillar type | Drives | Example formats |
| Evergreen how-to / tutorial | Search, library value | "How to X", "Complete setup" |
| Commentary / analysis | Suggested and browse | "Why X failed", "X explained" |
| Case study / experiment | Trust and watch time | "We tested X for 30 days" |
| Series with a recurring hook | Returning viewers | Weekly teardown, Q&A, ranking |
| Story / behind the scenes | Connection, community | "How I built X" |
Mix for most channels: ~50% searchable evergreen, 20% timely, 20% series for returning viewers, Shorts as a parallel track rather than a percentage of long-form.
Cadence
Consistency and quality beat frequency. Choose the cadence the team can hold for 6 months.
| Stage | Long-form | Shorts | Posts (community) |
| < 1K subs | 1/week | 2–4/week to test hooks and topics | Occasional |
| 1K–10K | 1–2/week | 3–5/week | Weekly poll or teaser |
| 10K–100K | 1–2/week plus a series slot | 3–7/week | 2–3/week |
| > 100K | 2+/week with a team | Daily if resourced | Regular |
Publish at a fixed slot; Studio's "when your viewers are on YouTube" beats generic time tables. Premieres and Posts can warm the slot.
Video structure for retention
| Section | Rule |
| Hook (0–15 s) | Show the payoff or the stakes; no "hi guys, welcome back"; the first frame should match the thumbnail's promise |
| Credibility (one line) | Why this video, why you — then move on |
| Body | A visual or structural change every 60–90 seconds; chapters in the description; deliver a concrete takeaway every 3–4 minutes |
| Open loops | Tease what is coming ("the third one is the one that broke") without stalling |
| Ending | One CTA to the next best video (end screen); do not stack subscribe/like/comment/follow |
Video length by goal
| Goal / genre | Typical length | Why |
| Tutorials | 8–15 min | Depth without drop-off |
| Commentary / analysis | 10–20 min | Argument needs runway |
| Deep dives / documentary | 20–40 min | High watch time per viewer if retention holds |
| News / timely | 6–12 min | Fast consumption |
| Shorts (reach) | 15–45 s | Highest completion and loops |
| Shorts (storytelling, up to 3 min) | 60–120 s | Only when the story holds; viewed-vs-swiped is the metric |
Shorts → long-form funnel
- Each Short carries one idea from a long-form video and ends on a question the long video answers
- Use the "related video" link on Shorts to point to the long-form
- Match the Short's topic to the channel's long-form so the audience overlap is real
- Track subscribers and long-form views from Shorts viewers in Studio; Shorts audiences convert weakly unless the bridge is explicit
Growth tactics
| Tactic | Effort | Impact | Why |
| Thumbnail Test & Compare on every upload | Low | Very high | Directly lifts the gatekeeper metric |
| Rewrite the first 30 seconds | Medium | Very high | Early retention decides distribution |
| Series with a recurring hook | Medium | Very high | Returning viewers and browse distribution |
| Playlists and end screens to the next video | Low | High | Session time and suggested traffic |
| Search-first titles for evergreen | Low | High | Compounding library views |
| Shorts bridge | Medium | High | Reach that converts |
| Collaborations with channels 2–5× your size | Medium | High | Audience transfer |
| Posts and polls between uploads | Low | Medium | Keeps subscribers warm, informs topics |
| Localisation (auto-dubbing, translated titles) | Low | Medium | New language markets at near-zero cost |
Channel Page Checklist
- Banner states who the channel is for and the upload promise
- Trailer for new visitors (30–60 s "why watch") and a different featured video for returning subscribers
- About with keywords, links and a contact
- Handle set (youtube.com/@name)
- 4–8 playlists matching pillars, arranged as home sections
- End-screen and card templates
- Default upload settings: description template with chapters, links, disclosure where needed
- Altered or synthetic content disclosure set when AI-generated media is used
Output Format
YOUTUBE AUDIT: [Channel] (URL)
Goal: [..] | Access: [fetched / Studio screenshots]
Subscribers: X | Videos: Y | Total views: Z | Avg views (last 20 long-form): W
--- CURRENT STATE ---
Format mix: Long-form X% / Shorts Y% / Live Z%
Cadence: X long-form/week, Y Shorts/week
Traffic sources: Browse X% / Suggested Y% / Search Z% / Shorts feed … / External …
CTR: X% | Avg view duration: Y | Avg % viewed: Z% | Returning viewers: W%
Top performers: [3 videos — why]
--- STRENGTHS ---
- [...]
--- GAPS ---
- [...]
--- CONTENT PILLARS & SERIES (3–5) ---
1. [Pillar] — [Series name/hook] — [Length] — [Frequency]
2. [...]
--- CADENCE ---
Long-form: [..] | Shorts: [..] | Posts: [..] | Slot: [from Studio or stated fallback]
--- TITLE & THUMBNAIL ---
[Current pattern] → [Recommended pattern]
Examples: [3 title rewrites with thumbnail concept]
Testing: [Test & Compare plan]
--- RETENTION FIXES ---
[Intro structure, pacing, chapters, open loops, ending]
--- SHORTS STRATEGY ---
[Bridge to long-form, cadence, metrics]
--- GROWTH PLAN ---
0–30 days: [3 actions]
30–90 days: [3 actions]
90+ days: [3 actions]
KPIs: [CTR, AVD/%, returning viewers, subs per video, browse share]
--- CHANNEL PAGE ---
[Banner, trailer, About, playlists, end screens]
--- ASSUMPTIONS & MISSING DATA ---
[...]Common Pitfalls
- Long intros. The first 15–30 seconds lose a third of viewers on most channels. Start with the payoff.
- Thumbnail repeating the title. They should carry different information: what vs why/stakes.
- Treating low CTR as a thumbnail failure in isolation. Read CTR with impressions; a broader push lowers CTR naturally.
- Random uploads. No series means no returning viewers; returning viewers are the browse engine.
- Shorts without a bridge. Reach without conversion; make the link to long-form explicit.
- Ignoring Studio. Traffic sources and retention curves are free, specific and actionable.
- Chasing frequency. Two forgettable videos a week lose to one that keeps people watching.
- One CTA too many. Stacked asks dilute; point to the next video.
Verification Checklist
- Last 20–30 uploads reviewed (or the limitation stated); no CTR/retention figures invented
- Traffic sources diagnosed and tied to actions
- CTR read together with impressions and AVD, benchmarked
- Retention curves interpreted (intro cliff, pacing, spikes) where provided
- 3–5 pillars with at least one recurring series
- Cadence matched to capacity for long-form, Shorts and Posts
- Title and thumbnail recommendations with concrete rewrites and a Test & Compare plan
- Shorts strategy includes an explicit bridge to long-form
- Channel page checklist applied
- Growth plan split 0–30 / 30–90 / 90+ days with KPIs
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
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.

