Update to Ravenpost

{
  "description": "Find, edit, reschedule, cancel or delete posts already in Ravenpost, and check how a published post actually landed on each account. Use when the user asks what is scheduled, wants to change or move a post (\"move Friday's post to Monday\", \"fix the typo in the draft\", \"cancel the TikTok one\"), asks whether a post went out, or asks why one failed. Covers the trap that editing a post resets it to a draft, and what deleting does and does not remove.",
  "included_files": [],
  "name": "manage-scheduled-posts",
  "skill_md_contents": "---\nname: manage-scheduled-posts\ndescription: Find, edit, reschedule, cancel or delete posts already in Ravenpost, and check how a published post actually landed on each account. Use when the user asks what is scheduled, wants to change or move a post (\"move Friday's post to Monday\", \"fix the typo in the draft\", \"cancel the TikTok one\"), asks whether a post went out, or asks why one failed. Covers the trap that editing a post resets it to a draft, and what deleting does and does not remove.\n---\n\n# Manage posts that already exist\n\nEverything here acts on a post that is already in Ravenpost. Composing a new one\nis the `publish-a-social-post` skill. Full argument list:\n[`../publish-a-social-post/references/tools.md`](../publish-a-social-post/references/tools.md).\n\n**Settle the workspace first** — `list_workspaces`, and ask if there is more than\none. Post ids belong to a workspace like everything else.\n\n## Finding the post\n\n`list_posts` takes an optional `status`: `DRAFT`, `SCHEDULED`, `PUBLISHING`,\n`PUBLISHED`, `FAILED`. \"What's scheduled?\" is `status: \"SCHEDULED\"`, which\ncomes back soonest first; \"did anything fail?\" is `FAILED`. It returns 50 posts\na page, newest first otherwise — `total` says how many match, and `page` reads\nfurther back, so say \"the 50 most recent\" rather than \"all of them\" when\n`totalPages` is more than one.\n\n`get_post` returns one post with **every destination's own status, permalink and\nerror**. That per-target list is the answer to \"did it go out?\" — a post can be\npublished to X and failed on Instagram at the same time, and the rollup alone\nwould hide it.\n\n## Changing one\n\n| The user wants | Use | Watch out for |\n|---|---|---|\n| Different words, media, accounts or format | `update_post` | **It resets the post to a draft.** |\n| The same post at a different time | `schedule_post` | Content untouched; absolute ISO 8601 with offset |\n| It out now | `publish_post` | Not reversible — needs an explicit instruction |\n| It gone | `delete_post` | Only removes Ravenpost's copy |\n\n**The reset is the one that bites.** `update_post` returns the post to `DRAFT`,\nso a scheduled post that is edited **stops going out** unless the same call also\ncarries `action` (`schedule` + `scheduledAt`, `queue`, or `now`). Fixing a typo\nin Friday's post and leaving it there is how a post silently misses its slot.\nWhen the user says \"fix the typo\", the whole job is: update, re-schedule to the\nsame time, and say both happened.\n\nA published or publishing post can no longer be edited. Offer to delete it and\ncompose a new one instead — and see the next section before promising that.\n\n## What deleting actually does\n\n`delete_post` removes the Ravenpost copy and cancels a pending publish. **It does\nnot take down a post that is already live**, and on Instagram, Threads, TikTok and\nYouTube nothing can: their APIs expose no delete endpoint Ravenpost holds the\nscope for. Say which copies stay up rather than letting \"deleted\" be heard as\n\"gone from the internet\". A post the user actually wants removed from Instagram\nhas to be removed in Instagram.\n\nDeleting is permanent and takes the post's targets and queued jobs with it, so\nconfirm before calling it — a draft is cheap to keep, and there is no undo.\n\n## Watching a publish land\n\nPublishing is queued, not synchronous: `publish_post` and `create_post` with\n`action: \"now\"` return as soon as the job is accepted. The per-account outcome\narrives seconds to minutes later.\n\nSo report it honestly — \"queued for 3 accounts\" — then call `get_post` to see\neach target settle. A target that fails carries the platform's own reason in\n`error`; pass it on verbatim rather than paraphrasing it into something vaguer.\nCommon ones are worth recognising:\n\n- **a token that expired** — LinkedIn connections need reconnecting roughly\n  every 60 days, and the account shows as needing attention on the Accounts page.\n  Nothing you can do from here; tell the user where to fix it.\n- **a missing Pinterest board** — the post was created without one. Add it with\n  `update_post` (`board`), then re-publish.\n- **TikTok rejecting an image** — PNG is refused; JPEG or WebP only, and the\n  refusal arrives minutes after the upload succeeded.\n"
}