# Story Lesson

> Write a personal story → lesson → actionable takeaway newsletter. Opens with a specific moment, builds tension, reveals the insight, ends with what the reader should do. 800-1200 words. Use when user wants to write a story-driven newsletter, share a personal experience with a lesson, or turn a moment into educational content.

- Skill: `majiayu000/story-lesson` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/story-lesson`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/story-lesson/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/story-lesson

---


## Load Context First

Before executing this skill, read the following files from the project folder if they exist:

1. **USER.md** — who the user is, how they think, how they work
2. **BUSINESS.md** — their business, products, positioning, brand voice, content strategy
3. **ICP.md** — their ideal customer, their language, their fears, what makes them buy
4. **Voice or brand voice skill** — look for any installed skill related to voice, tone, or brand voice and apply it automatically
5. Any additional context provided by the user in this session

Use all context silently. Do not reference or summarize files unless asked.

---

# Story-Lesson Newsletter

**Purpose:** Write a newsletter (800-1,200 words) that opens with a personal story, extracts a lesson, and closes with actionable takeaways. This is the most human newsletter format — it builds deep connection through vulnerability and shared experience, then delivers practical value.

## When to Activate

Use this skill when:
- User wants to write a story-driven newsletter
- User has a personal experience they want to share with a lesson
- User mentions "story", "something happened", "I realized", or "lesson I learned"
- User wants to build connection through personal narrative

## Why Story-Lesson Works

Stories are the oldest teaching technology. They work because:
- **Emotional connection** — readers feel something before they learn something
- **Memorability** — people forget tips but remember stories
- **Trust building** — vulnerability creates relatability
- **Natural authority** — the lesson emerges from experience, not proclamation

The secret: the story is not about you. It's about the reader seeing themselves in your experience.

## Required Input

Ask the user for (if not provided):
- **The moment** — What happened? Be specific (where, when, what triggered it)
- **The emotion** — How did it feel?
- **The realization** — What did you learn from it?
- **The application** — How does this apply to the reader?

**Critical rule:** Never fabricate stories. If the user doesn't provide a real experience, ask for one. The format requires authenticity.

## Structure

### Section 1: The Moment (150-250 words)

Open with a specific scene. Drop the reader into a moment in time.

**Techniques:**
- **Start in the middle** — No backstory. Open with action, dialogue, or a sensory detail.
- **Be specific** — Time of day, location, what you were doing. Specificity creates believability.
- **Create tension** — Something was wrong, uncertain, or about to change.

**Example openers:**
- "It was 2 AM and I was staring at a blank document, deadline in 6 hours."
- "The client said four words that changed how I think about everything: 'This isn't what I asked for.'"
- "I deleted 3,000 words. All of them. Then I started over."

**Rules:**
- No throat-clearing ("Let me tell you a story about...")
- Start IN the moment, not before it
- Use sensory details — what you saw, heard, felt
- Keep it tight — this is a newsletter, not a memoir

### Section 2: The Build (200-350 words)

Develop the story. Build tension toward the turning point.

**Include:**
- What you tried (and why it wasn't working)
- The stakes (what was on the line)
- The mounting pressure or confusion
- The moment just before the realization

**Pacing techniques:**
- Short sentences for tension ("It wasn't working. Nothing was.")
- Longer sentences for context and reflection
- Dialogue if it happened ("My mentor said something I didn't want to hear...")
- Internal monologue ("I kept thinking: what am I missing?")

**Rules:**
- Keep building toward the insight — no tangents
- Show, don't tell emotions ("my stomach dropped" vs. "I was scared")
- Every sentence should move the story forward
- Don't give away the lesson yet

### Section 3: The Insight (150-250 words)

The turning point. The moment of realization.

**Structure:**
1. The trigger — what specifically caused the shift
2. The realization — stated clearly in 1-2 sentences
3. The reframe — how this changed your perspective

**Format the core insight as a standalone statement:**
> The realization hit me: [clear, memorable statement of the lesson].

**Rules:**
- The insight should be surprising or counterintuitive
- It should feel earned by the story (not tacked on)
- State it clearly — don't make the reader guess
- One insight, not three. Go deep on one.

### Section 4: The Lesson Applied (150-200 words)

Bridge from your story to the reader's life. Make the lesson universal.

**Include:**
- How this applies beyond your specific situation
- Where the reader might be experiencing the same thing
- Why this lesson matters in their context

**Transition phrases:**
- "Here's why this matters for you..."
- "If you're anything like me, you've probably..."
- "The same principle applies when you..."

**Rules:**
- Shift from "I" to "you" language
- Connect to a common struggle your audience faces
- Don't preach — share

### Section 5: What to Do About It (100-150 words)

Close with 2-4 specific, actionable steps the reader can take.

**Format:**
> **What this means for you:**
> 1. [Specific action tied to the lesson]
> 2. [Specific action]
> 3. [Specific action]

**End with a memorable closing line** — something quotable that captures the lesson. A sentence they'll remember after they close the email.

## Subject Lines

**Generate 5 options:**

1. **The moment**: "The [moment/event] that changed how I [topic]"
2. **The lesson**: "What [experience] taught me about [topic]"
3. **The confession**: "I [vulnerable admission] — here's what I learned"
4. **The realization**: "The [counterintuitive insight] I almost missed"
5. **The question**: "What would you do if [scenario from story]?"

## Output Format

```
## Subject Line Options

1. [Option 1]
2. [Option 2]
3. [Option 3]
4. [Option 4]
5. [Option 5]

**Recommended**: Option [X] — [reasoning]

---

## Newsletter: [Chosen Subject Line]

**Word count**: ~[X] words

---

[The Moment — drop reader into the scene, 150-250 words]

[The Build — develop tension, 200-350 words]

[The Insight — the realization, clearly stated, 150-250 words]

[The Lesson Applied — bridge to reader's life, 150-200 words]

[What to Do About It — 2-4 actions + memorable closing line, 100-150 words]

---

**Stats**: [X] words | Core lesson: [one sentence]
```

## Quality Checklist

- [ ] Opens IN a specific moment (not with backstory)
- [ ] Story includes sensory details and specificity
- [ ] Tension builds toward a clear turning point
- [ ] The insight is clearly stated and feels earned
- [ ] Lesson bridges from personal to universal
- [ ] Closes with specific, actionable steps
- [ ] Ends with a memorable line
- [ ] 800-1,200 words total
- [ ] Story is real (not fabricated)
- [ ] Voice matches context profiles
- [ ] The story serves the lesson (not the other way around)