SOCIAL

Newsletter issue into social posts

Use when your newsletter has good material and you want social posts that do not just say "new issue out".

newsletter-to-social.md

Download .md

You are extracting social posts from a newsletter issue.

Issue text:
"""
{{NEWSLETTER_TEXT}}
"""
Platform: {{PLATFORM}}
Audience: {{AUDIENCE}}
Subscribe link: {{SUBSCRIBE_LINK}}

Step 1. List every distinct idea in the issue that could stand alone as a post. For each: the idea in one sentence, and whether it is a claim, a method, an observation, or a link recommendation.

Step 2. Pick the {{POST_COUNT}} strongest. Rank by this rule: an idea is stronger if a reader could act on it this week, and stronger still if a knowledgeable reader might disagree with it.

Step 3. Write each post in full, {{WORD_COUNT}} words, in the voice of the newsletter itself.

Rules:
- No post may be an advertisement for the newsletter. At most one of them mentions subscribing, in a final line, and only after delivering the idea.
- No "in this week's issue" openers.
- Each post must be readable by someone who has never heard of the newsletter.
- Keep the newsletter's own examples and figures. Do not add new ones. If a post needs context the issue does not give, write [NEEDS INPUT].
- No em dashes, no "it's not just X, it's Y", no closing paragraph that restates the opening.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{NEWSLETTER_TEXT}}
{{PLATFORM}}
{{AUDIENCE}}
{{SUBSCRIBE_LINK}}
{{POST_COUNT}}
{{WORD_COUNT}}

Getting a better result

Step 1 doubles as an audit - if an issue yields only two standalone ideas, that tells you something about the issue.
Space the posts a week apart rather than dumping them on send day.
Keep the ranked list; the ideas you did not use become next month's posts without new writing.

Questions about this prompt

When do I need this rather than a post announcing the issue?

When the issue is good and the post you would otherwise write is New issue out. An announcement asks people to click before they have been given anything. This extracts the ideas themselves, so each post works for someone who has never heard of the newsletter and might subscribe afterwards.

What do I need in front of me?

The issue text, the platform, the audience, the subscribe link, how many posts you want and a word count. The issue has to hold more than one idea for step one to be worth running. If it is a curated links roundup, step one will show you exactly how thin the standalone material is.

What comes back, and what should I keep?

Every standalone idea in the issue classified as claim, method, observation or link recommendation, a ranked shortlist, then the posts written in full in the newsletter's own voice. Keep the ranked list. The ideas you did not use are next month's posts and they cost nothing further to produce.

What is the mistake?

Publishing them all on send day, where they compete with each other and with the email. The tips suggest a week apart. The other failure is letting a post drift into promotion: at most one may mention subscribing, in a final line, and only after the idea has been delivered in full.