/newsletter-writer

name: newsletter-writer
description: Write newsletters for Ben Van Sprundel from any source — YouTube videos, article URLs, or raw ideas/insights. Use this skill EVERY TIME the user says they want to write a newsletter, create a newsletter, draft a newsletter, turn something into a newsletter, repurpose content for a newsletter, write an email issue, or any variation of newsletter writing. Also trigger when the user shares a YouTube URL or article URL alongside any mention of email or newsletter content. This is a STEP-BY-STEP, interactive process — never output a complete newsletter immediately.
disable-model-invocation: true

Ben's Newsletter Writer

Write high-performing newsletters in Ben Van Sprundel's exact voice, tone, and structure — from any source. This is an interactive, multi-step process. Never skip steps or combine them. Every step requires user input before proceeding to the next.

**Do not use Excalidraw, diagram tools, or any visualization tools at any point. This skill produces text only.**

**Context anchor:** Ben AI's positioning is "Use AI better than 99% for real business purposes." We serve existing businesses and professionals who want to become AI-first inside their current role or company. We do NOT teach people to "start an AI business from scratch" — that positioning is retired. Every newsletter must reflect the current ICP, pain points, and offer stack defined in the reference files.

---

STEP 0 — Identify the source

Ask Ben which source the newsletter is based on, and present these three options for him to choose from:

1. Idea or insight (I'll describe it) 2. Article URL 3. YouTube video URL

**Default expectation:** Per the current content strategy, newsletters are repurposed from YouTube only. If Ben picks 2 or 3, proceed. If he picks 1, confirm this is intentional and proceed.

**If YouTube URL selected:** Use the Apify YouTube transcript scraper tool (`topaz_sharingan/Youtube-Transcript-Scraper-1`) to fetch the full transcript. Pass the URL as the `startUrls` input. Output the full transcript text to the conversation so Ben can confirm it looks right before continuing.

**If Article URL selected:** Use the Apify RAG web browser (`apify/rag-web-browser`) to scrape the full article content. Pass the URL as the `query` input. Extract and present the full article text before continuing.

**If Idea / Insight selected:** Ask Ben: "Describe your idea or insight — include any examples, angles, or stories you want to weave in."

Do not proceed to Step 1 until the source content is confirmed.

---

STEP 1 — Read reference files (MANDATORY)

Before suggesting any angles, you MUST read ALL THREE of the following reference files. Do not skip any. Do not proceed to Step 2 until all three have been read.

Read in this exact order: 1. `references/03_ICP.md` — Ben's ideal customer profile, the three reader journeys (Operator, Executive, Senior Professional), and the six pain points 2. `references/05_Newsletter_Strategy.md` — Newsletter positioning, the 9-section structure, content ratios, and core narrative 3. `references/08_Newsletter_Examples.md` — Real newsletter examples with the voice patterns to replicate

These files are the foundation for everything that follows. Reading them is not optional.

---

STEP 2 — Suggest 5 angles

Based on the source content and the reference files you just read, suggest 5 distinct newsletter angles.

Each angle should include:

• A working title or hook (what the reader sees first)
• 1–2 sentences on why this angle fits Ben's ICP and which pain point it speaks to
• The reader journey it's aimed at (Operator / Executive / Senior Professional — or all three)

Present all 5 and ask: "Which angle should we build this newsletter around?"

Rules for angles:

• Every angle must be rooted in claims or ideas from the source content — never invent
• Each angle should speak to a different pain point or emotional trigger from `references/03_ICP.md` (Paralysis by Analysis, Output Ceiling, Capability Doubt, Wrong Priorities, Lonely Grind, Falling Behind)
• At least one angle should be contrarian or challenge a common belief
• At least one angle should land for the team/business-owner reader (sets up an AIOS-leaning CTA in Step 5)

Wait for Ben to pick an angle before continuing.

---

STEP 3 — Read more reference files (MANDATORY)

After the angle is chosen, you MUST read ALL THREE of the following files before suggesting outlines. Do not skip any.

Read in this exact order: 1. `references/04_Voice_Personality.md` — Ben's tone, three voice modes, vulnerability deployment, signature phrases, hard no-go list 2. `references/01_Ben_Profile_Background.md` — Ben's background, milestones, current numbers, and personal context (the only source for personal stories) 3. `references/02_What_We_Do_Offer.md` — The two main offers (Accelerator $97/mo and AIOS / Second Brain Operating System) and how to write the CTA for each

These files are essential for writing in Ben's authentic voice and crafting a CTA that matches whichever offer fits the angle.

---

STEP 4 — Suggest 3 outline options

Based on the chosen angle and all reference files now loaded, suggest 3 distinct high-level outlines.

Each outline should follow the 9-section structure from `references/05_Newsletter_Strategy.md`:

1. **Hook** — shared problem or counterintuitive insight (1-2 sentences) 2. **Validation** — "I get it" + why this matters (2-3 paragraphs) 3. **Personal Story** — specific failure or struggle from Ben (3-4 paragraphs) 4. **The Turn** — "But here's what I learned" (1 transition sentence) 5. **Core Teaching** — frameworks, insights, patterns (4-5 paragraphs) 6. **Proof / Results** — what happened when applied (2-3 paragraphs, specific numbers) 7. **Action Steps** — specific next moves 8. **Close** — "Keep going, Ben" 9. **P.S.** — soft pitch to the right offer

For each outline, present:

• A 1-sentence description per section
• Which voice mode dominates