Social posts from one real thing that happened

---
name: social-posts-from-one-real-thing
description: "Turns a single concrete event — a customer call, a shipped fix, a number that surprised you — into posts worth reading, instead of generating content about nothing. Use when the user asks for help with marketing tasks like social-media, content, marketing."
license: CC-BY-4.0
metadata:
  source: https://promptsbuddy.com/prompts/social-posts-from-one-real-thing
  author: "Rony"
  version: "1.0"
---

# Social posts from one real thing that happened

Turns a single concrete event — a customer call, a shipped fix, a number that surprised you — into posts worth reading, instead of generating content about nothing.

## Inputs to collect first

Ask the user for anything below that they have not already given you. Do not
invent values for these.

- `WHAT_HAPPENED` — One specific real thing. A conversation, a result, a mistake, a number. (e.g. A customer told us they'd been doing month-end reconciliation by hand for four years because nobody had asked.)
- `CHANNEL` — Where it's going — the format constraints differ a lot. (e.g. LinkedIn, where our audience is finance and ops managers.)
- `POV` — Whose voice, and what they're known for. (e.g. Our founder, who writes plainly and dislikes hustle language.)

## Tools this works with

Do not require any of these. If one is unavailable, use the stated fallback and
say which input is missing rather than inventing it.

- **Fathom** — Customer calls, where the one real thing usually happens.
  - Without it: Ask the user to paste call notes, or fall back to written customer feedback.
  - https://fathom.video/
- **Canva** — Turning the chosen post into an image or carousel once the words are right. If its MCP server is connected, fetch this yourself.
  - Without it: Deliver the structured outline and text; the user lays it out wherever they like.
  - https://www.canva.com/

## Instructions

Here is one real thing that happened. Turn it into social posts.

WHAT HAPPENED:
{{WHAT_HAPPENED}}

CHANNEL: {{CHANNEL}}
WHOSE VOICE: {{POV}}

First, tell me: **is there actually something here?** If this is only
interesting to us and not to a reader, say so and stop. Do not manufacture
significance.

If there is, write **three posts, three different angles**:
- The observation — what this reveals that most people get wrong.
- The specific — the story told plainly, with the detail that makes it real.
- The useful — what a reader can do differently tomorrow because of it.

For each: the opening line separately, since that is the only part most people
read. Keep the concrete detail; it is the whole reason the post works.

Then flag:
- **Which of the three is weakest**, and why.
- **Anything I should check before posting** — a claim about a customer, a
  number I'd need permission to share, a person identifiable from the detail.

Rules:
- Do not open with a rhetorical question, "Let that sink in", or a one-word
  line followed by a full stop.
- No engagement bait, no "agree?", no thread-teasing.
- Do not use an em dash more than once per post.
- Do not generalise the specific detail away. "A customer" is worse than "a
  finance manager at a 40-person logistics firm".
- If the story involves a real customer, assume I need their permission and say so.

## Notes from people who use this

- The gate at the top is the point — most social content is generated from nothing, and it shows.
- One real event beats ten content ideas. Keep a note of things that surprise you; that note is your content calendar.
- The permission check has saved people from posting a customer story they hadn't cleared.

---

Social posts from one real thing that happened · by Rony · v1.0
From PromptsBuddy — https://promptsbuddy.com/prompts/social-posts-from-one-real-thing
Licensed CC BY 4.0.

Every prompt is also available at /prompts/social-posts-from-one-real-thing/skill.md — see all install options.