Social Content
Turns one topic into a week of ready-to-post social content (7 posts with hook, body, CTA, hashtags) in varied formats. Use when the user says "write social posts about X", "content for the week", "turn this into posts", "LinkedIn/X/Instagram posts for my topic", or wants a content calendar from a single idea. Not for paid ad copy or long-form articles.
Add it to your agent
Give your agent (Claude Code, Cursor …) this prompt — it downloads the skill and drops it in the right place:
Install the StackScout skill "Social Content". 1. Download https://website-app-sable-eight.vercel.app/skills/social-content.zip 2. Unzip it into .claude/skills/social-content/ (create the folder if needed). 3. Confirm the folder contains SKILL.md, then tell me it's ready.
Rather do it yourself? Download the zip and unzip into .claude/skills/:
Download Social ContentFree · MIT license · one folder with a SKILL.md.
The full playbookRead it ↓Collapse ↑
Social Content Week
One topic in, seven distinct posts out — same voice, no filler.
Step 1 — Collect the setup
Ask in ONE message for whatever is missing; skip what is already given:
- Platform — LinkedIn, X/Twitter, Instagram, or Threads (pick ONE primary; lengths and hashtag counts depend on it)
- Audience — who should stop scrolling (role, niche, skill level)
- Voice — 2-3 adjectives or "like this example post"; if the user has no preference, default to: direct, concrete, lightly personal, no corporate speak
Also useful, use if provided: the user's product/service (for CTAs), one strong opinion they hold about the topic, a real anecdote or number from their work.
Step 2 — Angle before writing
From the topic, list 7 distinct angles — one per format below. Each angle must be a specific claim or moment, not a subtopic. ("Most people schedule posts at the wrong time" is an angle; "posting times" is not.) Real details from the user beat invented ones; never fabricate specific client stories, revenue numbers, or metrics — if you need an example and have none, frame it as hypothetical ("imagine you...").
Step 3 — Write 7 posts, one per format
| Day | Format | Job of the post |
|---|---|---|
| 1 | List | 3-7 concrete tactics/mistakes/tools; each item one line, no sub-explanations |
| 2 | Story | One specific moment (setback, client exchange, before/after) → one lesson |
| 3 | Hot take | A defensible contrarian claim + 2-3 sentences of reasoning; invite pushback |
| 4 | Tutorial | Numbered mini how-to (3-5 steps) the reader can do today in <15 min |
| 5 | Question | One sharp either/or or fill-in question; 1-2 lines of context max |
| 6 | Behind the scenes | What the user is building/testing/struggling with right now |
| 7 | Recap | Week's core insight distilled + pointer to the best post + strongest CTA |
Every post has exactly this structure:
- Hook (line 1): must work standing alone in the feed preview. Use a specific number, a tension, or a direct address. Ban openers: "In today's world", "Let's talk about", "I'm excited to", "Did you know".
- Body: short lines, line breaks between thoughts (except X, where ≤280 chars total unless the user wants threads). One idea per post — cut anything serving a second idea.
- CTA: one action only — comment prompt, follow, save, or link to the user's thing. Vary across the week; days 5 and 7 carry the strongest CTAs.
- Hashtags: LinkedIn 3, Instagram 5-8, X 0-1, Threads 0. Niche tags over giant generic ones (#buildinpublic over #business). On LinkedIn/X place them at the end.
Step 4 — Voice and quality pass
Re-read all 7 as a set and fix:
- Consistency: same person wrote all 7 (same pronouns, same energy, same stance)
- Banned: "game-changer", "unlock", "elevate", "revolutionize", "10x your", "the secret nobody tells you", "🤯", "🔥🔥", clickbait withholding ("...and what happened next"), fake urgency
- Standalone test: each post makes full sense to someone who saw none of the others — no "as I said yesterday"
- Specificity test: every post contains at least one concrete detail (number, named tool, exact phrase, real situation). If a post is all abstractions, rewrite it.
- Hook test: read only the 7 first lines in a row — each must create a reason to tap "more". Rewrite any that could open a post on any topic.
Step 5 — Deliver
Output as ## Day 1 — List, ## Day 2 — Story, etc. Under each: the post text
exactly as it should be pasted (hook, body, CTA, hashtags — no labels inside the
post itself). After Day 7, add a 3-line Posting notes block: suggested order
rationale, best 1-2 posts to pin or boost, and one A/B idea (an alternative hook
for the strongest post).
◎ or: the whole library at once
Skip the downloads — one MCP connector, every skill right inside your agent, always current.
See the MCP