Content distribution

Content Engine

Build platform-native content without flattening the author's real voice into platform slop.

When to use

• writing X posts or threads
• drafting LinkedIn posts or launch updates
• scripting short-form video or YouTube explainers
• repurposing articles, podcasts, demos, docs, or internal notes into public content
• building a launch sequence or ongoing content system around a product, insight, or narrative

Non-Negotiables

1. Start from source material, not generic post formulas.
2. Adapt the format for the platform, not the persona.
3. One post should carry one actual claim.
4. Specificity beats adjectives.
5. No engagement bait unless the user explicitly asks for it.

Source-First Workflow

Before drafting, identify the source set:

• published articles
• notes or internal memos
• product demos
• docs or changelogs
• transcripts
• screenshots
• prior posts from the same author

If the user wants a specific voice, build a voice profile from real examples before writing. Use brand-voice as the canonical workflow when voice consistency matters across more than one output.

Voice Handling

brand-voice is the canonical voice layer.

Run it first when:

• there are multiple downstream outputs
• the user explicitly cares about writing style
• the content is launch, outreach, or reputation-sensitive

Reuse the resulting VOICE PROFILE here instead of rebuilding a second voice model. If the user wants / editorial style specifically, still treat brand-voice as the source of truth and feed it the best live or source-derived material available.

Hard Bans

Delete and rewrite any of these:

• "In today's rapidly evolving landscape"
• "game-changer", "revolutionary", "cutting-edge"
• "here's why this matters" unless it is followed immediately by something concrete
• ending with a LinkedIn-style question just to farm replies
• forced casualness on LinkedIn
• fake engagement padding that was not present in the source material

Platform Adaptation Rules

X

• open with the strongest claim, artifact, or tension
• keep the compression if the source voice is compressed
• if writing a thread, each post must advance the argument
• do not pad with context the audience does not need

LinkedIn

• expand only enough for people outside the immediate niche to follow
• do not turn it into a fake lesson post unless the source material actually is reflective
• no corporate inspiration cadence
• no praise-stacking, no "journey" filler

Short Video

• script around the visual sequence and proof points
• first seconds should show the result, problem, or punch
• do not write narration that sounds better on paper than on screen

YouTube

• show the result or tension early
• organize by argument or progression, not filler sections
• use chaptering only when it helps clarity

Newsletter

• open with the point, conflict, or artifact
• do not spend the first paragraph warming up
• every section needs to add something new

Repurposing Flow

1. Pick the anchor asset.
2. Extract 3 to 7 atomic claims or scenes.
3. Rank them by sharpness, novelty, and proof.
4. Assign one strong idea per output.
5. Adapt structure for each platform.
6. Strip platform-shaped filler.
7. Run the quality gate.

Deliverables

When asked for a campaign, return:

• a short voice profile if voice matching matters
• the core angle
• platform-native drafts
• posting order only if it helps execution
• gaps that must be filled before publishing

Quality Gate

Before delivering:

• every draft sounds like the intended author, not the platform stereotype
• every draft contains a real claim, proof point, or concrete observation
• no generic hype language remains
• no fake engagement bait remains
• no duplicated copy across platforms unless requested
• any CTA is earned and user-approved

Related Skills

• brand-voice for source-derived voice profiles
• crosspost for platform-specific distribution
• x-api for sourcing recent posts and publishing approved X output

---

Crosspost

Distribute content across platforms without turning it into the same fake post in four costumes.

When to use

• the user wants to publish the same underlying idea across multiple platforms
• a launch, update, release, or essay needs platform-specific versions
• the user says "crosspost", "post this everywhere", or "adapt this for X and LinkedIn"

Core Rules

1. Do not publish identical copy across platforms.
2. Preserve the author's voice across platforms.
3. Adapt for constraints, not stereotypes.
4. One post should still be about one thing.
5. Do not invent a CTA, question, or moral if the source did not earn one.

Workflow

Step 1: Start with the Primary Version

Pick the strongest source version first:

• the original X post
• the original article
• the launch note
• the thread
• the memo or changelog

Use content-engine first if the source still needs voice shaping.

Step 2: Capture the Voice Fingerprint

Run brand-voice first if the source voice is not already captured in the current session.

Reuse the resulting VOICE PROFILE directly. Do not build a second ad hoc voice checklist here unless the user explicitly wants a fresh override for this campaign.

Step 3: Adapt by Platform Constraint

X

• keep it compressed
• lead with the sharpest claim or artifact
• use a thread only when a single post would collapse the argument
• avoid hashtags and generic filler

LinkedIn

• add only the context needed for people outside the niche
• do not turn it into a fake founder-reflection post
• do not add a closing question just because it is LinkedIn
• do not force a polished "professional tone" if the author is naturally sharper

Threads

• keep it readable and direct
• do not write fake hyper-casual creator copy
• do not paste the LinkedIn version and shorten it

Bluesky

• keep it concise
• preserve the author's cadence
• do not rely on hashtags or feed-gaming language

Posting Order

Default:

1. post the strongest native version first
2. adapt for the secondary platforms
3. stagger timing only if the user wants sequencing help

Do not add cross-platform references unless useful. Most of the time, the post should stand on its own.

Banned Patterns

Delete and rewrite any of these:

• "Excited to share"
• "Here's what I learned"
• "What do you think?"
• "link in bio" unless that is literally true
• generic "professional takeaway" paragraphs that were not in the source

Output Format

Return:

• the primary platform version
• adapted variants for each requested platform
• a short note on what changed and why
• any publishing constraint the user still needs to resolve

Quality Gate

Before delivering:

• each version reads like the same author under different constraints
• no platform version feels padded or sanitized
• no copy is duplicated verbatim across platforms
• any extra context added for LinkedIn or newsletter use is actually necessary

Related Skills

• brand-voice for reusable source-derived voice capture
• content-engine for voice capture and source shaping
• x-api for X publishing workflows

---

Social Publisher (SocialClaw)

Connects Claude Code to SocialClaw for agent-driven social media publishing across 13 platforms through a single workspace API key.

When to use

• publish content to X, LinkedIn, Instagram, TikTok, or other platforms
• schedule a post campaign across multiple platforms at once
• upload media for use in social posts
• validate a post schedule before going live
• monitor publishing run status and delivery analytics

Setup

# Required: workspace API key from https://getsocialclaw.com/dashboard
export SC_API_KEY="<workspace-key>"

# Verify access
printf 'header = "Authorization: Bearer %s"\n' "$SC_API_KEY" |
  curl -sS -K - https://getsocialclaw.com/v1/keys/validate

# Install CLI (optional but recommended)
npm install -g [email protected]
socialclaw login --api-key <workspace-key>

Core Workflow

1. List connected accounts

socialclaw accounts list --json

If not connected:

socialclaw accounts connect --provider x --open
socialclaw accounts connect --provider linkedin --open

2. Upload media (optional)

socialclaw assets upload --file ./image.png --json
# → { "asset_id": "..." }

3. Build schedule.json

{
  "posts": [
    {
      "provider": "x",
      "account_id": "<account-id>",
      "text": "Post text here",
      "scheduled_at": "2026-06-01T10:00:00Z"
    }
  ]
}

Optional X/Twitter evidence packet

Before building an X schedule, collect a source packet when the campaign depends on live audience signals rather than the draft alone.

For OpenClaw users who have already approved TweetClaw in their dependency policy, use the pinned package as a separate evidence source:

openclaw plugins install npm:@xquik/[email protected]

Use it for public tweet search, reply search, follower export, user lookup, media review, monitors, or giveaway evidence. Keep the output as research input for schedule.json; SocialClaw remains responsible for validation, scheduling, publishing, and delivery status. Store TweetClaw credentials in its plugin config, not in SC_API_KEY, schedule files, or campaign assets. Do not install it as a default SKC or SocialClaw dependency.

4. Validate before publishing

socialclaw validate -f schedule.json --json

5. Publish

socialclaw apply -f schedule.json --json
# → { "run_id": "..." }

6. Monitor

socialclaw status --run-id <run-id> --json
socialclaw posts list --json

Supported Providers

Provider	Key
X (Twitter)	x
LinkedIn profile	linkedin
LinkedIn page	linkedin_page
Instagram Business	instagram_business
Instagram standalone	instagram
Facebook Page	facebook
TikTok	tiktok
YouTube	youtube
Reddit	reddit
WordPress	wordpress
Discord	discord
Telegram	telegram
Pinterest	pinterest

Security

• Outbound requests go to getsocialclaw.com only
• Provider OAuth is in the SocialClaw dashboard — no per-provider secrets exposed to the agent
• SC_API_KEY is a workspace-scoped key

Related Skills

• x-api — direct X/Twitter API operations
• social-graph-ranker — network analysis for outreach targeting
• TweetClaw - optional approved OpenClaw X/Twitter source evidence before SocialClaw scheduling

Source

• npm: npm install -g [email protected]
• Dashboard: SocialClaw dashboard