• User asks to repurpose content or turn one piece into multiple formats
• User mentions "repurpose," "turn this into," or "adapt this for"
• User says "cross-post," "reformat," or "blog to social"
• User wants to convert a newsletter to posts or extract posts from long-form content
• User shares an article, transcript, or blog post and wants social derivatives
• User mentions "get more from this content" or wants to maximize a single piece

.agents/social-media-context-sms.md

"I don't see a social media context file yet. Run the

social-media-context-sms

skill first to capture your voice and platform preferences — it makes every derivative sound like you, not a bot."

• Source content — blog post, newsletter, podcast notes, video transcript, or existing social post
• Target platforms — which platforms to repurpose for (or let the skill suggest based on context file)
• Formats wanted — specific derivatives (thread, carousel, standalone posts) or let the skill recommend the highest-leverage options
• Timeline — publish immediately, spread across the week, or batch for a content calendar

• The core claim or lesson in one sentence
• A supporting example, data point, or story beat
• Who this insight is most valuable for

Source: Blog post "Why async interviews are better"
Insights extracted: 5

1. "Companies that switched to async saw 40% faster hiring" — stat insight
2. "The best candidate I ever hired did a Loom at midnight" — story insight
3. "Async removes geographic and timezone bias" — framework insight
4. "3-step process for running your first async interview" — how-to insight
5. "Most objections to async are actually objections to change" — contrarian insight

• Twitter / X — punchy, under 280 characters per post, direct opening line, no filler, threads use numbered posts
• LinkedIn — more context, conversational but professional, 3-5 short paragraphs, hook in the first line before the "see more" break
• Threads — casual, like a text to a smart friend, raw and real beats polished and corporate, shorter is often better
• Instagram captions — hook in the first line, depth in the body, CTA at the end, hashtags are optional and go last

1. Twitter/X thread — high reach if the hook lands; algorithmic amplification on replies
2. LinkedIn post — durable reach; LinkedIn content lives longer than X posts
3. Carousel — saves drive discovery; one strong carousel can resurface for weeks
4. Threads post — low effort, casual reach, good for testing angles
5. Standalone quote posts — easy to batch; one piece of source content yields 3-5 posts

"Want me to spread these across the week? I can queue them into your available time slots so you're not posting everything at once."

• Use

  list_time_slots

  to find open slots
• Spread derivatives across 5-7 days to avoid overlap
• Schedule the highest-leverage derivative first (anchor post)
• Space remaining posts at least 24 hours apart
• Use

  create_post

  to queue each derivative to its target platform

• Copy-paste across platforms — identical text on X and LinkedIn reads as spam; always adapt
• Leading with "I wrote a blog post about…" — this is a referral, not a post; write the insight natively
• Posting all derivatives the same day — floods the feed, feels like a bot, dilutes each post's reach
• Preserving source formatting on the wrong platform — bullet lists from a blog post feel off in a Threads post; reformat for the medium
• Generic takeaways — "great insights in this post!" is not a derivative; pull the actual insight
• Ignoring platform character limits — LinkedIn posts can breathe; X posts cannot; respect the constraints

LinkedIn:
"We switched to async interviews 6 months ago. Hiring time dropped 40%.
The best part? Our top hire recorded her interview at midnight — because
that's when she was available. Async doesn't lower the bar. It removes it."

Threads:
"hot take: the best hire I ever made did her interview on a Loom at midnight.
async interviews > scheduling nightmares. every time."

• Platform name and format type
• Full draft of the post
• Any platform-specific notes (e.g., "post as a thread reply chain on X")

• Does not write original content from scratch — see post-writer-sms for original posts
• Does not analyze post performance or metrics — see performance-analyzer-sms for analytics
• Does not define content strategy or pillars — see content-strategy-sms for strategic planning
• Does not produce visual design or images — output is text-based derivatives only
• Does not execute code or access external APIs unless BlackTwist MCP is connected
• Does not plan a full content calendar — see content-calendar-sms for scheduling across weeks

• social-media-context-sms — establish voice, pillars, and platform mix before repurposing
• platform-strategy-sms — decide which platforms to prioritize and why
• post-writer-sms — write a single original post from scratch
• thread-writer-sms — write a full multi-part thread
• carousel-writer-sms — write and structure a carousel post