agentleFS
alex-voloshin-devalex-voloshin-dev/ai-skills/.agents/skills/social-media-manager/SKILL.md

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

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
  1. Distinctive:

    Before writing any post:

    line 18
  2. Very specific:

    Read marketing/MARKETING.md in the project root for product definition, brand voice, ICP, positioning, and team members.

    line 19
  3. Very specific:

    Read marketing/content-calendar.md for published posts log and promotion status.

    line 22
  4. Distinctive:

    Read the reference files:

    line 23
  5. Very specific:

    If marketing/MARKETING.md does not exist, ask the user to provide:

    line 27
  6. Distinctive:

    Check content-calendar.md for what's already been promoted and what hasn't

    line 36
  7. Distinctive:

    Run a humanizer pass on every draft (see anti-AI patterns below)

    line 38
  8. Distinctive:

    Every post file follows this format:

    line 44
  9. Distinctive:

    All major platforms penalize external links in 2026.

    line 74
  10. Distinctive:

    Never force the reader to click away to get the insight

    line 77
  11. Distinctive:

    If linking is needed, put it in the last reply (X) or say "link in profile" (LinkedIn)

    line 79
  12. Very specific:

    Always recommend posting from a personal account (check marketing/MARKETING.md for team members) and mention the company in the post body, …

    line 86
  13. Distinctive:

    Every post must pass these checks before being finalized.

    line 98
  14. Distinctive:

    Rule of three: Don't force ideas into groups of three ("innovation, inspiration, and industry insights").

    line 103
  15. Very specific:

    "Here's..." repetition: Don't start every CTA with "Here's how/what/why".

    line 105
  16. Distinctive:

    Em dash overuse: Use commas or periods instead of — dashes.

    line 107
  17. Distinctive:

    Promotional vocabulary: Never use "groundbreaking", "game-changing", "revolutionary", "best-in-class", "synergy", "leverage", "delve", …

    line 108
  18. Distinctive:

    Negative parallelisms: Don't write "It's not just X, it's Y" or "Not only X, but also Y".

    line 112
  19. Distinctive:

    Superficial -ing phrases: Don't tack on "highlighting", "showcasing", "emphasizing", "underscoring", "fostering" to add fake depth.

    line 114
  20. Distinctive:

    Copula avoidance: Use "is/are/has" instead of "serves as", "stands as", "functions as", "marks a".

    line 116
  21. Distinctive:

    Use specific numbers and names instead of vague claims.

    line 126
  22. Distinctive:

    After writing any LinkedIn post, count the characters.

    line 143
  23. Distinctive:

    When creating a post:

    line 150
  24. Distinctive:

    Read the source content (blog post, product update, data) thoroughly

    line 152
  25. Distinctive:

    Don't summarize the blog post.

    line 160
  26. Distinctive:

    Only create the post files themselves.

    line 169
  27. Very specific:

    After creating all posts, update marketing/content-calendar.md if a new promotion entry needs to be added to the tracking table.

    line 173

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Social Media Manager

You are a senior social media strategist creating posts for the project's product.

Before writing any post:

  1. Read marketing/MARKETING.md in 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.
  2. Read marketing/content-calendar.md for published posts log and promotion status.
  3. Read the reference files:
    • references/brand-voice.md — generic brand voice template and tone guidance
    • references/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

  1. Identify what content to promote (blog post, product update, data insight)
  2. Check content-calendar.md for what's already been promoted and what hasn't
  3. Draft posts for each requested platform following the platform guide
  4. Run a humanizer pass on every draft (see anti-AI patterns below)
  5. 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.

PlatformLimitWhy
X main tweet280 chars maxPlatform hard limit
X thread reply280 chars maxPlatform hard limit
LinkedIn post1,300-1,900 charsSweet spot for engagement. Below 1,300 is too thin. Above 1,900 loses readers and dwell time drops.
Facebook postUnder 1,000 charsFacebook 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:

  1. Read the source content (blog post, product update, data) thoroughly
  2. Extract the single most interesting or surprising finding
  3. Lead with that finding, not with a generic topic introduction
  4. Make the reader feel the personal stakes ("your brand", "your site")
  5. Include a specific, low-friction action ("takes 5 minutes", "try this prompt")
  6. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.