galloway-youtube-outlier-packaging
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.
- License 许可
- Apache-2.0
- 所属仓库
- getedgehq/skills
- 最近更新
- 2026-11-12
- Stars
- ★ 5
- Forks
- 0
01 前言 Front Matter
- name
- galloway-youtube-outlier-packaging
- description
- 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.
02 资源文件 7
- 参考文档checklists/review-checklist.md6.0 KB
- 参考文档DERIVATION.json2.5 KB
- 参考文档examples/worked-examples.md9.1 KB
- 许可证LICENSE10.5 KB
- 参考文档references/method.md13.5 KB
- 参考文档references/sources.md3.0 KB
- 参考文档templates/output-template.md6.7 KB
03 SKILL.md 正文
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.
04 同仓库更多 Skills
zero-downtime-cloud-move
Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.
zayats-ceo-branding
Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.
yc-app-roast
YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks "what would a YC partner think", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
yc-app-review
YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press "Send my notes" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
x-growth-playbook
X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says "analyse my X posts", "what works on my Twitter", "how do I grow on X", "what should I post next on X", "audit my X account", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.
workplan
Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: "workplan", "work plan", "create a plan", "what's the plan", "where was I", or when Claude detects a multi-step task that needs tracking.