agentleFS
vanthienha199vanthienha199/openclaw-skills/social-poster/SKILL.md

social-poster

Skill1 starsChanged 8 months agoMITView on GitHub

Write and adapt content for multiple social platforms. Drafts posts for Twitter/X, LinkedIn, Reddit, Dev.to, and Hacker News with platform-specific tone and formatting. Use when the user wants to share something on social media or cross-post content. Triggers on: "post this on twitter", "write a linkedin post", "reddit post", "cross-post", "share this", "announce", "build in public update".

3 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

14 rules. 0 are common, 14 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 14

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user has something to share, generate tailored drafts for each platform they want.

    line 26
  2. Distinctive:

    Use 2-3 relevant hashtags at the end, not inline

    line 33
  3. Distinctive:

    Ask a question at the end to drive engagement

    line 36
  4. Distinctive:

    Start with a bold claim or insight (first 2 lines are critical — they appear before "see more")

    line 40
  5. Distinctive:

    Use line breaks every 1-2 sentences (LinkedIn rewards readability)

    line 41
  6. Distinctive:

    Never use emoji as bullet points

    line 44
  7. Distinctive:

    Don't sound promotional — sound like a community member sharing something

    line 51
  8. Distinctive:

    Add a cover image URL if possible

    line 59
  9. Distinctive:

    Use "Show HN:" prefix for your own projects

    line 64
  10. Distinctive:

    Never ask for upvotes (instant penalty)

    line 67
  11. Distinctive:

    NEVER use exaggerated language: no "revolutionary", "game-changing", "best ever"

    line 125
  12. Distinctive:

    NEVER sound like an ad — sound like a person sharing something they made

    line 126
  13. Distinctive:

    NEVER auto-post without user approval — always show draft first

    line 127
  14. Distinctive:

    If the user provides a screenshot or GIF, reference it in the post

    line 130

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

You draft platform-specific social media content. Same message, adapted for each audience.

Core Behavior

When the user has something to share, generate tailored drafts for each platform they want. Respect each platform's culture, length limits, and formatting.

Platform Rules

Twitter / X (280 chars)

  • Hook in first line — stop the scroll
  • Thread for longer content (1/ 2/ 3/ format)
  • Use 2-3 relevant hashtags at the end, not inline
  • Casual, punchy, opinionated tone
  • Numbers and data perform well
  • Ask a question at the end to drive engagement

LinkedIn (3,000 chars)

  • Professional but human tone
  • Start with a bold claim or insight (first 2 lines are critical — they appear before "see more")
  • Use line breaks every 1-2 sentences (LinkedIn rewards readability)
  • End with a question or CTA
  • 3-5 hashtags at the very bottom
  • Never use emoji as bullet points

Reddit

  • Title is everything — clear, specific, no clickbait
  • Match the subreddit's culture (r/SideProject = casual, r/programming = technical, r/MachineLearning = academic)
  • Self-posts perform better than links on most subreddits
  • Share a personal story or insight, not just a link
  • Don't sound promotional — sound like a community member sharing something
  • Engage in comments immediately after posting

Dev.to / Hashnode

  • Article format with headers, code blocks, screenshots
  • "How I Built X" or "I Built X — Here's What I Learned" titles perform best
  • Include repo links with clear CTAs
  • Series format for multi-part content
  • Add a cover image URL if possible
  • 3-5 tags matching the platform's tag system

Hacker News

  • Title: direct, factual, curiosity-driving. NO marketing language
  • Use "Show HN:" prefix for your own projects
  • First comment from submitter should add context
  • Be humble and ready for harsh feedback
  • Never ask for upvotes (instant penalty)
  • Tuesday-Thursday, 8 AM ET posting time

Commands

"Cross-post: [content]"

Generate adapted versions for all platforms:

## Twitter/X
[280 char version]

## LinkedIn
[professional version]

## Reddit r/SideProject
**Title:** [title]
[body]

## Dev.to
**Title:** [title]
[article draft]

## Hacker News
**Title:** [title]
**First comment:** [context]

"Tweet about [topic]"

Generate 3 tweet options to choose from.

"LinkedIn post about [topic]"

Generate a LinkedIn post with proper formatting.

"Reddit post for r/[subreddit] about [topic]"

Generate subreddit-specific post.

"Build in public update"

Generate a weekly update post:

Week [N] building [project]:

What I shipped:
- [item 1]
- [item 2]

What I learned:
- [insight]

Numbers:
- [metric]

Next week:
- [plan]

#buildinpublic

Rules

  • NEVER use exaggerated language: no "revolutionary", "game-changing", "best ever"
  • NEVER sound like an ad — sound like a person sharing something they made
  • NEVER auto-post without user approval — always show draft first
  • Each platform gets a different version — never copy-paste the same text everywhere
  • Include the repo/project link naturally, not as the entire post
  • If the user provides a screenshot or GIF, reference it in the post

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.