🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
πŸ¦€ ClawHub

Cross Poster

by @vanthienha199

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

Versionv1.0.0
Downloads401
TERMINAL
clawhub install cross-poster

πŸ“– About This Skill


name: social-poster description: > 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". tags: - social - twitter - linkedin - reddit - devto - marketing - cross-post - content

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
  • πŸ”’ Constraints

  • 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