Skip to content
Skills Library
Marketing & content · Automation

planpost

/planpost

Draft, schedule and publish social media posts through PlanPost, the agentic social scheduler with revenue attribution, and report what they earned. Use when the user wants to post, schedule, queue, repurpose or bulk-plan content for Instagram, TikTok, LinkedIn, X (Twitter), Facebook, Threads or YouTube, render a carousel or video for a post, check a post's status or a failed publish, or ask which posts drove clicks, signups or revenue. Requires the PlanPost MCP server (https://mcp.planpo.st/mcp).

Author
lukBB ↗
Licence
MIT
Last repository change
09.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Draft, schedule and publish social media posts through PlanPost, the agentic social scheduler with revenue attribution, and report what they earned. Use when the user wants to post, schedule, queue, repurpose or bulk-plan content for Instagram, TikTok, LinkedIn, X (Twitter), Facebook, Threads or YouTube, render a carousel or video for a post, check a post's status or a failed publish, or ask which posts drove clicks, signups or revenue. Requires the PlanPost MCP server (https://mcp.planpo.st/mcp).

Original author description

Draft, schedule and publish social media posts through PlanPost, the agentic social scheduler with revenue attribution, and report what they earned. Use when the user wants to post, schedule, queue, repurpose or bulk-plan content for Instagram, TikTok, LinkedIn, X (Twitter), Facebook, Threads or YouTube, render a carousel or video for a post, check a post's status or a failed publish, or ask which posts drove clicks, signups or revenue. Requires the PlanPost MCP server (https://mcp.planpo.st/mcp).

How it works

  1. Before anything else
  2. The rules that prevent bad posts
  3. Common jobs
  4. Limits to respect
Original SKILL.md headings · 108 lines, 697 words
SKILL.md preview
---
name: planpost
description: Draft, schedule and publish social media posts through PlanPost, the agentic social scheduler with revenue attribution, and report what they earned. Use when the user wants to post, schedule, queue, repurpose or bulk-plan content for Instagram, TikTok, LinkedIn, X (Twitter), Facebook, Threads or YouTube, render a carousel or video for a post, check a post's status or a failed publish, or ask which posts drove clicks, signups or revenue. Requires the PlanPost MCP server (https://mcp.planpo.st/mcp).
license: MIT
metadata:
  homepage: https://planpo.st/mcp
---

# PlanPost

PlanPost schedules and publishes to seven social networks and attributes
revenue back to individual posts. This skill is the operating manual for its
MCP tools. Tool names below are the ones the server exposes; your client may
prefix them (for example `mcp__planpost__create_post`).

## Before anything else

If no PlanPost tools are available, the server is not connected. Tell the user
to add `https://mcp.planpo.st/mcp` as a remote MCP server (connector) in their
agent and sign in when the browser opens. Details per client:
https://planpo.st/docs/agents. Do not ask the user to paste an API key into
the chat.

## The rules that prevent bad posts

1. **Resolve targets, never guess them.** Call `list_account_groups` (named
   sets such as "Agency clients") or `list_connections` and use the IDs they
   return. If the user names a group or handle you cannot find, show what
   exists and ask.
2. **Draft unless told otherwise.** `create_post` with no `scheduledFor` saves
   a draft. Schedule only when the user gave a time, and publish immediately
   (`publish_post`) only when they said "now" in so many words.
3. **Say the time back.** Pass `scheduledFor` as ISO 8601 plus the user's
   `timezone`, and repeat the local time in your answer. If they gave no time
   and want one, `suggest_schedule` or `get_best_times` picks it.
4. **Approval is not a failure.** A post that comes back `needs_approval` is
   waiting for the account owner in PlanPost. Report that and stop; do not
   retry or re-create it. `get_approval_status` tells you when it clears.
5. **Read warnings.** Responses carry `warnings[]` (what will be truncated or
   dropped at publish time) and sometimes `preflight.errors[]` (the post was
   saved as a draft because it would fail). Fix what they name, then
   `update_post`.
6. **X (Twitter) takes no links.** No URL, bare domain or t.co in the post,
   any thread segment, or the first comment. Put a link-free variant in
   `platformContent.twitter`.
7. **TikTok needs a visibility choice.** A scheduled or published TikTok post
   must carry `platformSettings.tiktok.privacyLevel`. Ask the user if they
   have not said.

## Common jobs

**Post one thing to several networks**

1. `list_account_groups` → pick the group, or `list_connections` → pick IDs.
2. `preview_post` with the text to see per-network length and media problems.
3. `create_post` with `content`, `connectionIds`, optional
   `platformContent` overrides and `scheduledFor`.
4. Give the user the status and the `Open in PlanPost` link from the response.

**Plan a week or a campaign**

Use `bulk_create_posts` with one manifest instead of looping `create_post`.
Give every post the same `campaign` so `list_posts` and `list_campaigns` can
find them again. To fill the user's standing queue instead of picking times,
read `get_posting_schedule` first.

**Attach media**

Reuse before uploading: `list_media` shows what is already in the library.
For a new file, `upload_media` returns a presigned URL; upload to it, then
pass the returned asset in `media`.

**Carousel**

`generate_carousel` (slide text) → `list_carousel_styles` or
`list_brand_kits` → `render_carousel` → poll `get_carousel_render` until
`completed` → `create_post` with the returned `assets` as `media`.

**Video**

`list_video_templates` → `create_video` → poll `get_video_status` →
`create_post` with `postType: "reel"` or `"short"`.

**Turn an article into posts**

`list_content_sources` → `fetch_source_content` → `list_imported_content` →
write per-network variants (use `get_brand_voice_prompt` when a brand voice
exists) → `create_post` as drafts.

**A post failed**

`get_post` → read `platformResults[]`: `errorClass`, `error`, `fix`.
`retry_failed` re-queues only transient failures and never re-posts a network
that already went out. Failures that need the user (reconnect an account,
choose TikTok visibility) come back with the fix to relay.

**What worked?**

`get_analytics` for reach and engagement, `get_revenue_overview` for revenue,
signups and clicks attributed to posts. Lead with the posts that earned
money, not the ones with the most likes.

## Limits to respect

- Calls count against the user's monthly API allowance; prefer one
  `bulk_create_posts` over many `create_post` calls, and do not poll render
  status faster than every few seconds.
- A tool that answers with a missing-permission error means the user did not
  grant that scope. Say which capability is missing; do not look for a
  workaround.
- Image, video and carousel generation spend the user's AI credits or render
  quota. Confirm before generating more than a couple.
- Connecting a new social account needs a human in a browser:
  `get_connection_link` returns the link to send them.

Versions

The database has no other skills named planpost.

Database snapshot: 13.11.2026 · package version eab7dee62e3a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100send-to-plan-post
    Compose and route social posts through the user's PlanPost app. Resolves named account groups ("Polish Pages", "English Pages", "SaaS", "Personal", etc.) into PlanPost connection IDs and creates draft, scheduled, or immediately-published posts. MANDATORY TRIGGERS - "send to plan…
  • 100sendcove
    Draft, schedule and publish social media posts, upload media, check engagement and best times to post, and answer inbox comments with the Sendcove MCP server (X, Instagram, TikTok, Threads, Bluesky, YouTube, Facebook Pages, LinkedIn). Use when the user asks to write, schedule,…
  • 100schedule-posts
    Schedule and publish social media posts through PostFast, with the user's approval before anything goes out. Use when someone wants to post or schedule something on X, Instagram, Facebook, TikTok, LinkedIn, YouTube, Threads, Pinterest, Bluesky, Telegram or Google Business…
  • 1001social
    Publish and schedule social media posts to Instagram, TikTok, X (Twitter), Threads, LinkedIn, Facebook Pages, YouTube Shorts and Bluesky from OpenClaw, Hermes, Claude Code or Codex. One post adapted to each network's limits, cross-posted now or scheduled up to 30 days ahead,…
  • 90solmarrow-social
    Draft, schedule and check social media posts across 19 networks through the SolMarrow MCP server. Use when the user wants to plan, write, schedule or review posts for X, LinkedIn, Facebook, Instagram, Threads, Bluesky, TikTok, YouTube, Pinterest, Telegram, Discord and more.
  • 90schedule-social-posts
    Draft, approve and schedule social media posts through the TimeToPost MCP server. Use when the user says "schedule a post", "draft a tweet", "queue posts for the week", "post this to X and Instagram", "write a thread", "what's in my approval queue", "approve that draft", "when…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.