Update to Publora

{
  "name": "publora-publishing",
  "description": "Publish or schedule a post to connected social accounts through Publora — LinkedIn, X, Instagram, Threads, TikTok, YouTube, Facebook, Bluesky, Mastodon, Telegram. Use for drafting, scheduling, editing the queue and checking what is already queued. Not for analytics; Publora does not expose metrics here.",
  "included_files": [],
  "skill_md_contents": "---\nname: publora-publishing\ndescription: >\n  Publish or schedule a post to connected social accounts through Publora —\n  LinkedIn, X, Instagram, Threads, TikTok, YouTube, Facebook, Bluesky,\n  Mastodon, Telegram. Use for drafting, scheduling, editing the queue and\n  checking what is already queued. Not for analytics; Publora does not\n  expose metrics here.\n---\n\n# Publishing with Publora\n\nOne post, several networks, one set of rules. This skill covers the whole\npublishing path: read what is connected, respect each network's limits, save a\ndraft or schedule, then confirm what actually happened.\n\nPublishing is public and effectively irreversible. Show the user the exact text\nand the exact accounts before anything goes out, and never publish on a guess.\n\n## Always start with the connections\n\n```\nlist_connections\n```\n\nCopy each target's `platformId` **verbatim** into the next call. Never invent,\nshorten or guess an id — a wrong id is the most common reason a post silently\ngoes nowhere. If the network the user asked for is not in the list, say so and\nstop: connecting an account is done by the user in the Publora dashboard, not\nby a tool.\n\nPinterest can be connected but cannot be published to.\n\n## Draft, schedule or publish\n\n`create_post` does all three, and the difference is one field:\n\n| Intent | Call |\n|---|---|\n| Draft, to finish later | `create_post` **without** `scheduledTime` |\n| Scheduled | `create_post` with `scheduledTime` |\n| Right now | `create_post` with a `scheduledTime` a few minutes ahead |\n\nTimes are ISO 8601 in UTC, for example `2026-08-12T09:00:00Z`. When the user\nsays \"tomorrow at 9\", convert from their timezone and state the conversion back\nto them. Read the `scheduledTime` in the response rather than repeating the\nrequested one: the server may adjust it and explain why in `warnings`.\n\nDefault to a draft when the request is ambiguous. A draft that needed to be a\npost costs one click; a post that needed to be a draft cannot be recalled.\n\n## Per-network limits\n\nPublora validates these, but knowing them avoids a failed call:\n\n| Network | Caption limit | Media |\n|---|---|---|\n| X | 280 | optional |\n| Threads, Mastodon | 500 | optional |\n| Instagram, TikTok | 2200 | **required** |\n| YouTube | 5000 | **required** |\n| LinkedIn | 3000 | optional |\n| Facebook, Bluesky, Telegram | generous | optional |\n\nWhen one post targets several networks, the strictest limit wins. If the text\nis too long for one of them, offer to shorten it or to drop that network —\ndo not silently truncate.\n\nInstagram, TikTok and YouTube reject a text-only post. Attach media or leave\nthem out; see the `publora-media` skill for how.\n\nNetwork-specific options — YouTube title and tags, TikTok privacy, Instagram\ncover, Telegram flags, Threads reply control, LinkedIn scheduled repost — go in\n`platformSettings`, never inside the caption.\n\n## After the call\n\n`create_post` returns a `postGroupId`. Give it to the user together with the\nstored time and the resolved account names. That id is how anything is changed\nlater.\n\n- `list_posts` — what is queued, filtered by status, network or date range.\n- `get_post` — one post group in full, including per-network state.\n- `update_post` — edit content, targets, status, time or settings in place.\n  It overwrites, so state what will change before calling it. Removing a\n  network from the target list drops that network's post.\n- `delete_post` — permanent, for one post group at a time. Ask first, and\n  never run it across a list because the user said \"clear my queue\".\n\n## Retries\n\nEvery write accepts an `idempotencyKey`. Reuse the same key when retrying the\nsame post so a network hiccup cannot produce two identical posts. Change the\nkey only when the content changes.\n\n## Test without publishing\n\n`publora-playground` is a reserved target: a post sent there is acknowledged\nand discarded, and nothing reaches a real account. Use it to prove the\nconnection works before touching a live account — especially on a first run.\nIt must be the only entry in `platforms` when used.\n\n## Never\n\n- Publish or delete without the user seeing the exact text and targets.\n- Invent a `platformId`, an account, or a time the user did not confirm.\n- Answer \"which accounts do I have\" from memory. Call `list_connections`.\n- Present a draft as published, or a scheduled post as already live.\n"
}