newsletter-to-social

Original🇺🇸 English
Translated

Extract standalone snippets from newsletters or blog posts and route to social platforms. Posts suggestions to

13installs
Added on

NPX Install

npx skill4agent add cdeistopened/opened-vault newsletter-to-social

Newsletter/Blog to Social Router

Transform a newsletter or blog post into multiple social suggestions using framework fitting.

Invocation

User says:
  • "social from newsletter" or "social from today's newsletter"
  • "social from [blog post title]"
  • "generate social for [URL]"
  • "/newsletter-to-social"

When to Use

  • After publishing a daily or weekly newsletter
  • After publishing a blog post to Webflow
  • When repurposing any hub content for social
  • For batch social content generation

Output

Posts suggestions to #content-inbox (C0ABV2VQQKS) for triage, not direct scheduling.

The Process

NEWSLETTER
    ├─→ THOUGHT segment → Extract hot take
    │       ├─→ LinkedIn (Contrarian template)
    │       ├─→ X (Paradox Hook)
    │       └─→ Instagram (Quote card)
    ├─→ TREND segment → Extract stat + interpretation
    │       ├─→ LinkedIn (Authority template)
    │       └─→ X (Commentary)
    └─→ TOOL segment → Extract recommendation
            ├─→ LinkedIn (List/How-to)
            └─→ X (Thread: tool + benefits)

Phase 1: Snippet Extraction

Read the newsletter and extract standalone snippets from each segment.
From THOUGHT segment (contrarian take):
  • Core opinion (1-2 sentences)
  • Why it matters
  • Snippet type:
    hot_take
From TREND segment (data/research):
  • Key stat or finding
  • OpenEd interpretation
  • Snippet type:
    stat
From TOOL segment (practical advice):
  • Recommendation
  • Why it helps
  • Snippet type:
    how_to
Output format:
markdown
## Extracted Snippets

### Snippet 1 (from THOUGHT)
**Type:** hot_take
**Content:** [1-2 sentence opinion]
**Context:** [why this matters]

### Snippet 2 (from TREND)
**Type:** stat
**Content:** [stat + interpretation]
**Source:** [if external]

### Snippet 3 (from TOOL)
**Type:** how_to
**Content:** [recommendation]
**Benefit:** [what it enables]

Phase 2: Parallel Sub-Agents

For each snippet, spawn parallel platform sub-agents.
Load for all sub-agents:
  1. TEMPLATE_INDEX.md (lightweight index)
  2. opened-identity (brand voice)
  3. ai-tells (hard blocks)
Sub-agent prompt pattern:
You are a [PLATFORM] content specialist for OpenEd.

SNIPPET: [extracted snippet]
TYPE: [hot_take|stat|how_to]

Match to 2-3 best templates from TEMPLATE_INDEX.md.
Generate draft options.
Apply voice constraints.
Return for selection.
Platform-specific routing:
Snippet TypeLinkedInXInstagramFacebook
hot_takeContrarian, StoryParadox Hook, BinaryQuote cardAgree/Disagree
statAuthority, CommentaryCommentary, ThreadCarouselQuestion post
how_toList, TipsThreadCarouselFill-blank

Phase 3: Quality Gate

Apply Lite Quality Loop (3-judge):
  1. AI-Tell Judge (BLOCKING)
  2. Voice Judge (BLOCKING)
  3. Platform Judge (ADVISORY)

Phase 4: Nearbound Check

Before finalizing, check if any people are mentioned:
  1. Search
    Studio/Nearbound Pipeline/people/
    for name
  2. If found, add platform-appropriate @handle to post:
    • LinkedIn: Full name or @handle if connected
    • X: @handle
    • Instagram: @handle in caption
  3. If not found, note for future profile creation

Phase 5: Post to Content Inbox

Post each suggestion to #content-inbox (C0ABV2VQQKS) using the standard format.
Message format for each suggestion:
*[Hook/Title from post]*
_Newsletter | [Newsletter Title] | [Platform]_

[The draft post content]

OpenEd angle: [Why this works for this platform]
@handles: [Tagged people if any]

Source: [Newsletter URL or title]
Example:
*Your kid's Minecraft addiction might be genius*
_Newsletter | OpenEd Daily 2026-01-28 | LinkedIn_

Every parent worries about screen time.

But here's what the research actually shows: kids who play Minecraft develop stronger spatial reasoning than kids who don't.

The key isn't less screens. It's intentional screens.

OpenEd angle: Contrarian take that validates flexible approaches
@handles: none

Source: OpenEd Daily - Jan 28
Expected output per newsletter:
  • 2-3 LinkedIn suggestions
  • 2-3 X suggestions
  • 1-2 Instagram suggestions (with visual direction)
  • 1-2 Facebook suggestions
Total: 6-9 suggestions posted to #content-inbox for triage
Users react with ✍️ to develop further or ✅ to approve as-is.

Quick Reference

Snippet Type → Template Mapping

TypeBest Templates
hot_takeContrarian, Paradox Hook, Binary Framing, Call BS
statAuthority, Commentary, Data Story
how_toList, Thread, Tips, Do's/Don'ts
quoteQuote + Hot Take, Commentary
storyTransformation, Day-in-Life

Voice Constraints (Always Apply)

  • NO correlatives
  • NO AI-isms
  • Hyphens with spaces
  • Brand account voice

Related Skills

  • text-content
    - Full template library
  • quality-loop
    - Quality gates
  • opened-daily-newsletter-writer
    - Newsletter source
  • x-posting
    - X/Twitter scheduling