harperreed/dotfiles / .claude/skills-archive/snowball-content
snowball-content
VerifiedUse when turning a single topic into a full content plan with multiple angles, formats, and a publishing calendar. Triggers on "content plan", "content calendar", "snowball method", "turn one topic into many posts", "content multiplication", "30 days of content", "content from one idea".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.4 KB |
| simmer/iteration-0-candidate.md | markdown | 5.1 KB |
| simmer/iteration-1-candidate.md | markdown | 5.7 KB |
| simmer/iteration-2-candidate.md | markdown | 5.3 KB |
| simmer/iteration-3-candidate.md | markdown | 5.4 KB |
| simmer/trajectory.md | markdown | 1.1 KB |
simmer/iteration-1-candidate.md
View on GitHub---
name: snowball-content
description: Use when turning a single topic into a full content plan with multiple angles, formats, and a publishing calendar. Triggers on "content plan", "content calendar", "snowball method", "turn one topic into many posts", "content multiplication", "30 days of content", "content from one idea".
---
# The Snowball Method
Turn 1 topic into 40+ content pieces across platforms using a 4-prompt sequential pipeline.
## When to Use
- User wants to generate a content plan from a single topic
- User needs a month of content ideas
- User wants to multiply one idea into many angles and formats
## The Pipeline
This is a **sequential 4-prompt process**. Each prompt builds on the previous output. Do NOT skip steps or combine them.
```dot
digraph snowball {
rankdir=TB;
core [label="Prompt 1: THE CORE\nAsk clarifying questions FIRST\nthen define the core problem"];
angles [label="Prompt 2: ANGLES & HEADLINES\n7 unexpected angles from core\neach with hooks, facts, controversy"];
branches [label="Prompt 3: BRANCHES\n3 subtopics per angle\n3 formats per subtopic"];
calendar [label="Prompt 4: 30-DAY CALENDAR\nPlatform-adapted posts\nwith metrics and distribution"];
core -> angles;
angles -> branches;
branches -> calendar;
}
```
## Prompt 1: THE CORE
**You MUST ask clarifying questions before producing output.** Do not skip this.
Ask about:
- Goal (what outcome does this content serve?)
- Target audience (who specifically?)
- Pain points (what keeps them up at night?)
- Constraints (budget, team size, tools available?)
- Tone (professional, casual, provocative, educational?)
- Platforms (Threads, Reels, TikTok, LinkedIn, email, YouTube?)
After receiving answers, deliver:
| Deliverable | Spec |
|-------------|------|
| Core problem | One specific problem people discuss and share |
| Why it matters | 2-3 sharp sentences |
| 30-day content goals | Measurable outcomes (saves, leads, shares — not vanity metrics) |
| ICP table | See format below |
**ICP Table Format:**
| Who | What they want | What blocks them | Their language | Triggers | Taboos |
|-----|---------------|-----------------|----------------|----------|--------|
Be specific. Generic personas ("busy professionals") fail. Use language the audience actually uses.
## Prompt 2: ANGLES & HEADLINES
Generate **7 unexpected angles** from the core problem. Each angle must be:
- Counterintuitive, OR
- "You're doing it wrong", OR
- Myth vs reality, OR
- Hidden cost of the usual solution
**For each angle, provide ALL of these:**
| Element | Constraint |
|---------|-----------|
| 2 hooks | Each ≤12 words, platform-ready (Threads/Reels) |
| 1 core insight | ≤80 words |
| 1 number/fact | With brief source mention for credibility |
| 1 controversial statement | Designed to spark comments |
**The 7 angles must not overlap.** If two angles feel similar, cut one and find something sharper.
## Prompt 3: BRANCHES
For each of the 7 angles, create **3 subtopics**. Each subtopic must pass the **Cliche Inversion Gate** before proceeding:
**Cliche Inversion Gate (mandatory for every subtopic):**
1. Write a one-sentence "obvious version" — the cliche take a mediocre writer would produce on this subtopic.
2. Confirm the generated subtopic contradicts or meaningfully inverts that obvious version.
3. If you cannot articulate the obvious version, the subtopic is too vague — revise it until you can.
4. If the subtopic does not clearly invert the obvious version, replace it.
Show your gate check inline before presenting each subtopic's formats.
For each subtopic that passes the gate, create **3 formats:**
### Format 1: Educational
- Hook (≤2 lines)
- Insight (≤80 words)
- 3 concrete "do this today" steps
### Format 2: Provocative
- Debatable hook
- 3 supporting proofs
- Question at the end (drives comments)
### Format 3: Case Study
- Context (situation before)
- Action (what changed)
- Numbers (measurable result)
- Takeaway (one sentence)
If data is missing for case studies, ask the user — do not fabricate numbers.
## Prompt 4: 30-DAY CALENDAR
For each piece of content from Prompt 3, adapt for the user's specified platforms:
- Adjust length per platform norms
- Specify visual format (carousel, reel, text post, thread, etc.)
- Include a CTA appropriate to the platform
- Define a success metric for each post
Build the calendar as a table:
| Date | Platform | Topic | Angle | Format | Goal/Metric | Distribution Notes |
|------|----------|-------|-------|--------|-------------|-------------------|
**Calendar rules:**
- Remove repetition — no two posts should feel like the same take
- Alternate topics to avoid audience fatigue
- Note repurposing opportunities (clips, carousels from long-form, etc.)
- Front-load problem-awareness content, back-load solution content
## Common Mistakes
| Mistake | Fix |
|---------|-----|
| Skipping clarifying questions | The core problem definition depends on knowing the audience. Always ask first. |
| Generic angles | "5 tips for X" is not an angle. Push for counterintuitive, myth-busting, or hidden-cost framing. |
| Hooks over 12 words | Edit ruthlessly. If it doesn't fit in 12 words, the hook isn't sharp enough. |
| Missing credibility facts | Every angle needs a number or fact with a source. Vague claims don't build trust. |
| Fabricating case study data | Ask the user for real numbers. "I made $10K" without basis destroys credibility. |
| Same content, different platform | Adapting means changing format, length, and CTA — not just cross-posting. |
| No success metrics | Each post needs a defined metric. "Engagement" is not a metric. "Save rate >5%" is. |
| Self-certifying subtopics | Do not decide a subtopic is non-obvious without completing the Cliche Inversion Gate. |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |