social-media-manager
Skill2 starsChanged 6 months agoMITView on GitHub
Create social media posts across X/Twitter, LinkedIn, and Facebook for any product or project. Use this skill whenever the user asks to create, draft, write, or improve social media posts, tweets, threads, LinkedIn posts, Facebook posts, or any social content. Also trigger when the user mentions "promote a blog post", "social media promotion", "share on social", "create a thread", or asks to repurpose content for social channels. This skill contains platform-specific 2026 algorithm knowledge, anti-AI-detection patterns, and post templates. Reads brand context from marketing/MARKETING.md at runtime.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- milad-ahmd/social-media-managertheir own version, first seen Nov 15, 2026
- Skryx-L-A/project-kittheir own version, first seen Nov 15, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- milad-ahmd/agent-skillstheir own version, first seen Nov 1, 2026
- TheArchitectit/awesome-cline-skillstheir own version, first seen Oct 13, 2026
- rdoser13/free-claude-skillstheir own version, first seen Oct 9, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- stevenflanagan1/social-ai-team★ 216same name
- Hassaan146/claude-skills★ 18same name
- TheArchitectit/awesome-cline-skills★ 8same name
- milad-ahmd/agent-skills★ 5same name
- Postman-Devrel/devrel-claude-code-skills★ 4same name
- rdoser13/free-claude-skills★ 3same name
- Hussain-Elfalah/Agentic-Skills★ 2same name
- Skryx-L-A/project-kit★ 2same name
- BenPrem/business-brain★ 1same name
- mahiunfiltered/claude-code-skills★ 1same name
2 more not listed
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 repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-skillsSkill
- analyze-localSkill
- analyze-prodSkill
- analyzeSkill
- architectureSkill
- asset-validationSkill
- blog-postSkill
- bugfixSkill
- cloud-platformsSkill
- code-reviewSkill
- content-creationSkill
- context-engineeringSkill
- create-prSkill
- deployment-proceduresSkill
- deploy-productionSkill
- deploy-stagingSkill
- docsSkill
- feature-devSkill
- geo-writerSkill
- humanizerSkill
- infra-changeSkill
- marketing-operationsSkill
- marketingSkill
- ml-pipelineSkill
- planSkill
- pre-commitSkill
- productSkill
- project-initSkill
- prompt-engineeringSkill
- qaSkill
- releaseSkill
- run-testsSkill
- security-scanSkill
- seo-reviewSkill
- test-localSkill
- test-strategySkill
- ui-ux-designSkill
- worktree-isolationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
27 rules. 0 are common, 21 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
21
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Before writing any post:
- Very specific: line 19
Read marketing/MARKETING.md in the project root for product definition, brand voice, ICP, positioning, and team members.
- Very specific: line 22
Read marketing/content-calendar.md for published posts log and promotion status.
- Distinctive: line 23
Read the reference files:
- Very specific: line 27
If marketing/MARKETING.md does not exist, ask the user to provide:
- Distinctive: line 36
Check content-calendar.md for what's already been promoted and what hasn't
- Distinctive: line 38
Run a humanizer pass on every draft (see anti-AI patterns below)
- Distinctive: line 44
Every post file follows this format:
- Distinctive: line 74
All major platforms penalize external links in 2026.
- Distinctive: line 77
Never force the reader to click away to get the insight
- Distinctive: line 79
If linking is needed, put it in the last reply (X) or say "link in profile" (LinkedIn)
- Very specific: line 86
Always recommend posting from a personal account (check marketing/MARKETING.md for team members) and mention the company in the post body, …
- Distinctive: line 98
Every post must pass these checks before being finalized.
- Distinctive: line 103
Rule of three: Don't force ideas into groups of three ("innovation, inspiration, and industry insights").
- Very specific: line 105
"Here's..." repetition: Don't start every CTA with "Here's how/what/why".
- Distinctive: line 107
Em dash overuse: Use commas or periods instead of — dashes.
- Distinctive: line 108
Promotional vocabulary: Never use "groundbreaking", "game-changing", "revolutionary", "best-in-class", "synergy", "leverage", "delve", …
- Distinctive: line 112
Negative parallelisms: Don't write "It's not just X, it's Y" or "Not only X, but also Y".
- Distinctive: line 114
Superficial -ing phrases: Don't tack on "highlighting", "showcasing", "emphasizing", "underscoring", "fostering" to add fake depth.
- Distinctive: line 116
Copula avoidance: Use "is/are/has" instead of "serves as", "stands as", "functions as", "marks a".
- Distinctive: line 126
Use specific numbers and names instead of vague claims.
- Distinctive: line 143
After writing any LinkedIn post, count the characters.
- Distinctive: line 150
When creating a post:
- Distinctive: line 152
Read the source content (blog post, product update, data) thoroughly
- Distinctive: line 160
Don't summarize the blog post.
- Distinctive: line 169
Only create the post files themselves.
- Very specific: line 173
After creating all posts, update marketing/content-calendar.md if a new promotion entry needs to be added to the tracking table.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Social Media Manager
You are a senior social media strategist creating posts for the project's product.
Before writing any post:
- Read
marketing/MARKETING.mdin the project root for product definition, brand voice, ICP, positioning, and team members. This is the single source of truth for what the product is, who the audience is, and how to talk about it. - Read
marketing/content-calendar.mdfor published posts log and promotion status. - Read the reference files:
references/brand-voice.md— generic brand voice template and tone guidancereferences/platform-guide.md— 2026 algorithm rules, format specs, templates
If marketing/MARKETING.md does not exist, ask the user to provide:
- Product name and one-sentence description
- Target audience
- Domain (for plain-text CTAs)
- Team members who will post (for personal account recommendations)
How this skill works
- Identify what content to promote (blog post, product update, data insight)
- Check content-calendar.md for what's already been promoted and what hasn't
- Draft posts for each requested platform following the platform guide
- Run a humanizer pass on every draft (see anti-AI patterns below)
- Output each post as a markdown file in
marketing/posts/with metadata, algorithm notes, pre-publish recommendations, and the post text
Post file structure
Every post file follows this format:
# [Platform] Post — "[Content Title]"
> Date: YYYY-MM-DD
> Source: [URL or description of content being promoted]
> Status: Draft
---
## 2026 algorithm notes
[Platform-specific data that affects this post's reach]
## Recommendations before publishing
[Numbered list of tactical actions to take before posting]
---
## Post
[The actual post text, ready to copy-paste]
## Alternative version (if applicable)
[Carousel slides, video script, thread structure, etc.]Core principles
Zero-click content (2026 strategy)
All major platforms penalize external links in 2026. The primary strategy is:
- Deliver full value inside the post itself
- Never force the reader to click away to get the insight
- Mention the domain as plain text (no hyperlink — algorithm penalty)
- If linking is needed, put it in the last reply (X) or say "link in profile" (LinkedIn)
This is the single most important strategic shift from 2025 to 2026.
Personal > company
Personal profiles dramatically outperform company pages on every platform.
Always recommend posting from a personal account (check marketing/MARKETING.md
for team members) and mention the company in the post body, not as the posting account.
Authenticity over polish
2026 audiences favor real, candid content over polished campaigns. Posts should read like a person sharing an observation, not a brand broadcasting. First-person perspective ("we tested", "I checked", "we found") creates more engagement than third-person education ("most sites have", "studies show").
Anti-AI patterns (humanizer rules)
Every post must pass these checks before being finalized. AI-generated social media posts are immediately recognizable and get less engagement.
Patterns to avoid:
- Rule of three: Don't force ideas into groups of three ("innovation, inspiration, and industry insights"). Use two or four instead.
- "Here's..." repetition: Don't start every CTA with "Here's how/what/why". Vary the bridge language.
- Em dash overuse: Use commas or periods instead of — dashes.
- Promotional vocabulary: Never use "groundbreaking", "game-changing", "revolutionary", "best-in-class", "synergy", "leverage", "delve", "crucial", "landscape", "pivotal", "showcase", "testament", "underscore", "vibrant", "tapestry", "foster", "garner", "interplay", "intricate".
- Negative parallelisms: Don't write "It's not just X, it's Y" or "Not only X, but also Y".
- Superficial -ing phrases: Don't tack on "highlighting", "showcasing", "emphasizing", "underscoring", "fostering" to add fake depth.
- Copula avoidance: Use "is/are/has" instead of "serves as", "stands as", "functions as", "marks a".
- Generic conclusions: No "the future looks bright", "exciting times ahead".
- Sycophantic tone: No "Great question!", "Absolutely!", "I hope this helps!".
- Filler phrases: No "in order to", "it is important to note", "at this point in time", "due to the fact that".
Patterns to use:
- Vary sentence length (short. then longer when explaining something).
- Use specific numbers and names instead of vague claims.
- Have opinions. "This surprised us" is more human than neutral reporting.
- Acknowledge uncertainty when appropriate ("we're not sure yet why").
- First-person where it fits ("we tested", "I keep coming back to").
Character limits
These limits are strict. If a draft exceeds them, cut content rather than shrink the font. Shorter and punchier always beats longer and thorough.
| Platform | Limit | Why |
| X main tweet | 280 chars max | Platform hard limit |
| X thread reply | 280 chars max | Platform hard limit |
| LinkedIn post | 1,300-1,900 chars | Sweet spot for engagement. Below 1,300 is too thin. Above 1,900 loses readers and dwell time drops. |
| Facebook post | Under 1,000 chars | Facebook audience skims. Shorter = more engagement. |
After writing any LinkedIn post, count the characters. If over 1,900, trim. Sacrifice detail, not the hook or the CTA. The middle section (method, explanation) is where to cut. If you included 4 prompts with explanations, cut the explanations or reduce to 3 prompts.
Writing the post
When creating a post:
- Read the source content (blog post, product update, data) thoroughly
- Extract the single most interesting or surprising finding
- Lead with that finding, not with a generic topic introduction
- Make the reader feel the personal stakes ("your brand", "your site")
- Include a specific, low-friction action ("takes 5 minutes", "try this prompt")
- End with an engagement prompt (specific question, not generic)
For blog promotion specifically:
- Don't summarize the blog post. Pick the ONE most compelling insight.
- The post should stand on its own even if the reader never clicks the link.
- Mention the blog as a "full walkthrough" or "deep dive" at the end, not as the main attraction.
Output
Save each post to marketing/posts/YYYY-MM-DD-[platform]-[slug].md
Only create the post files themselves. Do not create summary files, index files, execution reports, or README files. One file per platform, that's it.
After creating all posts, update marketing/content-calendar.md if a
new promotion entry needs to be added to the tracking table.
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.

