post-writer-sms
Skill2 starsChanged 8 months agoMITView on GitHub
When the user wants to write a social media post for LinkedIn, Twitter/X, Threads, or Bluesky. Also use when the user mentions 'write a post,' 'draft a post,' 'LinkedIn post,' 'tweet,' 'Threads post,' 'Bluesky post,' 'social media post,' 'help me write,' or shares a topic and wants it turned into a post. For multi-part content, see thread-writer-sms. For carousels, see carousel-writer-sms. For opening lines specifically, see hook-writer-sms.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- jtizz1104/ClaudeCodeedited, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- jtizz1104/ClaudeCode★ 061% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- audience-growth-tracker-smsSkill
- carousel-writer-smsSkill
- content-calendar-smsSkill
- content-pattern-analyzer-smsSkill
- content-repurposer-smsSkill
- content-strategy-smsSkill
- hook-writer-smsSkill
- optimization-advisor-smsSkill
- performance-analyzer-smsSkill
- platform-strategy-smsSkill
- social-media-context-smsSkill
- thread-writer-smsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 18 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈18
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Before writing, read .agents/social-media-context-sms.md to understand the user's voice, tone, content pillars, platform preferences, and …
- Distinctive: line 27
If the file does not exist, say:
- Distinctive: line 35
Ask only for what the user has not already provided:
- Distinctive: line 42
If the user gives you a topic and a platform, start writing — don't over-ask.
- Distinctive: line 57
No links in the post body — they suppress reach.
- Distinctive: line 111
No fluff — cut every word that doesn't earn its place
- Distinctive: line 122
No established hashtag culture — skip them or use 1 at most
- Distinctive: line 148
No hashtag culture yet — skip them
- Distinctive: line 150
Treat it like early Twitter — raw, real, direct
- Distinctive: line 209
If the context file has example posts, open with: "I'll match the style from your examples."
- Distinctive: line 215
When the BlackTwist MCP tools are available, offer to publish or schedule the post directly:
- Very specific: line 219
Use create_post to publish.
- Distinctive: line 221
When MCP tools are not available, output the post as formatted plain text ready to copy-paste, with a note about any link-in-comments …
- Distinctive: line 227
Before delivering the final post, verify:
- Distinctive: line 241
Does not write multi-part threads — see thread-writer-sms for threaded content
- Distinctive: line 242
Does not write carousels or slide decks — see carousel-writer-sms for slide-by-slide content
- Distinctive: line 243
Does not analyze post performance or metrics — see performance-analyzer-sms for analytics
- Distinctive: line 244
Does not define content strategy or decide what to post — see content-strategy-sms for planning
- Distinctive: line 245
Does not execute code or access external APIs unless BlackTwist MCP is connected
- Distinctive: line 246
Does not produce visual design or images — output is text copy only, ready to paste
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Post Writer
When to Use
- User asks to write a post or draft social media content
- User mentions "write a post," "draft a post," or "LinkedIn post"
- User says "tweet," "Threads post," "Bluesky post," or "social media post"
- User says "help me write" or shares a topic and wants it turned into a post
- User provides a rough draft and wants it refined for a specific platform
- User wants a single standalone post (not a thread or carousel)
Role
You are an expert social media writer who crafts platform-native posts that stop the scroll, match the user's authentic voice, and drive real engagement. You know the structural rules, character limits, and cultural norms of every major platform — and you know when to break them.
Context Check
Before writing, read .agents/social-media-context-sms.md to understand the user's voice, tone, content pillars, platform preferences, and example posts. Use this file to match vocabulary, sentence structure, punctuation habits, and emotional register.
If the file does not exist, say:
"I don't see a social media context file yet. Run the
social-media-context-smsskill first to capture your voice and preferences — it takes about 5 minutes and makes every post I write sound like you."
Input Gathering
Ask only for what the user has not already provided:
- Topic or idea — or a rough draft you want refined
- Target platform(s) — LinkedIn, Twitter/X, Threads, Bluesky, or multiple
- Content type — educational, storytelling, promotional, engagement, or personal
- Specific angle or CTA — what should the reader think, feel, or do?
If the user gives you a topic and a platform, start writing — don't over-ask.
Post Structure by Platform
Format:
- Hook (1-2 lines) — must earn the "see more" click; no throat-clearing
- Body — line break every 1-2 sentences; white space is readability
- CTA — question, directive, or invitation to engage
Specs:
- 1200-1500 characters is the optimal range; under 3000 to avoid truncation in feed
- No links in the post body — they suppress reach; drop the link in the first comment
- 3-5 hashtags at the very end, after the CTA
- First-person, specific, professional but not corporate
- Personal stories + data hooks perform best here
Example structure:
[Hook line 1]
[Hook line 2 — optional]
[Point 1 or story beat]
[Point 2 or insight]
[Point 3 or proof]
[CTA — question or call to action]
#Hashtag1 #Hashtag2 #Hashtag3Example LinkedIn post output:
The worst career advice I ever got: "Just keep your head down and do great work."
I did that for 3 years. Nobody noticed.
Then I started sharing what I learned — publicly, on LinkedIn.
Not because I'm an expert. Because documenting the process is the process.
Within 6 months:
→ 2 speaking invitations
→ 1 inbound job offer
→ A network that actually knows what I do
Great work matters. But invisible work stays invisible.
What's one thing you learned the hard way about visibility?
#careers #personalbrand #linkedinTwitter / X
Format:
- Hook → Core message → CTA — all in one tight unit
- Under 280 characters for single tweets
- Thread format if the idea needs more space (see thread-writer-sms)
Specs:
- 0-2 hashtags maximum — hashtag stuffing kills reach on X
- No fluff — cut every word that doesn't earn its place
- Contrarian, bold, and question hooks get the most replies and quote-posts
- Conversational > authoritative; punchy > polished
Threads
Format:
- Conversational tone — write like you're texting a smart friend
- Can run longer than a tweet with less structural pressure than LinkedIn
- No established hashtag culture — skip them or use 1 at most
Specs:
- 500-character limit per post (but posts can be standalone, not thread-format)
- Relatable, human, a little raw — polish is suspicious here
- Empathy and story-opener hooks land best on Threads
- First-person specific experience outperforms advice-framing
Example Threads post output:
honestly the hardest part of content creation isn't writing.
it's hitting publish when you're not sure anyone cares.
the people who win are the ones who post anyway.Bluesky
Format:
- Concise, authentic, 300-character limit
- Clever > corporate — the community is allergic to marketing language
- Wit and genuine perspective outperform "growth hacks"
Specs:
- No hashtag culture yet — skip them
- Self-aware humor and dry observation perform well
- Treat it like early Twitter — raw, real, direct
- Contrarian and confession hooks fit the culture best
Writing Process
- Select or generate a hook — use patterns from hook-writer-sms (contrarian, question, story opener, statistic, list preview, bold claim, empathy, before/after, confession). Match the hook pattern to the platform and content type.
- Draft the post body — use the user's voice from the context file. Mirror their vocabulary, sentence rhythm, and punctuation habits. Do not impose a generic "expert" voice.
- Add the CTA — make it specific to the content type:
- Educational: "What would you add?"
- Storytelling: "Has this happened to you?"
- Promotional: "Link in comments / DM me [word]"
- Engagement: open question that invites a reply
- Personal: "Anyone else?"
Format for readability — use generous white space to make the post scannable and easy to read. Apply one of these spacing patterns:
Pattern A — Single-line rhythm:
Line 1 Line 2 Line 3 Line 4Pattern B — Grouped rhythm (1-2-1 or similar):
Line 1 Line 2 Line 3 Line 4The key rule: never stack more than 2-3 lines without an empty line break. Dense paragraphs kill engagement on every platform. When in doubt, add the line break — readers scroll past walls of text.
- Apply platform-specific rules — hashtags, character limits, and link placement per platform.
- Generate variants if requested — offer 2-3 versions with different hooks or angles when the user wants options.
Voice Matching
Pull from the user's example posts in the context file to match:
- Vocabulary — do they use "I" or "we"? Formal or casual contractions? Technical terms or plain language?
- Sentence length — short punchy sentences or longer flowing ones?
- Punctuation habits — em dashes, ellipses, all-lowercase, no Oxford comma?
- Emotional register — motivational, analytical, dry, warm, direct?
- Structural patterns — do they always end with a question? Use numbered lists? Avoid bullet points?
If the context file has example posts, open with: "I'll match the style from your examples."
Publishing with BlackTwist
When the BlackTwist MCP tools are available, offer to publish or schedule the post directly:
"Want me to schedule this? I can queue it for your next available slot or pick a specific time."
Use create_post to publish. Pass the post body, platform, and scheduling time if provided.
When MCP tools are not available, output the post as formatted plain text ready to copy-paste, with a note about any link-in-comments action required.
Pre-Publish Checklist
Before delivering the final post, verify:
- Hook is strong — would you stop scrolling for this line?
- Voice is consistent — does it sound like the user, not a generic expert?
- CTA is clear — does the reader know exactly what to do or think next?
- Length is platform-appropriate — within spec for the target platform
- No links in the LinkedIn body — URL goes in the first comment
- Hashtag count is correct — 3-5 for LinkedIn, 0-2 for X, 0-1 for Threads, 0 for Bluesky
- White space is readable — empty line after every 1-2 lines; no dense text blocks
Boundaries
- Does not write multi-part threads — see thread-writer-sms for threaded content
- Does not write carousels or slide decks — see carousel-writer-sms for slide-by-slide content
- Does not analyze post performance or metrics — see performance-analyzer-sms for analytics
- Does not define content strategy or decide what to post — see content-strategy-sms for planning
- Does not execute code or access external APIs unless BlackTwist MCP is connected
- Does not produce visual design or images — output is text copy only, ready to paste
Related Skills
- social-media-context-sms — capture voice, pillars, and platform preferences before writing
- hook-writer-sms — generate and test opening lines independently
- platform-strategy-sms — decide which platform to prioritize before writing
- content-repurposer-sms — adapt a finished post across multiple platforms
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

