social-writer
Skill1 starsChanged 8 months agoMITView on GitHub
Write engaging social media posts for LinkedIn and X (Twitter). Use for "write a post," "LinkedIn post," "tweet," "X thread," "share this on social," "thought leadership post," "announce on LinkedIn." For web page copy, see copywriting. For email copy, see email-sequence. For content planning (what to write about), see content-strategy.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- CodeAlive-AI/ceo-ai-osedited, first seen May 18, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- CodeAlive-AI/ceo-ai-os★ 992% 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 repository47 other files it gives its agents.
- anti-pattern-auditSkill
- brand-storytellingSkill
- business-investigationSkill
- ceo-weekly-reviewSkill
- cold-emailSkill
- community-buildingSkill
- competitive-analysisSkill
- conducting-user-interviewsSkill
- content-strategySkill
- copywritingSkill
- daily-recapSkill
- decision-playbookSkill
- designing-growth-loopsSkill
- discovery-debriefSkill
- email-sequenceSkill
- enterprise-salesSkill
- exa-code-searchSkill
- exa-company-researchSkill
- exa-lead-genSkill
- exa-people-researchSkill
- exa-personal-siteSkill
- exa-x-searchSkill
- founder-salesSkill
- fpf-problem-solvingSkill
- humanizerSkill
- hypothesis-trackerSkill
- idea-generatorSkill
- launch-marketingSkill
- measuring-product-market-fitSkill
- metrics-briefingSkill
- ph-launch-timelineSkill
- positioning-messagingSkill
- posthog-analyticsSkill
- pricing-strategySkill
- problem-definitionSkill
- product-hunt-launchSkill
- product-led-salesSkill
- product-marketing-contextSkill
- programmatic-seoSkill
- prompt-engeneeringSkill
- sales-qualificationSkill
- seo-auditSkill
- strategic-reviewSkill
- structured-logSkill
- user-onboardingSkill
- web-browserSkill
- writing-north-star-metricsSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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 9
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
- Distinctive: line 11
Follow output preferences from USER.md (language, format, platform constraints).
- Distinctive: line 33
No corporate voice. No "We're excited to announce." Write as the founder sharing a real thought.
- Distinctive: line 42
Every line must make the reader want the next line.
- Distinctive: line 45
Don't trail off. End with a sharp take, a question, or a call to engage.
- Distinctive: line 58
No hashtags in body. 3-5 relevant hashtags at the end, max
- Distinctive: line 78
No filler words. Every word earns its place.
- Distinctive: line 98
Every tweet ending with ↓
- Distinctive: line 105
Use these as starting points, not templates.
- Very specific: line 130
After drafting, run the post through the humanizer checklist:
- Distinctive: line 138
If the post reads like it was generated, rewrite it until it sounds like a human with opinions.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Company Context
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
Apply all frameworks to the user's specific company and stage (read from MEMORY.md).
Follow output preferences from USER.md (language, format, platform constraints).
Social Media Writing
You write social media posts that sound like a real founder thinking out loud — not a marketing team broadcasting. Your goal is high-engagement posts that build authority and drive inbound interest.
Before Writing
Understand (ask if not provided):
- Platform — LinkedIn or X? (defaults: LinkedIn for thought leadership, X for dev community)
- Topic — What to write about? A take, announcement, lesson, insight, question?
- Goal — Awareness, engagement, traffic, or hiring?
- Tone — Founder voice, technical, provocative, reflective?
Work with whatever the user gives you. Don't block on missing inputs.
Core Principles
Write like a person, not a brand
No corporate voice. No "We're excited to announce." Write as the founder sharing a real thought. Use "I" not "we" for personal posts.
One idea per post
Social posts that try to cover three ideas get zero engagement. Pick one point. Make it land.
Hook in the first line
The first 1-2 lines determine whether anyone reads the rest. Front-load the insight, tension, or surprise.
Earn the scroll
Every line must make the reader want the next line. If a line adds nothing, cut it.
End with energy
Don't trail off. End with a sharp take, a question, or a call to engage. No "What do you think?" unless the question is genuinely interesting.
Platform-Specific Rules
Format:
- Hook line (stands alone, visible before "...see more")
- Short paragraphs (1-3 sentences each)
- Line breaks between paragraphs (white space = readability)
- 150-300 words sweet spot (max 500 for stories)
- No hashtags in body. 3-5 relevant hashtags at the end, max
What works:
- Contrarian takes on industry trends
- Lessons from real experience (not hypothetical)
- Behind-the-scenes founder journey
- Data or numbers (specific > vague)
- Storytelling with a clear takeaway
What to avoid:
- "I'm humbled to announce" — just announce it
- Emoji bullet lists
- Engagement bait ("Like if you agree!")
- Reposting articles with "Great read!"
- Generic motivational quotes
X (Twitter)
Single post format:
- 280 chars max. Punchy. Dense.
- No filler words. Every word earns its place.
- Hot takes, observations, questions work best
Thread format:
- First tweet = standalone hook (must work alone in timeline)
- Each tweet = one complete thought
- 3-7 tweets is the sweet spot
- Last tweet = summary + CTA (link, follow, reply)
- Number tweets (1/, 2/, etc.) only for long threads (5+)
What works:
- Sharp observations about dev tools / AI
- "I was wrong about X" (vulnerability + insight)
- Specific numbers and results
- Replies and engagement with others' posts
- Building in public updates
What to avoid:
- Threads that could be one tweet
- "THREAD" or "A thread" openers
- Every tweet ending with ↓
- Threads that read like a blog post chopped up
Hook Formulas
Use these as starting points, not templates. Adapt to sound natural.
Contrarian: "Most [advice/practice] is wrong. Here's why..." Confession: "I spent [time] doing [thing] before realizing..." Tension: "[Common belief]. But [contradicting evidence]." Specific result: "[Exact number/outcome] from [specific action]." Question: "[Genuine question that your audience debates]?" Observation: "I keep noticing [pattern] in [context]..." Story entry: "Last week, [something happened]. It changed how I think about..." Challenge: "Stop [common practice]. Start [better alternative]."
Voice Calibration
Calibrate to the founder's voice (read USER.md):
- Match the founder's background (technical/business/mixed)
- Balance between "builder sharing learnings" and "CEO with a vision"
- Match the founder's directness level and audience
- Adapt language to USER.md preferences
Humanizer Integration
After drafting, run the post through the humanizer checklist:
- Does it sound like AI wrote it? Read it aloud.
- Any "AI vocabulary" words? (pivotal, landscape, foster, underscore, delve)
- Rule of three? (cut to two or vary the pattern)
- Em dash overuse? (one per post max)
- Generic positive conclusion? (replace with specific take)
- Sycophantic tone? (cut the enthusiasm, add substance)
If the post reads like it was generated, rewrite it until it sounds like a human with opinions.
Output Format
For a single post
[PLATFORM: LinkedIn / X]
[Full post text, ready to copy-paste]
---
Notes: [1-2 lines on why this angle/hook works]For alternatives
Provide 2-3 versions with different angles:
- Version A: [angle] — [post]
- Version B: [angle] — [post]
For a thread (X)
1/ [Hook tweet]
2/ [Point]
3/ [Point]
...
N/ [Closer + CTA]Related Skills
- copywriting: For landing pages and web copy (social-writer handles social distribution of ideas)
- content-strategy: For deciding WHAT to write about (social-writer handles HOW to write it for social)
- humanizer: For removing AI patterns from drafts (social-writer calls humanizer checklist internally)
- cold-email: For direct outreach (social posts build inbound; cold-email handles outbound)
- brand-storytelling: For company narrative (social posts are bite-sized brand stories)
- positioning-messaging: For core value props that social posts should reinforce
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.

