agentleFS
vindreshsinghvindreshsingh/engineering-skills/skills/marketing/social-distribution/SKILL.md

social-distribution

Skill0 starsChanged 5 months agoMITView on GitHub

Plans and writes short-form social content and distributes it across platforms — posts, threads, carousels, and launch announcements. Use when you need daily social presence, launch threads, or platform-specific content that drives traffic and engagement.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

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

    Never astroturf; be transparent you're the builder

    line 67
  2. Very specific:

    Add discussion tag; engage in comments

    line 72
  3. Distinctive:

    Every post is "Sign up now!" with no value

    line 135

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

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

Social Distribution

Social is where developers discover products between commits. This skill turns strategy and long-form content into platform-native posts — not the same caption pasted everywhere. Each platform has different norms; respect them or get ignored.

Chains from [[growth-strategy]] (channels, pillars, calendar) and [[content-marketing]] (articles to snippet). Feeds traffic to landing pages optimized via [[seo-growth]]; engagement handled by [[community-engagement]] in comments and DMs.

When to Use

  • Daily/weekly social posting cadence
  • Launch announcement threads (X, LinkedIn)
  • Repurposing a blog post into social snippets
  • Product update posts, feature highlights, tips
  • Engagement replies and quote-tweet strategy (templates)
  • Planning a Show HN / Product Hunt / Reddit launch post

Skip for long-form articles — use [[content-marketing]]. Skip for in-community moderation — use [[community-engagement]].

Process

1. Load the distribution brief

From [[growth-strategy]] or gather:

  • Platforms (primary + secondary) — X, LinkedIn, Reddit, Instagram, etc.
  • Cadence — e.g. X 1/day, LinkedIn 3/week, Reddit 1/week value post
  • Campaign theme — this week's pillar
  • Links — landing page, UTM-tagged URLs per platform
  • Voice — technical, helpful, no cringe hype
  • Assets — GIFs, screenshots, demo video links from content team

Build UTM pattern: ?utm_source=x&utm_medium=social&utm_campaign=[campaign]

2. Platform playbooks

Adapt format and tone per platform:

X / Twitter

  • Hooks in first line — pain, stat, or bold claim
  • Threads: 5–10 tweets, one idea per tweet, last tweet = CTA + link
  • Code snippets, screenshots, short demo GIFs perform well
  • Reply to relevant dev conversations (don't spam links)
  • 1–2 hashtags max; often zero is better

LinkedIn

  • Professional story arc — problem → journey → lesson → soft CTA
  • Carousels: 5–8 slides, one point per slide, last slide CTA
  • Tag people sparingly; authenticity over engagement bait
  • Comment on posts in your ICP's feed

Reddit

  • Read subreddit rules first — many ban self-promotion
  • Value-first post: full guide in text; link at end or in comment if allowed
  • r/SideProject, r/webdev, r/cscareerquestions, r/startups — pick where ICP lives
  • Never astroturf; be transparent you're the builder

Dev.to / Hashnode

  • Cross-post tutorials with canonical URL if blog exists
  • Add discussion tag; engage in comments

Hacker News / Product Hunt

  • One-shot launch; prepare title, tagline, first comment (maker story)
  • HN: "Show HN: [Product] — [specific benefit]" not marketing speak
  • PH: clear screenshots, maker comment, respond to every question for 24h

3. Content batch — weekly pack

Produce a 7-day pack (adjust cadence to brief):

DayPlatformTypeHook (draft)CTAAsset
MonXTip thread
TueLinkedInStory post
WedXProduct demo GIF
ThuRedditValue post
FriLinkedInCarousel
SatXUser quote / win
SunXBehind-the-build

Each row: full draft text ready to copy-paste, character count for X, hashtag notes.

4. Launch sequence (when applicable)

For product/feature launch, run this sequence:

  1. T-7 days — teaser ("building something for dev networking")
  2. T-3 days — problem thread (pain without naming product)
  3. T-1 day — "launching tomorrow" + what to expect
  4. Launch day — thread + LinkedIn + Reddit/HN/PH per brief
  5. T+1 — thank you + early user highlight
  6. T+7 — results/learnings post (transparency builds trust)

Draft all six in one sitting; schedule or queue.

5. Engagement rules

  • Reply within 24h to comments on your posts — template helpful replies, not "thanks!"
  • Quote tweets / reshare user wins and feedback (with permission)
  • Never argue in public threads — take heated DMs offline
  • Track which hooks got saves/shares — feed back to [[growth-strategy]] weekly review

6. Compliance and quality gate

Before publishing:

  • Link works and UTM tags correct
  • No unverified claims
  • Platform character limits respected
  • Reddit/forum post follows that community's rules
  • Screenshots don't expose private user data

Common Rationalizations

  • "Same post everywhere saves time" — Lazy cross-posting gets zero engagement everywhere.
  • "More hashtags = more reach" — On X and LinkedIn, hashtag stuffing looks spammy.
  • "Reddit is free advertising" — Reddit will ban you. Lead with value.
  • "We'll engage later" — First-hour replies boost reach; schedule time for launch day.

Red Flags

  • Every post is "Sign up now!" with no value
  • Links broken or missing UTM tracking
  • Launch day with no maker story or demo
  • Ignoring comments on launch posts
  • Posting promotional content in communities that forbid it

Verification

Distribution pack is done when:

  • Weekly post pack with full drafts per platform
  • UTM links defined for each platform
  • Launch sequence drafted (if launch campaign)
  • Engagement reply templates for common questions
  • Platform rule check for Reddit/forum posts
  • Quality gate checklist passed

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.