Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
AI-powered social media publishing for LinkedIn and X (Twitter) with algorithm optimization and scheduling.
AI-powered social media publishing for LinkedIn and X (Twitter) with algorithm optimization and scheduling.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
ClawPost helps you create, manage, and publish content to LinkedIn and X (Twitter) β with AI-assisted writing, drafts, scheduling, and direct publishing via API.
If the user doesn't have an account or API key yet, walk them through these steps: Sign up at clawpost.dev β sign in with LinkedIn. Connect platforms β In the Dashboard, connect LinkedIn and/or X (Twitter) accounts. Add credits β Go to Dashboard β Billing and top up credits (minimum $5). Credits are used for AI generation features. Generate an API key β Go to Dashboard β Settings β API Keys β Generate New Key. The key starts with claw_. Set the environment variable: export CLAW_API_KEY="claw_your_key_here"
Required environment variable: CLAW_API_KEY β your API key (starts with claw_). Generate one following the steps above. Optional: CLAW_API_URL β defaults to https://clawpost.dev. Only set this if using a self-hosted instance. All endpoints are under {{CLAW_API_URL}}/api/claw/v1/ (default: https://clawpost.dev/api/claw/v1/).
Every request needs the header: Authorization: Bearer {{CLAW_API_KEY}}
When sending JSON data with curl, always use a heredoc to avoid shell escaping issues with quotes and special characters: curl -s -X POST URL \ -H "Authorization: Bearer {{CLAW_API_KEY}}" \ -H "Content-Type: application/json" \ -d @- <<'EOF' {"key": "value"} EOF All examples below use this pattern. Do not use -d '{...}' with single quotes β it breaks when content contains quotes, newlines, or special characters.
All responses follow this shape: { "success": true, "message": "Human-readable summary", "data": { ... }, "error": { "code": "ERROR_CODE", "details": "..." } } Always read the message field β it's designed to be relayed directly to the user.
Verify your API key works and see what's connected. curl -s {{CLAW_API_URL}}/api/claw/v1/status \ -H "Authorization: Bearer {{CLAW_API_KEY}}"
curl -s {{CLAW_API_URL}}/api/claw/v1/platforms \ -H "Authorization: Bearer {{CLAW_API_KEY}}"
curl -s {{CLAW_API_URL}}/api/claw/v1/credits \ -H "Authorization: Bearer {{CLAW_API_KEY}}"
Filter by status (draft, published, scheduled, failed) and platform (linkedin, twitter). curl -s "{{CLAW_API_URL}}/api/claw/v1/posts?status=draft&platform=linkedin&limit=10" \ -H "Authorization: Bearer {{CLAW_API_KEY}}"
Retrieve your X (Twitter) post history from the cached profile data. This is a read-only endpoint - no credits are used. Query parameters: type - posts, replies, or all (default: all) limit - max results, 1-100 (default: 20) period - 7d, 30d, 90d, or all (default: all) curl -s "{{CLAW_API_URL}}/api/claw/v1/history/x?type=posts&period=30d&limit=10" \ -H "Authorization: Bearer {{CLAW_API_KEY}}" The response includes a summary object with aggregated metrics (totalPosts, totalReplies, totalLikes, totalRetweets, totalRepliesReceived, totalImpressions, topPost) and a posts array with individual tweet details, metrics, media, and reply context.
curl -s {{CLAW_API_URL}}/api/claw/v1/posts/POST_ID \ -H "Authorization: Bearer {{CLAW_API_KEY}}" Each post includes an availableActions array (e.g., ["publish", "schedule", "update", "delete"]). Post Object Fields Every post includes a postType field: "original" β a regular post composed by the user "quote" β a quote tweet of another post (X only) "reply" β a reply to another post (X only) "remix" β an original tweet inspired by another post (X only) When postType is "quote", "reply", or "remix", the post also includes a reference object with the original tweet's context: { "postType": "quote", "content": "User's commentary text", "reference": { "tweetId": "1234567890", "text": "The original tweet text that was quoted", "author": "originalAuthor" } } This lets you see exactly what was quoted/replied to alongside the user's own text.
curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/drafts \ -H "Authorization: Bearer {{CLAW_API_KEY}}" \ -H "Content-Type: application/json" \ -d @- <<'EOF' {"content": "Your post text here", "platform": "linkedin"} EOF Platform: "linkedin" or "twitter". Twitter content must be β€ 280 characters.
curl -s -X PUT {{CLAW_API_URL}}/api/claw/v1/posts/POST_ID \ -H "Authorization: Bearer {{CLAW_API_KEY}}" \ -H "Content-Type: application/json" \ -d @- <<'EOF' {"content": "Updated post text"} EOF
curl -s -X DELETE {{CLAW_API_URL}}/api/claw/v1/posts/POST_ID \ -H "Authorization: Bearer {{CLAW_API_KEY}}"
curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/posts/POST_ID/publish \ -H "Authorization: Bearer {{CLAW_API_KEY}}"
curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/publish \ -H "Authorization: Bearer {{CLAW_API_KEY}}" \ -H "Content-Type: application/json" \ -d @- <<'EOF' {"content": "Publishing this directly!", "platform": "linkedin"} EOF
curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/posts/POST_ID/schedule \ -H "Authorization: Bearer {{CLAW_API_KEY}}" \ -H "Content-Type: application/json" \ -d @- <<'EOF' {"scheduledAt": "2026-06-15T10:00:00Z"} EOF
curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/schedule \ -H "Authorization: Bearer {{CLAW_API_KEY}}" \ -H "Content-Type: application/json" \ -d @- <<'EOF' {"content": "Scheduled post!", "platform": "linkedin", "scheduledAt": "2026-06-15T10:00:00Z"} EOF
Let AI write a post based on your prompt. Optional: tone and platform. curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/ai/generate \ -H "Authorization: Bearer {{CLAW_API_KEY}}" \ -H "Content-Type: application/json" \ -d @- <<'EOF' {"prompt": "Write about the importance of code reviews", "platform": "linkedin"} EOF
Improve existing content with instructions. curl -s -X POST {{CLAW_API_URL}}/api/claw/v1/ai/refine \ -H "Authorization: Bearer {{CLAW_API_KEY}}" \ -H "Content-Type: application/json" \ -d @- <<'EOF' {"content": "Original post text...", "instructions": "Make it shorter and punchier", "platform": "linkedin"} EOF
Quick publish: Use /publish to post immediately without creating a draft. Review flow: Create a draft with /drafts, refine with /ai/refine, then publish with /posts/ID/publish. Cross-post: Make separate calls for LinkedIn and Twitter β each is a separate post. Check before publishing: Call /platforms to verify the target platform is connected. Twitter limit: Tweets must be β€ 280 characters. The API will reject longer content with a clear message.
CodeMeaningUNAUTHORIZEDInvalid or revoked API keyNOT_FOUNDPost or resource doesn't existVALIDATION_ERRORBad input (missing content, too long, invalid date)CONFLICTCan't perform action (e.g., already published)PLATFORM_NOT_CONNECTEDTarget social platform isn't linkedINSUFFICIENT_CREDITSNot enough credits for AI operationsNO_AI_KEYNo AI API key configuredRATE_LIMITEDToo many requests (60/min general, 10/min publish)INTERNAL_ERRORSomething went wrong server-side
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.