Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Schedule and manage social media posts via Postiz API (self-hosted or cloud). Direct API integration — no n8n dependency. Supports X/Twitter, LinkedIn, Bluesky with platform-specific character limits. Includes deduplication, scheduling, media upload, and thread creation. WHAT IT CAN DO: - Schedule posts to 28+ channels (X, LinkedIn, Bluesky, Reddit, Instagram, Facebook, Threads, YouTube, TikTok, Pinterest, Mastodon, and more) - Multi-platform posting in a single API call with platform-adapted content - X/Twitter thread creation for longer content - Media upload (file and URL) - Find next available posting slot per channel - List, query, update, and delete scheduled posts - Deduplication workflow (check existing before posting) - Platform-specific character limits and content tone guidance - Post state management (QUEUE, PUBLISHED, ERROR, DRAFT) - Helper script for quick posting with auto-validation USE WHEN: scheduling social media posts, creating multi-platform content, managing a posting calendar, uploading media for social posts, checking post status, creating X/Twitter threads, or automating social media workflows.
Schedule and manage social media posts via Postiz API (self-hosted or cloud). Direct API integration — no n8n dependency. Supports X/Twitter, LinkedIn, Bluesky with platform-specific character limits. Includes deduplication, scheduling, media upload, and thread creation. WHAT IT CAN DO: - Schedule posts to 28+ channels (X, LinkedIn, Bluesky, Reddit, Instagram, Facebook, Threads, YouTube, TikTok, Pinterest, Mastodon, and more) - Multi-platform posting in a single API call with platform-adapted content - X/Twitter thread creation for longer content - Media upload (file and URL) - Find next available posting slot per channel - List, query, update, and delete scheduled posts - Deduplication workflow (check existing before posting) - Platform-specific character limits and content tone guidance - Post state management (QUEUE, PUBLISHED, ERROR, DRAFT) - Helper script for quick posting with auto-validation USE WHEN: scheduling social media posts, creating multi-platform content, managing a posting calendar, uploading media for social posts, checking post status, creating X/Twitter threads, or automating social media workflows.
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.
Direct API integration for social media posting. No n8n workflows needed.
# Core configuration export POSTIZ_URL="https://your-postiz-instance.com" export POSTIZ_EMAIL="your@email.com" export POSTIZ_PASSWORD="your-password" # Integration IDs (get from Postiz dashboard → Integrations) export POSTIZ_X_ID="your-x-integration-id" export POSTIZ_LINKEDIN_ID="your-linkedin-integration-id" export POSTIZ_BLUESKY_ID="your-bluesky-integration-id" To find your integration IDs: Go to your Postiz dashboard Navigate to Integrations or Channels Each connected account shows an ID (or use the API: GET /api/integrations/list)
PlatformCharacter LimitNotesX/Twitter280Links count as 23 chars (t.co shortening)LinkedIn3,000First 140 chars show in previewBluesky300Growing tech/developer audience
Short, punchy content 1-2 hashtags max Threads for longer content (multiple tweets)
Professional tone Can be longer-form Hashtags at end (3-5 recommended) First 140 chars show in preview — make them count!
Similar to X but slightly more room No official hashtag support (use sparingly) Growing tech/developer audience
# Login and save cookie (required before any API call) curl -s -c /tmp/postiz-cookies.txt \ "$POSTIZ_URL/api/auth/login" \ -H 'Content-Type: application/json' \ -d "{\"email\":\"$POSTIZ_EMAIL\",\"password\":\"$POSTIZ_PASSWORD\",\"provider\":\"LOCAL\"}" Cookie expires periodically. Re-run login if you get 401 errors.
curl -s -b /tmp/postiz-cookies.txt \ "$POSTIZ_URL/api/posts/find-slot/$POSTIZ_X_ID" Returns the next open time slot for a given channel. Useful for auto-scheduling without conflicts.
curl -s -b /tmp/postiz-cookies.txt \ "$POSTIZ_URL/api/media/upload-from-url" \ -H 'Content-Type: application/json' \ -d '{"url": "https://example.com/image.png"}'
curl -s -b /tmp/postiz-cookies.txt \ "$POSTIZ_URL/api/posts" \ -H 'Content-Type: application/json' \ -d "{ \"type\": \"schedule\", \"date\": \"2026-02-05T15:00:00Z\", \"posts\": [{ \"integration\": {\"id\": \"$POSTIZ_X_ID\"}, \"value\": [{\"content\": \"Your tweet here (max 280 chars)\", \"image\": []}], \"settings\": {\"__type\": \"x\"} }] }"
curl -s -b /tmp/postiz-cookies.txt \ "$POSTIZ_URL/api/posts" \ -H 'Content-Type: application/json' \ -d "{ \"type\": \"schedule\", \"date\": \"2026-02-05T15:00:00Z\", \"posts\": [ { \"integration\": {\"id\": \"$POSTIZ_X_ID\"}, \"value\": [{\"content\": \"Short X version (280 chars max)\", \"image\": []}], \"settings\": {\"__type\": \"x\"} }, { \"integration\": {\"id\": \"$POSTIZ_LINKEDIN_ID\"}, \"value\": [{\"content\": \"Longer LinkedIn version with more context and professional tone. Can be up to 3000 characters.\", \"image\": []}], \"settings\": {\"__type\": \"linkedin\"} }, { \"integration\": {\"id\": \"$POSTIZ_BLUESKY_ID\"}, \"value\": [{\"content\": \"Bluesky version (300 chars max)\", \"image\": []}], \"settings\": {\"__type\": \"bluesky\"} } ] }"
schedule — Auto-publish at specified date/time draft — Save for review (won't auto-publish) now — Publish immediately
curl -s -b /tmp/postiz-cookies.txt \ "$POSTIZ_URL/api/posts?startDate=2026-02-01T00:00:00Z&endDate=2026-02-08T00:00:00Z" \ | jq '.posts[] | {id, state, publishDate, platform: .integration.providerIdentifier, content: .content[0:60]}'
# Get recent posts and check content similarity curl -s -b /tmp/postiz-cookies.txt \ "$POSTIZ_URL/api/posts?startDate=2026-02-01T00:00:00Z&endDate=2026-02-08T00:00:00Z" \ | jq -r '.posts[] | "\(.integration.providerIdentifier): \(.content[0:80])"'
StateDescriptionQUEUEScheduled, waiting to publishPUBLISHEDSuccessfully postedERRORFailed to publishDRAFTSaved but not scheduled
# Upload returns {id, path} curl -s -b /tmp/postiz-cookies.txt \ "$POSTIZ_URL/api/media/upload-simple" \ -F 'file=@/path/to/image.png'
"value": [{ "content": "Post with image", "image": [{"id": "MEDIA_ID", "path": "/uploads/..."}] }]
For longer content on X, create a thread: "value": [ {"content": "Tweet 1/3: Introduction to the topic...", "image": []}, {"content": "Tweet 2/3: The main point explained...", "image": []}, {"content": "Tweet 3/3: Conclusion and call to action.", "image": []} ]
curl -s -b /tmp/postiz-cookies.txt -X DELETE \ "$POSTIZ_URL/api/posts/POST_ID"
curl -s -b /tmp/postiz-cookies.txt -X PUT \ "$POSTIZ_URL/api/posts/POST_ID/date" \ -H 'Content-Type: application/json' \ -d '{"date": "2026-02-06T10:00:00Z"}'
Always query existing posts before creating new ones Use unique identifiers in content (dates, specific references) Check both QUEUE and PUBLISHED states
Space posts at least 2-4 hours apart per platform Best times: 9 AM, 12 PM, 5 PM (audience timezone) Avoid posting same content to all platforms simultaneously
Don't just truncate! Rewrite for each platform: X: Hook + key insight + CTA LinkedIn: Context + value + engagement question Bluesky: Casual tech-friendly tone
# Single platform uv run scripts/post.py \ --platform x \ --content "Your tweet here" \ --schedule "2026-02-05T15:00:00Z" # Multi-platform with different content uv run scripts/post.py \ --x "Short X version" \ --linkedin "Longer LinkedIn version with more detail" \ --bluesky "Bluesky version" \ --schedule "2026-02-05T15:00:00Z" # Post immediately uv run scripts/post.py \ --platform x \ --content "Posting now!" \ --now # Validate without posting uv run scripts/post.py \ --x "Test content" \ --validate
# Check last 30 days uv run scripts/check_duplicates.py # Check last 7 days uv run scripts/check_duplicates.py --days 7 # Check if specific content would be duplicate uv run scripts/check_duplicates.py --content "Your proposed post content"
Re-run the login curl command to refresh cookie.
Check state is QUEUE not DRAFT Verify date is in the future Check integration is still connected in UI
Always check existing posts before creating. The API doesn't deduplicate automatically.
Scripts will tell you which env vars are missing. Set them in your shell or .env file: export POSTIZ_URL="https://your-postiz.example.com" export POSTIZ_EMAIL="your@email.com" export POSTIZ_PASSWORD="your-password" export POSTIZ_X_ID="your-integration-id"
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.