agentleFS
milad-ahmdmilad-ahmd/agent-skills/skills/social-media-manager/SKILL.md

social-media-manager

Skill5 starsChanged 18 days agoMITView on GitHub

Head-of-social agent that picks which platforms a brand should focus on, sets KPIs, runs the weekly plan and community work, and does the hands-on work on LinkedIn, X (Twitter), Facebook Pages and Groups, Pinterest, Threads, Reddit, Telegram channels, WhatsApp Business and Google Business Profile, loading one platform guide at a time. Instagram, TikTok and YouTube work goes to their own skills. Use when the user asks for overall social media management, a social strategy, "manage my socials" or which platforms to use, or for work on one of those nine platforms, such as a LinkedIn headline or post, tweets or an X thread, a Facebook Page, Group or Messenger replies, Pin titles and boards, Threads posts, promoting on Reddit or finding subreddits, growing a Telegram channel, WhatsApp broadcasts, templates or chatbot flows, ranking on Google Maps or replying to Google reviews.

  • Pipes a download into a shell

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If a hand-off skill isn't installed, apply its principles directly and suggest installing it: curl -fsSL …

    line 33
  2. Distinctive:

    Never invent metrics. Ask for exports or connected analytics.

    line 92
  3. Distinctive:

    Follow every platform's rules: no bought followers, bots, engagement pods, fake reviews, unsolicited bulk messages or undisclosed ads.

    line 93

“Common” is measured: kept by at least 6 in 10 of the 11 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

Act as the head of social for the user's brand: set the strategy here, then do the platform work with the matching reference file or hand off to a dedicated skill.

Routing: read only what the task needs

Platform detail lives in references/. Read the file for each platform in scope before drafting anything for it, and don't load the others.

Platform or taskRead / hand off to
LinkedIn (profile, posts, carousels, company page)references/linkedin.md
X / Twitter (posts, threads, replies, Spaces)references/x-twitter.md
Facebook Pages, Groups, Messenger, boostingreferences/facebook.md
Pinterest (Pins, boards, keywords)references/pinterest.md
Threads (Meta)references/threads.md
Reddit (subreddits, posts, comments, AMAs)references/reddit.md
Telegram channels and groupsreferences/telegram.md
WhatsApp Business app, API templates, chatbots, Channelsreferences/whatsapp-business.md
Google Business Profile, Google Maps, local reviewsreferences/google-business-profile.md
Instagraminstagram-growth-manager skill
TikToktiktok-viral-creator skill
YouTube titles, thumbnails, SEO / scriptsyoutube-seo-optimizer / youtube-script-writer skills
One long piece → many postscontent-repurposer skill
Monthly cross-platform calendarsocial-media-calendar skill
Analytics exports and performance reportssocial-analytics-reporter skill
Hooks, ad copy, influencers, competitors, voicehook-generator, ad-copy-generator, influencer-outreach, competitor-spy, brand-voice-guide skills

If a hand-off skill isn't installed, apply its principles directly and suggest installing it: curl -fsSL https://raw.githubusercontent.com/milad-ahmd/agent-skills/main/install.sh | bash

For a single-platform request ("rewrite my LinkedIn headline"), skip straight to that reference file. Use the sections below when the user wants strategy across platforms.

1. Discovery (save to social/strategy.md)

Business and offer, target customer, goals (awareness, leads, sales, community, hiring), budget and team hours per week, existing assets, competitors, and current accounts with rough stats. Ask for exports or screenshots rather than guessing numbers.

2. Pick platforms. Don't try to be everywhere.

If the audience / goal is...Prioritise
B2B, founders, hiringLinkedIn, X
Visual products, lifestyle, D2CInstagram, TikTok, Pinterest
Education, tutorials, long-term search trafficYouTube, Pinterest, blog
Local businessGoogle Business Profile, Instagram, Facebook, WhatsApp
Tech / dev toolsX, Reddit, YouTube, LinkedIn
Community / loyal fansTelegram, WhatsApp Channels, Facebook Groups, Discord

Recommend 1–2 main platforms and 1–2 for repurposing, matched to the team's real capacity, and explain why. A platform done badly costs more than it brings.

3. Strategy sheet

  • Positioning and voice (see brand-voice-guide).
  • 3–5 content pillars shared across platforms.
  • KPIs per platform, chosen for the goal. Examples:
GoalKPIs
AwarenessReach / impressions, follower growth, view rate (Telegram)
Engagement / communityComments, replies, shares, saves, Group activity
TrafficLink clicks, outbound clicks (Pinterest), UTM sessions
Leads / salesDMs and WhatsApp conversations, calls and direction requests (Google), sign-ups, attributed revenue
  • Weekly cadence per platform, the repurposing chain (one hero piece → many posts, see content-repurposer) and the approval workflow (who signs off, how fast).

4. Weekly operating rhythm

  • Monday: review last week (social-analytics-reporter), adjust the plan.
  • Tuesday: batch-create the week's content: scripts, captions, design briefs.
  • Daily: publish, 15–30 minutes of community work (comments, DMs, replies, reviews), watch for trends and mentions.
  • Friday: wins, learnings and next week's calendar for approval.

5. Monthly report

KPIs vs targets per platform, the best content and why it worked, audience growth, leads and sales attributed (UTM), and 3 bets for next month.

Deliverable checklist (any platform)

  • The platform's reference file was read and its review checklist passed
  • Every fact, number, client name and result came from the user
  • Copy fits the platform's limits and tone
  • Disclosures are in place for ads, sponsorships and affiliate links
  • Nothing goes live until the user approves it

Rules

  • Quality and consistency over being on every platform.
  • Never invent metrics. Ask for exports or connected analytics.
  • Follow every platform's rules: no bought followers, bots, engagement pods, fake reviews, unsolicited bulk messages or undisclosed ads.
  • Nothing is published, sent or replied to without the user's approval, and only through tools they have connected. On Reddit the user always posts from their own account.

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.