Social
Corey HainesCommunityCreated by Corey Haines
- Skill
- Content generator
- Business and productivity
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The social skill provides a structured approach to social media management, focusing on storytelling and audience connection. It covers the entire lifecycle of social content, from initial strategy and pillar development to repurposing long-form assets and executing daily engagement routines. The skill emphasizes avoiding common AI-generated writing patterns to ensure content remains authentic and engaging across platforms like LinkedIn, Twitter/X, Instagram, and TikTok.
What it does
- Develops content pillars aligned with business goals and audience interests.
- Provides hook formulas and templates for various social platforms.
- Offers a systematic approach to repurposing long-form content into social-ready atoms.
- Defines daily engagement routines for building community and brand presence.
- Includes frameworks for creating high-performing carousels and short-form videos.
- Guides the analysis of performance metrics to optimize future content strategy.
When to use it
- When you need to create or schedule social media content for major platforms.
- When you want to repurpose existing blog posts, videos, or newsletters into social content.
- When you need to develop a consistent social media strategy or content calendar.
- When you want to improve engagement through social listening and targeted interaction.
- When you need to analyze competitor content or viral trends in your niche.
Advantages
- Ensures content is authentic by avoiding common AI-generated writing patterns.
- Maximizes content ROI through a structured repurposing system.
- Provides actionable frameworks for different content types like carousels and videos.
- Helps maintain consistency with a clear weekly planning and batching strategy.
- Focuses on platform-specific best practices to improve reach and engagement.
Usage examples
- “I have a new blog post about SaaS pricing. Can you help me turn this into a LinkedIn carousel and a Twitter thread?”
- The agent will analyze the blog post, extract key insights, and draft a slide-by-slide carousel structure for LinkedIn along with a multi-tweet thread for X.
- “I'm feeling stuck on what to post on Instagram. Can you help me brainstorm some Reel ideas based on my content pillars?”
- The agent will review your established content pillars and suggest 3-5 short-form video concepts with hooks and structural outlines.
- “I want to start engaging more on LinkedIn. Can you help me set up a daily routine to find and comment on relevant posts?”
- The agent will help you identify target accounts and keywords, then provide a 30-minute daily engagement workflow to build relationships.
- “Can you review this draft LinkedIn post and tell me if it sounds like AI?”
- The agent will audit the post against the 'No AI Tells' guidelines, identifying issues like broetry, contrast reveals, or engagement bait and suggesting improvements.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/coreyhaines31/social/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip social.zip -d .agents/skills
Documentation by Corey Haines
Social Content
You are an expert social media strategist. Your goal is to help create engaging content that builds audience, drives engagement, and supports business goals.
Whatever the platform, storytelling and connecting with your audience come first. The better the user can share their story, the better their posts will perform — platform tactics and algorithm mechanics amplify a good story; they never replace one. Keep this at the center of every recommendation below.
Before Creating Content
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
1. Goals
What's the primary objective? (Brand awareness, leads, traffic, community)
What action do you want people to take?
Are you building personal brand, company brand, or both?
2. Audience
Who are you trying to reach?
What platforms are they most active on?
What content do they engage with?
3. Brand Voice
What's your tone? (Professional, casual, witty, authoritative)
Any topics to avoid?
Any specific terminology or style guidelines?
4. Resources
How much time can you dedicate to social?
Do you have existing content to repurpose?
Can you create video content?
Platform Quick Reference
| Platform | Best For | Frequency | Key Format |
|---|---|---|---|
| B2B, thought leadership | 3-5x/week | Carousels, stories | |
| Twitter/X | Tech, real-time, community | 3-10x/day | Threads, hot takes |
| Visual brands, lifestyle | 1-2 posts + Stories daily | Reels, carousels | |
| TikTok | Brand awareness, younger audiences | 1x/day, up to 3x once posts clear a view floor | Short-form video |
| Communities, local businesses | 1-2x/day | Groups, native video |
For detailed platform strategies (LinkedIn, X, Instagram, TikTok, Facebook, Telegram): See references/platforms.md
For hashtag limits and character counts: See references/platform-limits.md
For X (Twitter) ranking mechanics — the For You feed signals from xAI's open-sourced algorithm, and the 10 posting rules they imply: See references/x-algorithm.md. Use it whenever the task involves posting on X.
Content Pillars Framework
Build your content around 3-5 pillars that align with your expertise and audience interests.
Example for a SaaS Founder
| Pillar | % of Content | Topics |
|---|---|---|
| Industry insights | 30% | Trends, data, predictions |
| Behind-the-scenes | 25% | Building the company, lessons learned |
| Educational | 25% | How-tos, frameworks, tips |
| Personal | 15% | Stories, values, hot takes |
| Promotional | 5% | Product updates, offers |
Pillar Development Questions
For each pillar, ask:
What unique perspective do you have?
What questions does your audience ask?
What content has performed well before?
What can you create consistently?
What aligns with business goals?
Hook Formulas
The first line determines whether anyone reads the rest.
Curiosity Hooks
"I was wrong about [common belief]."
"[Outcome] usually comes down to [specific, surprising cause]."
"[Impressive result] in [surprisingly short time]."
Story Hooks
"Last week, [unexpected thing] happened."
"I almost [big mistake/failure]."
"3 years ago, I [past state]. Today, [current state]."
Value Hooks
"How to [desirable outcome] (without [common pain]):"
"[Number] [things] that [outcome]:"
"Stop [common mistake]. Do this instead:"
Contrarian Hooks
"Unpopular opinion: [bold statement]"
"[Common advice] cost us [specific result]."
"I stopped [common practice] and [positive result]."
For post templates and more hooks: See references/post-templates.md
No AI Tells
Readers scroll past posts that read as generated, and on LinkedIn they say so in the comments. A hook formula is a starting shape. Fill it with a specific fact, number, or story.
Never write these:
Contrast reveals: "It's not X, it's Y." "Not because X. Because Y." State Y directly, with the reason.
Negation lists: "No X, no Y, no Z." Say what does happen. One plain absence ("No card required") is fine.
Trailing pile-ons: a full claim, then a comma and more restating clauses. End the sentence at the claim.
Self-answered questions and colon reveals: "The result? 3x faster." "The best part: it learns." FAQ questions and a question in the reader's own voice are fine.
Stock phrases: "Say goodbye to," "X, reimagined," "Unlock the power of," "Take it to the next level," "Here's the thing."
Em dashes in posts. Use a period or a line break.
Social-specific tells:
Broetry: one short sentence per line, every line, for the whole post. Write paragraphs and break lines where a person would pause.
Engagement bait: "Agree?" "Thoughts?" "Let that sink in." "Read that again." End on the point, or a real question you want answered.
Manufactured vulnerability: "I'll be honest, I was terrified..." with no real story behind it.
Emoji as bullets: 🚀 ✅ 💡 leading every line.
Keep fragments and lists of three to one per post. For the full blacklist, use the copywriting skill's AI-tells reference.
For carousels (Instagram carousels, LinkedIn document posts): See references/carousel-frameworks.md — five slide-by-slide narrative architectures (Value-Stack, Problem-Proof, Hack List, Rant Callout, Demo Walkthrough) with framework selection guidance, per-slide copy slots, platform notes, and a production checklist. Pick the framework before writing slides.
Content Repurposing System
Turn one piece of content into many. The best social content isn't created from scratch — it's extracted from longer-form pillar content and adapted to each platform.
Blog Post → Social Content
| Platform | Format |
|---|---|
| Key insight + link in comments | |
| Carousel of main points | |
| Twitter/X | Thread of key takeaways |
| Carousel with visuals | |
| Reel summarizing the post |
Podcast / Video → Social Content
Extract "content atoms" — self-contained moments from any long-form content that work on their own:
| Atom Type | What to Look For | Best Platform |
|---|---|---|
| Quotable moment | A bold claim, hot take, or memorable line (15-60 sec) | Twitter/X, LinkedIn, TikTok |
| Story arc | A complete mini-story with setup, conflict, resolution (60-90 sec) | Instagram Reels, TikTok, YouTube Shorts |
| Tactical tip | A specific how-to or framework explained clearly (30-60 sec) | LinkedIn, YouTube Shorts |
| Controversial take | A contrarian opinion that sparks debate | Twitter/X, LinkedIn |
| Data/stat callout | A surprising number or research finding | LinkedIn carousel, Twitter/X |
| Behind-the-scenes | Authentic, unpolished moments | Instagram Stories, TikTok |
Podcast repurposing workflow:
Get transcript — use Whisper, Descript, or your podcast host's transcription
Mark timestamps — flag the 5-10 best moments while listening or scanning transcript
Extract clips — pull video/audio clips for each moment (Descript, Opus Clip, or manual)
Write standalone captions — each clip needs context; don't assume the viewer heard the rest
Add subtitles — most social video is watched without sound
Schedule across 1-2 weeks — spread a single episode across multiple posts
Per episode, aim for:
3-5 short video clips or audiograms (15-60 sec) for Reels/TikTok/Shorts
1-2 LinkedIn text posts from key insights
1 Twitter/X thread of takeaways
1 carousel summarizing the main framework or list
1 newsletter section or blog post from the best segment
Webinar / Live Event → Social Content
| Extract | Format |
|---|---|
| Key slides with commentary | LinkedIn carousel |
| Q&A highlights | Twitter/X thread |
| Speaker quotes | Quote graphics for Instagram/LinkedIn |
| Audience reactions/poll results | Engagement posts |
| Full recording → short clips | Reels, TikTok, Shorts |
Newsletter → Social Content
| Extract | Format |
|---|---|
| Main insight | LinkedIn post |
| Curated links with commentary | Twitter/X thread |
| Data or stat | Quote graphic |
| Hot take or opinion | Twitter/X post, LinkedIn |
Repurposing Workflow
Create pillar content (blog, video, podcast, webinar, newsletter)
Extract content atoms (5-10 per piece — quotes, stories, tips, data)
Adapt to each platform (format, length, and tone)
Write standalone captions (each post must work without context)
Schedule across the week (spread distribution, don't dump all at once)
Update and reshare (evergreen content can repeat every 3-6 months)
Content Calendar Structure
Weekly Planning Template
| Day | Twitter/X | ||
|---|---|---|---|
| Mon | Industry insight | Thread | Carousel |
| Tue | Behind-scenes | Engagement | Story |
| Wed | Educational | Tips tweet | Reel |
| Thu | Story post | Thread | Educational |
| Fri | Hot take | Engagement | Story |
Batching Strategy (2-3 hours weekly)
Review content pillar topics
Write 5 LinkedIn posts
Write 3 Twitter threads + daily tweets
Create Instagram carousel + Reel ideas
Schedule everything
Leave room for real-time engagement
Engagement Strategy
Daily Engagement Routine (30 min)
Respond to all comments on your posts (5 min)
Comment on 5-10 posts from target accounts (15 min)
Share/repost with added insight (5 min)
Send 2-3 DMs to new connections (5 min). For LinkedIn as an outbound channel (limits, sequences, connection and message copy), see the cold-email skill's LinkedIn outreach reference
For surfacing which posts to comment on (top-10 daily lists, brand/competitor monitoring, intent-signal triage), see references/listening.md. Includes a scoring rubric and curl recipes for Reddit, Hacker News, and Bluesky.
Quality Comments
Add new insight, not just "Great post!"
Share a related experience
Ask a thoughtful follow-up question
Respectfully disagree with nuance
Building Relationships
Identify 20-50 accounts in your space
Consistently engage with their content
Share their content with credit
Eventually collaborate (podcasts, co-created content)
Analytics & Optimization
Metrics That Matter
Awareness: Impressions, Reach, Follower growth rate
Engagement: Engagement rate, Comments (higher value than likes), Shares/reposts, Saves
Conversion: Link clicks, Profile visits, DMs received, Leads attributed
Weekly Review
Top 3 performing posts (why did they work?)
Bottom 3 posts (what can you learn?)
Follower growth trend
Engagement rate trend
Best posting times (from data)
Optimization Actions
If engagement is low:
Test new hooks
Post at different times
Try different formats
Increase engagement with others
If reach is declining:
Avoid external links in post body
Increase posting frequency
Engage more in comments
Test video/visual content
Content Ideas by Situation
When You're Starting Out
Document your journey
Share what you're learning
Curate and comment on industry content
Engage heavily with established accounts
When You're Stuck
Repurpose old high-performing content
Ask your audience what they want
Comment on industry news
Share a failure or lesson learned
Scheduling Best Practices
When to Schedule vs. Post Live
Schedule: Core content posts, Threads, Carousels, Evergreen content
Post live: Real-time commentary, Responses to news/trends, Engagement with others
Queue Management
Maintain 1-2 weeks of scheduled content
Review queue weekly for relevance
Leave gaps for spontaneous posts
Adjust timing based on performance data
Publishing From Your Agent
Everything above produces drafts and a calendar — actually getting posts onto accounts still needs a scheduling tool. If the user has one with an MCP server or API, you can execute the plan directly instead of handing them copy-paste work:
Check what's connected. Ask the user what they schedule with. Many scheduling tools (Typefully, Buffer, Marky, and others) expose drafting and scheduling through an MCP server or an API, so you can create and schedule posts directly. Check the tools registry for guides.
Create posts as drafts first — the user approves before anything is scheduled. Never auto-publish without an explicit go-ahead.
Schedule per the calendar you built (spacing and platform rules from this skill still apply), then report back the queue with review links.
Close the loop. If the tool exposes post-level stats, pull them next session and feed real engagement data back into the "adjust timing based on performance" step instead of guessing.
Reverse Engineering Viral Content
Instead of guessing, analyze what's working for top creators in your niche:
Find creators — 10-20 accounts with high engagement
Collect data — 500+ posts for analysis
Analyze patterns — Hooks, formats, CTAs that work
Codify playbook — Document repeatable patterns
Layer your voice — Apply patterns with authenticity
Convert — Bridge attention to business results
For the complete framework: See references/reverse-engineering.md
Short-Form Video (TikTok, Reels, Shorts)
Short-form video is the highest-reach format on every major platform. These frameworks apply whether you're creating for TikTok, Instagram Reels, or YouTube Shorts.
Platform Specs
| Platform | Optimal Length | Aspect Ratio | Key Difference |
|---|---|---|---|
| TikTok | 15-60 sec | 9:16 | Trending sounds, raw/authentic feel |
| Reels | 15-30 sec | 9:16 | Polished content, rewards saves/shares |
| Shorts | 30-60 sec | 9:16 | YouTube SEO applies, searchable titles |
The 3-Second Rule
You have 3 seconds to stop the scroll. Every video needs three simultaneous hooks:
[VISUAL HOOK] + [VERBAL HOOK] + [TEXT OVERLAY]All three should hit in the first second.
Video Structures
Problem-Solution (15-30 sec):
[0-3s] Hook: State the problem
[3-10s] Agitate: Why it matters
[10-25s] Solution: Your method/product/tip
[25-30s] CTA: What to do nextList Format (30-60 sec):
[0-3s] Hook: "X things that [outcome]"
[3-50s] Items: One every 5-8 seconds
[50-60s] CTATutorial (30-60 sec):
[0-3s] Hook: Show the end result first
[3-8s] Overview: "Here's how..."
[8-50s] Steps: Quick, clear instructions
[50-60s] Result + CTACaption & Subtitle Best Practices
Captions increase watch time by 25-40%. Most social video is watched without sound.
MAX 2 lines on screen at once
3-5 words per line
Bold, sans-serif font with black outline
Highlight key words in a different color
Match timing to speech exactly
Tools: CapCut (free), Descript, Captions.ai, Premiere Pro
Content Ideas by Type
| Business Type | Video Ideas |
|---|---|
| SaaS | Feature demos (show outcome first), before/after, "Watch me do X in Y seconds" |
| E-commerce | Unboxing, comparisons, how it's made, customer reviews |
| Services | Process reveals, client transformations, myth-busting |
| Personal brand | Lessons learned, controversial takes, day-in-the-life |
Common Mistakes
Slow hooks — don't build up to the point
No text overlay — many watch without sound
Poor audio — bad audio kills retention instantly
Too long — if it can be shorter, make it shorter
No CTA — tell viewers what to do
Ignoring comments — engagement in first hour matters
For video hook formulas, scripting templates, warming up a new account, staged posting cadence, and finding a winning format: See references/short-form-video.md
Task-Specific Questions
What platform(s) are you focusing on?
What's your current posting frequency?
Do you have existing content to repurpose?
What content has performed well in the past?
How much time can you dedicate weekly?
Are you building personal brand, company brand, or both?
Related Skills
copywriting: For longer-form content that feeds social
launch: For coordinating social with launches
reverse-engineer-marketing: For reading a company's content patterns, house style, and formulas across every channel
emails: For nurturing social audience via email
marketing-psychology: For understanding what drives engagement
Files
- ATTRIBUTION.mdAdded by AutoGineer873 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md18.1 KiB
- evals/evals.json11.6 KiB
- references/carousel-frameworks.md10.9 KiB
- references/listening-sources-template.md3.4 KiB
- references/listening.md13.2 KiB
- references/platform-limits.md2.8 KiB
- references/platforms.md8.2 KiB
- references/post-templates.md3.9 KiB
- references/reverse-engineering.md5.4 KiB
- references/short-form-video.md10.3 KiB
- references/x-algorithm.md6.9 KiB
references/carousel-frameworks.md
Carousel Frameworks
Five slide-by-slide narrative architectures for carousels — Instagram carousels and LinkedIn document posts. Each framework is a different reason to keep swiping; picking the right one for the content matters more than polishing individual slides.
A carousel is not a blog post chopped into squares. It's a swipe-through with two jobs per slide: deliver one idea, and make the next swipe irresistible. These frameworks encode structures that show up repeatedly in high-performing carousels; treat them as starting structures to adapt, not rigid formulas — and expect to validate against your own analytics.
Picking a Framework
| Your content is... | Use | Why |
|---|---|---|
| A list of resources, tools, or tips | A: Value-Stack | Completeness is the promise; the count is the hook |
| A personal result with a system behind it | B: Problem-Proof | Proof opens and closes the loop; the system is the meat |
| Several named techniques on one theme | C: Hack List | Each hack re-earns the swipe independently |
| A strong opinion about a common practice | D: Rant Callout | Conviction is the content; structure keeps it fair |
| A product or workflow you can show | E: Demo Walkthrough | Seeing the steps is more persuasive than describing them |
Two cross-framework rules before the specifics:
Slide 1 is the thumbnail. It competes in the feed alone, before anyone knows a carousel follows. Design and write it as a standalone scroll-stopper.
One visual template per carousel. Same layout, type scale, and palette on every interior slide. Variety between slides reads as clutter; consistency lets the content change while the frame stays still.
Framework A: Value-Stack (4–14 slides)
The "everything you need" carousel. Works because the cover makes a completeness claim — an exact count and an exact deliverable — and every swipe pays it down.
| Slide | Job | Pattern |
|---|---|---|
| 1 — Cover | State the exact count + exact deliverable. Specificity proves scale upfront. | "[N] [resource type] for [role/outcome]" |
| 2 to N−1 — Value delivery | One item or category per slide, 3–6 concrete sub-items each. Same visual template, zero filler slides. | "[Category/item]: [sub-items]" |
| N — Close | Convert the swipe-through into an action. | "[Action] for [the payoff]" — comment a keyword, follow, link in bio |
Why the exact count matters: "27 free tools" outperforms "the best free tools" because a number is a checkable promise — the reader can verify you delivered. Rounding up with padding breaks the trust the count created.
SaaS example: "12 ChatGPT prompts for SaaS onboarding emails" → one prompt per slide with the use case → "Comment PROMPTS and I'll send the full doc."
Failure mode: filler slides to hit a bigger number. Cut to the real count; a tight 8 beats a padded 14.
Framework B: Problem-Proof (6–10 slides)
The "I did X, here's the system" carousel. The hook is a result stated as fact, not advice — and the final slide shows the receipt, closing the loop slide 1 opened.
| Slide | Job | Pattern |
|---|---|---|
| 1 — Hook | A specific personal claim with a number. A result, not a tip. | "[I/we did X]. [Specific result, with number]." |
| 2 — Reframe the problem | Name what's actually going wrong so the reader recognizes themselves. | "The real problem: [named issue]" |
| 3–4 — The mechanism | Show the real system: named tools, named steps. Concrete beats vague. | "The system: [named tools/steps]" |
| 5 to N−1 — The detail | The literal prompt text, template, or step-by-step. This is the save-worthy part. | "[The literal prompt or process detail]" |
| N — Proof | The actual output artifact. A screenshot, not a description. | "[Screenshot of output]: the receipt" |
The open loop is the engine: slide 1 makes a claim, the last slide proves it, and everything between explains how. Readers swipe to see whether the receipt is real.
SaaS example: "We cut churn 22% with one onboarding email." → the real problem (activation, not price) → the sequence structure → the literal email copy → the retention chart.
Failure mode: vague mechanism slides ("optimize your workflow") — if the middle slides don't name tools and steps, the proof slide reads as luck, not system.
Framework C: Hack List (6–10 slides)
The "numbered techniques" carousel. A contrarian cover creates status anxiety — most people are doing this wrong — and each numbered hack independently re-earns the swipe.
| Slide | Job | Pattern |
|---|---|---|
| 1 — Contrarian hook | A stat or claim implying most people fail at this. | "[Stat implying most people fail at X]" |
| 2 — The problem | Why the common approach fails, ideally with an analogy. | "The problem: [why it fails]" |
| 3 to N−1 — Numbered hacks | One named technique per slide. Bad-vs-good contrast makes each hack land instantly. | "Hack #[n]: [named technique]" |
| N — Synthesis + close | A one-line thesis tying the hacks together, then a save/share/follow CTA. | "[Thesis tying hacks together]" + [CTA] |
Name every technique. "The 3-second rule" is shareable and memorable; "keep it short" is neither. Named techniques travel — people repeat them and credit the source.
SaaS example: "90% of trial emails never get opened." → why (they read like receipts, not messages) → Hack #1: The founder-from line, Hack #2: The one-question subject, ... → "Trial emails are conversations, not confirmations. Save this for your next sequence."
Failure mode: hacks that are restatements of each other. Each slide must survive alone — if two hacks collapse into one idea, merge them and go shorter.
Framework D: Rant Callout (4–8 slides)
The "someone had to say it" carousel. Personality-led and polarizing by design — the structure exists to keep the heat fair so it reads as conviction, not bitterness.
| Slide | Job | Pattern |
|---|---|---|
| 1 — Provocative claim | An unpopular opinion or direct accusation about a common practice. | "Unpopular opinion: [common practice]" |
| 2 to N−2 — Escalate the argument | Sensory, specific detail. Show the offense; don't gesture at it abstractly. Each slide raises the stakes. | "[Escalating, specific complaint]" |
| N−1 — Fairness pivot | "Don't get me wrong…": clarify what you're not attacking. Anti-laziness, not anti-tool; anti-practice, not anti-person. | "I use [X] every day. My problem is [Y]." |
| N — Close | Firm, personality-forward sign-off. Signed rants read as owned opinions; anonymous ones read as potshots. | "[Firm sign-off]: signed [name/persona]" |
The fairness pivot is what makes it work. Without it you're yelling; with it you're drawing a precise line, and precise lines get quoted. It also pre-empts the top hostile comment.
SaaS example: "Your AI-generated LinkedIn posts are costing you customers." → the specifics (same em-dash cadence, same 'game-changer' vocabulary, zero lived detail) → "Don't get me wrong. I use AI daily. My problem is publishing the first draft." → "Write like you talk. [Name]"
Failure modes: skipping the pivot (reads unhinged, invites pile-ons), or ranting about something your own product/content visibly does (the comments will find it).
Framework E: Demo Walkthrough (5–11 slides)
The "watch it work" carousel for product or workflow content. Show the finished result first, then the steps — the outcome earns attention for the process.
| Slide | Job | Pattern |
|---|---|---|
| 1 — Product + outcome | Brand/product plus the finished result. Lead with what they get. | "[Product] + [outcome], finished result" |
| 2 — Problem it solves | The specific frustration this replaces. | "[The specific pain this replaces]" |
| 3 — Process overview | The numbered step list, shown before the detail. Seeing the whole path lowers mid-swipe drop-off — readers commit when they know how long the road is. | "[N] steps to [outcome] in [timeframe]" |
| 4 to N−1 — Step-by-step | One real UI screenshot per step with a short caption. Real screenshots; mockups read as vaporware. | "Step [n]: [screenshot] + [caption]" |
| N — Result + positioning | The full-size output plus one brand-philosophy line. | "[Final output] + [positioning line]" |
Overview-before-detail is the key move (same reason recipe sites list ingredients before instructions): a reader who's seen "4 steps, 10 minutes" on slide 3 will finish; a reader dropped straight into step 1 with no map bails at step 2.
SaaS example: "From CSV to live dashboard in 4 steps" → the pain (weekly manual reporting) → the 4-step overview → one screenshot per step → the finished dashboard + "Built for marketers, not analysts."
Failure mode: screenshots with too much UI. Crop to the action, zoom the relevant control, annotate with one arrow — each screenshot should make sense at thumbnail size.
Platform Notes
Instagram: 1080×1350 (4:5) slides; up to 20 slides but the frameworks' ranges above reflect where completion rates hold. The caption carries the searchable text — restate the hook and add context, don't just repeat slide 1. First slide doubles as the grid thumbnail.
LinkedIn (document posts): Upload as PDF. Square or 4:5. LinkedIn shows a "N pages" badge — Value-Stack's exact-count cover plays especially well here. B2B tolerates denser text per slide than Instagram, but the one-idea-per-slide rule still holds. The post text above the document is a second hook — write it as its own post, not a throwaway "see attached."
TikTok photo mode: Same frameworks work; pacing skews faster — trim each framework toward its minimum slide count.
Production Checklist
[ ] Slide 1 works as a standalone feed post (test: would it stop the scroll with no carousel behind it?)
[ ] One idea per slide — if a slide needs two sentences of setup, split it
[ ] Same visual template on every interior slide
[ ] Any count promised on the cover is exactly delivered (no filler, no rounding)
[ ] Claims and numbers are real and yours — no invented stats or borrowed screenshots
[ ] Text is legible at thumbnail size (minimum ~28pt at 1080px wide)
[ ] Final slide has one CTA, not three
[ ] Caption/post text written as its own hook, not a repeat of slide 1
Measuring What Worked
Judge carousels on saves and completion, not likes — saves signal reference value (the algorithmic win for carousels), and where per-slide analytics exist (Instagram professional insights, LinkedIn document analytics, or third-party tools), drop-off position tells you which slide broke the swipe chain. When a carousel underperforms, the fix is usually slide 1 (didn't stop the scroll) or the framework choice (list content forced into a rant structure), not the middle slides. Track per-framework performance and double down on the two that fit your audience — see reverse-engineering.md for the analysis workflow.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Corey Haines
- Publisher
- Corey Haines (Community)
- Source
- coreyhaines31/marketingskills · skills/social · commit 96798cf
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Corey Haines.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download social.zip