AGENT SKILL

social-publishing

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.

License 许可
MIT
最近更新
2026-09-11
Stars
★ 0
Forks
0

01 前言 Front Matter

license
MIT
metadata
{ "source": "https://github.com/ndesv21/socialclaw", "version": "1.0.0", "homepage": "https://getsocialclaw.com" }
description
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.

03 SKILL.md 正文

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

  1. One key, all platforms — SOCIALCLAW_API_KEY authenticates across all connected accounts
  2. Platform-native copy — Adapt tone and format for each platform rather than copy-pasting
  3. Validate timing — Always confirm schedule before submission to avoid rate limit errors
  4. 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)

04 同仓库更多 Skills

NeelakshSaxena
NeelakshSaxena/Vayu

runpodctl

Runpod CLI for managing GPU/CPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send/receive). Use for terminal/CI/scripting, Hub browse/deploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod

Start here for any Runpod task — running GPU/CPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-usage

How Runpod works and how to work it — pods vs serverless, GPU/VRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv/apt). Use to answer "how does X work", "which GPU", "how do I build a container", or "how do I stand up a workload on a pod". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-templates

Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says "run <X> on a pod" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-migrate

Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-mcp

Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU/CPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.

★ 0