Load expert:experts/brunson-storytelling.md (Epiphany Bridge for narrative expansion)
Load expert:experts/ogilvy-headlines.md (subject line generation)
Load for critique:references/rubber-duck-escalator.md
Step 2: Analyze source post
Read the LinkedIn post and identify compressed elements:
Core claim — What's the main argument?
Implied evidence — What stats, studies, or examples are referenced or hinted at but not fully developed?
Hinted stories — What personal experiences or case studies are compressed into 1-2 sentences?
Mentioned frameworks — What models or structures are named but not fully explained?
Missing counterarguments — What "but what about..." questions would a sharp reader ask?
Angle — Which angle is the source post? (This informs expansion strategy.)
Step 3: Mini-research from Brain
Load relevant Brain sections to find deeper evidence:
evidence_bank — Find 2-3 additional stats that support the core claim
topic_depth_layers — Pull key debates, common mistakes, practitioner wisdom on the topic
newsletter_insights — Find cross-references from 2+ newsletter sources
synthesized_mental_models — Identify relevant mental model to weave in
Step 4: Expand using newsletter structure
Follow the full structure from references/newsletter-practices.md:
Opening story (200-400 words)
If source post hints at a story → expand using Epiphany Bridge (7-step)
If source is framework-based → create a scene that reveals why the framework matters
If source is contrarian → open with the moment you realized the common view was wrong
Bridge to insight (100-200 words)
Connect the story to the core claim naturally
Deep framework/evidence section (600-1200 words)
Fully develop the framework or argument that was compressed in the LinkedIn post
Add the 2-3 evidence anchors from mini-research
Cross-reference 2+ newsletter sources
Include the "only I could have written this" section (200+ words)
Use rejection-based teaching where appropriate
Practitioner callout (200-400 words)
"What most get wrong" — the compressed insights from the LinkedIn post become the foundation
Expand with specific examples and counterarguments
Landing (100-200 words)
Connect back to opening story
Specific, actionable takeaway
P.S.
Secondary CTA or personal note
Step 5: Generate subject line + preview text
Using Ogilvy headline principles:
Write 5 subject line variations
Select the best (curiosity + specificity)
Write preview text that extends (not repeats) the subject line
Step 6: Critique (Rubber Duck Escalator)
Run all 5 phases with newsletter-adapted scoring:
MIRROR demands 2-3 specific experiential moments (vs 1 for LinkedIn)
CHALLENGE demands 3+ evidence anchors
CRYSTALLIZE checks 1500-3000 word range and subject line quality
All phases must score 8+
Max 3 iterations
Step 7: Present to user
Show the full newsletter with scorecard and subject line options.
Output Format
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
EXPANSION ANALYSIS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Source: [LinkedIn post summary]
Core claim: [1 sentence]
Compressed elements found: [list]
Evidence added from Brain: [list]
Newsletter sources cross-referenced: [list]
Mental model applied: [name]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
NEWSLETTER
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Subject line: [Primary]
Alt subjects: [2 alternatives]
Preview text: [1-2 sentences]
Word count: [X words]
---
[Full newsletter body]
---
P.S. [text]
SCORECARD
Mirror: X | Probe: X | Challenge: X | Illuminate: X | Crystallize: X
Composite: X.X | Status: PASS/FAIL
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1---2name: expand3description: Skill: Expand Content (Micro → Pillar)4---5# Skill: Expand Content (Micro → Pillar)67## Trigger8"Expand this into a newsletter" / "Turn this into an article" / "Make this a newsletter" / User provides a LinkedIn post to expand.910## Process1112### Step 1: Load references13- **Always load:** `references/newsletter-practices.md`, `references/format-adaptation-matrix.md`14- **Load expert:** `experts/brunson-storytelling.md` (Epiphany Bridge for narrative expansion)15- **Load expert:** `experts/ogilvy-headlines.md` (subject line generation)16- **Load for critique:** `references/rubber-duck-escalator.md`1718### Step 2: Analyze source post19Read the LinkedIn post and identify compressed elements:201. **Core claim** — What's the main argument?212. **Implied evidence** — What stats, studies, or examples are referenced or hinted at but not fully developed?223. **Hinted stories** — What personal experiences or case studies are compressed into 1-2 sentences?234. **Mentioned frameworks** — What models or structures are named but not fully explained?245. **Missing counterarguments** — What "but what about..." questions would a sharp reader ask?256. **Angle** — Which angle is the source post? (This informs expansion strategy.)2627### Step 3: Mini-research from Brain28Load relevant Brain sections to find deeper evidence:29- `evidence_bank` — Find 2-3 additional stats that support the core claim30- `topic_depth_layers` — Pull key debates, common mistakes, practitioner wisdom on the topic31- `newsletter_insights` — Find cross-references from 2+ newsletter sources32- `synthesized_mental_models` — Identify relevant mental model to weave in3334### Step 4: Expand using newsletter structure35Follow the full structure from `references/newsletter-practices.md`:36371. **Opening story (200-400 words)**38 - If source post hints at a story → expand using Epiphany Bridge (7-step)39 - If source is framework-based → create a scene that reveals why the framework matters40 - If source is contrarian → open with the moment you realized the common view was wrong41422. **Bridge to insight (100-200 words)**43 - Connect the story to the core claim naturally44453. **Deep framework/evidence section (600-1200 words)**46 - Fully develop the framework or argument that was compressed in the LinkedIn post47 - Add the 2-3 evidence anchors from mini-research48 - Cross-reference 2+ newsletter sources49 - Include the "only I could have written this" section (200+ words)50 - Use rejection-based teaching where appropriate51524. **Practitioner callout (200-400 words)**53 - "What most get wrong" — the compressed insights from the LinkedIn post become the foundation54 - Expand with specific examples and counterarguments55565. **Landing (100-200 words)**57 - Connect back to opening story58 - Specific, actionable takeaway59606. **P.S.**61 - Secondary CTA or personal note6263### Step 5: Generate subject line + preview text64Using Ogilvy headline principles:651. Write 5 subject line variations662. Select the best (curiosity + specificity)673. Write preview text that extends (not repeats) the subject line6869### Step 6: Critique (Rubber Duck Escalator)70Run all 5 phases with newsletter-adapted scoring:711. MIRROR demands 2-3 specific experiential moments (vs 1 for LinkedIn)722. CHALLENGE demands 3+ evidence anchors733. CRYSTALLIZE checks 1500-3000 word range and subject line quality744. All phases must score 8+755. Max 3 iterations7677### Step 7: Present to user78Show the full newsletter with scorecard and subject line options.7980## Output Format81```82━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━83EXPANSION ANALYSIS84━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━85Source: [LinkedIn post summary]86Core claim: [1 sentence]87Compressed elements found: [list]88Evidence added from Brain: [list]89Newsletter sources cross-referenced: [list]90Mental model applied: [name]9192━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━93NEWSLETTER94━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━9596Subject line: [Primary]97Alt subjects: [2 alternatives]98Preview text: [1-2 sentences]99Word count: [X words]100101---102103[Full newsletter body]104105---106107P.S. [text]108109SCORECARD110Mirror: X | Probe: X | Challenge: X | Illuminate: X | Crystallize: X111Composite: X.X | Status: PASS/FAIL112113━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━114```
Run npx skillmds@latest add raven-sourav/expand in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Skill: Expand Content (Micro → Pillar) It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
raven-sourav (@raven-sourav) published this skill. Their other Agent Skills are listed on their SkillMD profile.