galloway-youtube-outlier-packaging
Skill5 starsChanged 12 days agoApache-2.0View on GitHub
Build a YouTube strategy, evidence-backed idea slate, and title plus thumbnail package using Paddy Galloway's public method. Use when planning a channel, choosing concepts, or preparing a video before filming.
In this repository168 other files it gives its agents.
- abel-sell-the-alphaSkill
- agent-governance-gap-analysisSkill
- agent-infra-fixerSkill
- agent-receiptSkill
- agent-skills-gapSkill
- ai-dnaSkill
- ai-festival-posterSkill
- ai-teamSkill
- albro-founder-brandSkill
- anatomySkill
- andy-raskin-strategic-narrativeSkill
- ar-aging-and-cash-applicationSkill
- asshauer-performance-contentSkill
- autonomous-researchSkill
- awwwards-sitesSkill
- better-typographySkill
- bourgoin-why-we-buySkill
- brain-scanSkill
- brath-b2b-demand-frameworkSkill
- braun-poke-the-bearSkill
- broll-pickerSkill
- claritySkill
- client-commsSkill
- cli-ux-reviewSkill
- clone-my-voiceSkill
- clone-yourselfSkill
- costa-negotiation-dynamicsSkill
- crawler-access-auditSkill
- cv-job-matchSkill
- data-globeSkill
- decision-ledgerSkill
- denney-persona-angle-formatSkill
- dicks-homework-five-secondSkill
- domain-uptime-monitorSkill
- dreyer-funnel-diagnosisSkill
- dry-three-copy-testsSkill
- dunford-obviously-awesomeSkill
- edge-find-skillsSkill
- fede-cloneSkill
- fede-voiceSkill
- fehr-clarity-taste-strategySkill
- fitzpatrick-mom-testSkill
- flores-founder-content-machineSkill
- founders-handbookSkill
- foxwell-meta-creativeSkill
- frankus-geo-auditsSkill
- gahan-b2b-creator-blueprintSkill
- generate-imageSkill
- geo-dominationSkill
- gerhardt-founder-brandSkill
- german-taxes-elsterSkill
- goetz-challenger-marketingSkill
- greger-creator-squadSkill
- handley-everybody-writesSkill
- harness-firstSkill
- hire-founding-engineerSkill
- hott-ugly-adsSkill
- http-error-triageSkill
- hubspot-crm-cleanupSkill
- humanizerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 20
Establish scope and inputs: Read references/method.md.
- Distinctive: line 24
Name the visible advantage: Follow references/method.md to identify distinctive knowledge, skill, personality, or access.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Paddy Galloway's YouTube Outlier Packaging
Based on Paddy Galloway's public method. Not affiliated with or endorsed by Paddy Galloway.
When to use
Use this skill to turn a channel brief into a focused strategy, prioritize video ideas, or prepare a title and thumbnail package before production. It also supports reviewing a channel whose uploads rarely exceed its usual view range. The central decision is which viewer promise deserves production effort, followed by how to communicate and fulfill that promise. [S1][S4]
Produce a readable strategy page with a supporting packaging appendix. Keep the page useful for decisions; put the evidence ledger, title candidates, and thumbnail briefs in the appendix. For a single upload, use the existing channel strategy and complete only the relevant fields. Do not force a full channel planning exercise into a narrow packaging request. Follow templates/output-template.md for either scope.
The method primarily concerns long form YouTube. Treat Shorts, business models, and device-specific production as optional context when they affect the brief. Galloway's numerical recommendations are working heuristics, not guarantees. Preserve the user's constraints, label missing data, and distinguish public recommendations from this package's operational adaptations. references/method.md explains those boundaries; references/sources.md identifies the fetched evidence.
Procedure
- Establish scope and inputs. Read references/method.md. Gather niche, audience, recent comparable uploads, view counts, production capacity, access, budget, and the decision deadline. Separate observed information from estimates. Use the template's intake fields to record unresolved inputs without inventing evidence.
- Choose a sustainable model and starting territory. Use references/method.md to select a low frequency, high frequency, or weekly approach. Identify one or two sub-niches to win first. Explain how the model fits the team and leaves time for ideation, packaging, and intros. [S1][S3][S5]
- Name the visible advantage. Follow references/method.md to identify distinctive knowledge, skill, personality, or access. Attach a concrete proof point and a filming implication to every claimed advantage. Generic enthusiasm is insufficient evidence of differentiation. [S1]
- Map three viewer groups. In templates/output-template.md, describe core, casual, and new viewers and why each would click and stay. Use references/method.md to broaden understandable stakes while preserving the channel's subject and expertise. [S1][S6]
- Build and tag the idea pool. For a strategy pass, brainstorm at least 100 ideas, using internal outliers, external outliers, and innovation. Record source links, baselines, and uncertainty using references/method.md. For a single upload, inspect relevant existing ideas and comparables instead of padding a new pool. [S1][S2]
- Shortlist through explicit gates. Apply demand or novelty, viewer fit, creator advantage, and package clarity from references/method.md. Write a one sentence premise and revise failed gates before filming. Consult examples/worked-examples.md for illustrations of reframing without unsupported claims. [S4][S6]
- Explore title angles. Draft at least ten materially different titles for the lead idea. Use references/method.md to vary stakes, contrast, novelty, and unanswered questions. Pair each promising angle with a visual concept rather than selecting a title in isolation. [S2]
- Develop visual alternatives. Generate at least five thumbnail concepts and prepare three distinct variants. Follow references/method.md for focal elements and the glance test. If image creation is unavailable, supply production-ready briefs and explicitly mark rendering as unfinished. [S1][S3][S6]
- Choose the combined promise. Review scroll stopping, curiosity, and believable value together. Use checklists/review-checklist.md to reject ambiguity, clutter, or an unsupported implied outcome. Record the chosen pair, alternatives, required shots, and selection rationale in templates/output-template.md. [S4][S6]
- Confirm delivery and execution. Plan visual or verbal promise confirmation in approximately the first five seconds, followed by the actual investigation or payoff. Apply references/method.md to catch missing footage, access, and quality problems. Set a decision deadline that allows publication and learning. [S4][S6]
- Review and repeat. Complete checklists/review-checklist.md, then schedule comparison with the channel baseline, retention curves, and audience reached. Use references/method.md to define a prompt follow-up when a format works, while continuing experiments. Return to the idea pool with the resulting evidence. [S1][S2][S5]
Files in this skill
- SKILL.md: Entry point, scope, and the agent's main loop.
- references/method.md: Detailed principles, decisions, numerical heuristics, warnings, and edge cases.
- references/sources.md: Six fetched public sources and their contributions, indexed by citation ID.
- examples/worked-examples.md: Two invented before and after packaging illustrations with rule annotations.
- templates/output-template.md: Strategy page and packaging appendix with field guidance.
- checklists/review-checklist.md: Pass/fail review, completion criteria, and failure repairs.
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.

