social-publishing

wshobson/agents · plugins/social-publishing/skills/social-publishing/SKILL.md

Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API. Use when the user wants to publish, schedule, or manage social media content programmatically. Requires SOCIALCLAW_API_KEY.

Software EngineeringMIT★ 39156⑂ 4179commit 38e19c2

Install skillView source on GitHub

What this skill does

Social Publishing

Agent-first social media publishing via SocialClaw. One workspace API key, 13 platforms, zero per-platform OAuth setup.

When to Use This Skill

Use this skill when the user wants to:

Publish or schedule posts across multiple social media platforms
Orchestrate a multi-platform content campaign
Upload and attach media to social posts
Retrieve post-level engagement analytics
Manage a content calendar programmatically

Supported Platforms

| Platform | Notes | |----------|-------| | X (Twitter) | Profile posts, threads | | LinkedIn | Profile posts + Company pages | | Instagram | Business + standalone accounts | | Facebook Pages | Page posts with link previews | | TikTok | Video descriptions | | Discord | Channel targeting, embeds | | Telegram | Channel/group messaging | | YouTube | Video descriptions and metadata | | Reddit | Subreddit posts with flair | | WordPress | Blog posts with SEO metadata | | Pinterest | Pins with board targeting |

Setup

# Install via npx
npx skills add ndesv21/socialclaw

# Or install as package
npm install socialclaw@0.1.12

# Set your workspace API key
export SOCIALCLAW_API_KEY=your_key_here

Get a workspace API key at getsocialclaw.com.

Workflow

Step 1: Define Campaign

Specify platforms, message content, schedule, and any media attachments.

Step 2: Draft Platform Variants

Claude generates platform-optimized copy for each channel (character limits, hashtag norms, tone).

Step 3: Upload Media (Optional)

Upload images or videos once — SocialClaw stores them for reuse across platforms.

Step 4: Validate Schedule

Claude checks platform-specific timing rules and rate limits before submitting.

Step 5: Publish or Schedule

Posts queue via the SocialClaw API. Receive post IDs and scheduled times for confirmation.

Step 6: Analytics

Pull engagement metrics (impressions, clicks, reactions) 24–48 hours after publishing.

Usage Examples

Single Platform Post

Post to our company LinkedIn page:
"Excited to announce our Q2 product roadmap — here's what's coming next.
[roadmap image]"

Multi-Platform Campaign

Announce our beta launch on X, LinkedIn, Instagram, and Discord.
Message: "Our beta is live! 100 spots available — sign up at example.com #launch"
Schedule for tomorrow 9am PST

Content Series

Create a 5-day drip campaign for our feature launch week.
Platforms: X and LinkedIn.
I'll provide copy for each day.

Guidelines

One key, all platforms — SOCIALCLAW_API_KEY authenticates across all connected accounts
Platform-native copy — Adapt tone and format for each platform rather than copy-pasting
Validate timing — Always confirm schedule before submission to avoid rate limit errors
Media reuse — Upload assets once and reference by ID across multiple posts

Limitations

Requires active SocialClaw account with connected social accounts
Platform availability depends on workspace tier
Some platforms require video content for optimal reach (TikTok, YouTube, Instagram Reels)

Installation

Copy a source-pinned command for your client. You run it yourself.

Destination: .claude/skills/social-publishing · pinned to the source commit

# Run from your project root
git clone https://github.com/wshobson/agents.git .skillboard-tmp
git -C .skillboard-tmp checkout 38e19c20d2b154510b0e624a2e3e186b19b5c527
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/plugins/social-publishing/skills/social-publishing" ".claude/skills/"
rm -rf .skillboard-tmp

Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.

New here? Step-by-step setup – from installing the agent to using the skill

Operating systemAgentI already use Claude Code

1
Install Git
Install Git with your package manager (Debian/Ubuntu shown; use dnf/pacman on others). Official download.
```
sudo apt update && sudo apt install -y git
```
2
Install Claude Code
Requires Node.js 18+. Install the CLI globally: Official docs. (command-line tool)
```
npm install -g @anthropic-ai/claude-code
```

Get the skill, pinned to its exact version

Open a terminal and run these steps (they clone the source, check out the exact commit, and copy the skill into place):

# Run from your project root
git clone https://github.com/wshobson/agents.git .skillboard-tmp
git -C .skillboard-tmp checkout 38e19c20d2b154510b0e624a2e3e186b19b5c527
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/plugins/social-publishing/skills/social-publishing" ".claude/skills/"
rm -rf .skillboard-tmp

Destination: .claude/skills/social-publishing

4
Use it in Claude Code
Open Claude Code in your project. It reads skills from the folder above, so social-publishing is now available. Always review the source before using it – static checks cannot prove runtime safety.

Security & Audits

Scanner static-checks@0.1.0 · commit 38e19c20d2b1. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.

highCredential or secret access
References credentials, tokens or secret files that a skill should not need.
Evidence: [redacted]· fingerprint ccae6d912a41bfef
mediumShell or process execution
Instructs shell/process/package operations that run commands on the host.
Evidence: npm install· fingerprint 3a2dc0ae21eb56d7

social-publishing

wshobson/agents · plugins/social-publishing/skills/social-publishing/SKILL.md

Software EngineeringMIT★ 39156⑂ 4179commit 38e19c2

Install skillView source on GitHub

What this skill does

Social Publishing

Agent-first social media publishing via SocialClaw. One workspace API key, 13 platforms, zero per-platform OAuth setup.

When to Use This Skill

Use this skill when the user wants to:

Publish or schedule posts across multiple social media platforms
Orchestrate a multi-platform content campaign
Upload and attach media to social posts
Retrieve post-level engagement analytics
Manage a content calendar programmatically

Supported Platforms

Setup

# Install via npx
npx skills add ndesv21/socialclaw

# Or install as package
npm install socialclaw@0.1.12

# Set your workspace API key
export SOCIALCLAW_API_KEY=your_key_here

Get a workspace API key at getsocialclaw.com.

Workflow

Step 1: Define Campaign

Specify platforms, message content, schedule, and any media attachments.

Step 2: Draft Platform Variants

Claude generates platform-optimized copy for each channel (character limits, hashtag norms, tone).

Step 3: Upload Media (Optional)

Upload images or videos once — SocialClaw stores them for reuse across platforms.

Step 4: Validate Schedule

Claude checks platform-specific timing rules and rate limits before submitting.

Step 5: Publish or Schedule

Posts queue via the SocialClaw API. Receive post IDs and scheduled times for confirmation.

Step 6: Analytics

Pull engagement metrics (impressions, clicks, reactions) 24–48 hours after publishing.

Usage Examples

Single Platform Post

Post to our company LinkedIn page:
"Excited to announce our Q2 product roadmap — here's what's coming next.
[roadmap image]"

Multi-Platform Campaign

Announce our beta launch on X, LinkedIn, Instagram, and Discord.
Message: "Our beta is live! 100 spots available — sign up at example.com #launch"
Schedule for tomorrow 9am PST

Content Series

Create a 5-day drip campaign for our feature launch week.
Platforms: X and LinkedIn.
I'll provide copy for each day.

Guidelines

One key, all platforms — SOCIALCLAW_API_KEY authenticates across all connected accounts
Platform-native copy — Adapt tone and format for each platform rather than copy-pasting
Validate timing — Always confirm schedule before submission to avoid rate limit errors
Media reuse — Upload assets once and reference by ID across multiple posts

Limitations

Requires active SocialClaw account with connected social accounts
Platform availability depends on workspace tier
Some platforms require video content for optimal reach (TikTok, YouTube, Instagram Reels)

Installation

Copy a source-pinned command for your client. You run it yourself.

Destination: .claude/skills/social-publishing · pinned to the source commit

# Run from your project root
git clone https://github.com/wshobson/agents.git .skillboard-tmp
git -C .skillboard-tmp checkout 38e19c20d2b154510b0e624a2e3e186b19b5c527
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/plugins/social-publishing/skills/social-publishing" ".claude/skills/"
rm -rf .skillboard-tmp

Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.

New here? Step-by-step setup – from installing the agent to using the skill

Operating systemAgentI already use Claude Code

1
Install Git
Install Git with your package manager (Debian/Ubuntu shown; use dnf/pacman on others). Official download.
```
sudo apt update && sudo apt install -y git
```
2
Install Claude Code
Requires Node.js 18+. Install the CLI globally: Official docs. (command-line tool)
```
npm install -g @anthropic-ai/claude-code
```

Get the skill, pinned to its exact version

Open a terminal and run these steps (they clone the source, check out the exact commit, and copy the skill into place):

# Run from your project root
git clone https://github.com/wshobson/agents.git .skillboard-tmp
git -C .skillboard-tmp checkout 38e19c20d2b154510b0e624a2e3e186b19b5c527
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/plugins/social-publishing/skills/social-publishing" ".claude/skills/"
rm -rf .skillboard-tmp

Destination: .claude/skills/social-publishing

4
Use it in Claude Code
Open Claude Code in your project. It reads skills from the folder above, so social-publishing is now available. Always review the source before using it – static checks cannot prove runtime safety.

Security & Audits

Scanner static-checks@0.1.0 · commit 38e19c20d2b1. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.

highCredential or secret access
References credentials, tokens or secret files that a skill should not need.
Evidence: [redacted]· fingerprint ccae6d912a41bfef
mediumShell or process execution
Instructs shell/process/package operations that run commands on the host.
Evidence: npm install· fingerprint 3a2dc0ae21eb56d7

social-publishing

What this skill does

Social Publishing

When to Use This Skill

Supported Platforms

Setup

Workflow

Step 1: Define Campaign

Step 2: Draft Platform Variants

Step 3: Upload Media (Optional)

Step 4: Validate Schedule

Step 5: Publish or Schedule

Step 6: Analytics

Usage Examples

Single Platform Post

Multi-Platform Campaign

Content Series

Guidelines

Limitations

Installation

Install Git

Install Claude Code

Get the skill, pinned to its exact version

Use it in Claude Code

Security & Audits

social-publishing

What this skill does

Social Publishing

When to Use This Skill

Supported Platforms

Setup

Workflow

Step 1: Define Campaign

Step 2: Draft Platform Variants

Step 3: Upload Media (Optional)

Step 4: Validate Schedule

Step 5: Publish or Schedule

Step 6: Analytics

Usage Examples

Single Platform Post

Multi-Platform Campaign

Content Series

Guidelines

Limitations

Installation

Install Git

Install Claude Code

Get the skill, pinned to its exact version

Use it in Claude Code

Security & Audits