Update to ReelsFarm

{
  "description": "Preflight, schedule, or publish approved ReelsFarm content to an exact connected social account. Use for TikTok, YouTube, Instagram, Facebook, and scheduler publishing requests.",
  "included_files": [],
  "name": "reelsfarm-publishing",
  "skill_md_contents": "---\nname: reelsfarm-publishing\ndescription: Preflight, schedule, or publish approved ReelsFarm content to an exact connected social account. Use for TikTok, YouTube, Instagram, Facebook, and scheduler publishing requests.\n---\n\n# ReelsFarm publishing\n\nPublish only approved content to an exact connected account. Always perform account discovery and publishing preflight before scheduling or publishing.\n\n## Tool discovery\n\nDiscover the ReelsFarm MCP tools before acting. Start with `reelsfarm_get_account`. Use `reelsfarm_list_connected_accounts` and `reelsfarm_list_social_accounts` to find eligible destinations. Use `reelsfarm_list_videos`, `reelsfarm_list_slideshows`, and `reelsfarm_list_gallery` to resolve the exact content. Use `reelsfarm_list_scheduled_posts` and `reelsfarm_get_publish_status` to inspect existing publishing work.\n\nNever choose an account from a platform name alone when more than one eligible account exists. Ask the user to select the exact account. Social account linking and credential changes remain dashboard-only.\n\n## ChatGPT follow-ups\n\nIn ChatGPT, ReelsFarm app selection applies to one user message. A follow-up that needs another ReelsFarm tool call must select or `@mention` ReelsFarm again. If the current turn has no ReelsFarm tools, do not claim that ReelsFarm lacks the requested capability. Ask the user to select ReelsFarm and resend the action. Discussing an existing result without a new tool call does not require reselection.\n\n## Preparation\n\nConfirm the content, content type, publish format, caption, timezone, exact account, and scheduled time. Use `reelsfarm_validate_caption` for all selected platforms. Then run `reelsfarm_preflight_publishing` with the exact targets.\n\nResolve every preflight error before preparation. Use `reelsfarm_prepare_schedule_post` for a future time and `reelsfarm_prepare_publish_now` for immediate publishing. Use `dryRun: true` when the user requests a preview or when any destination, caption, time, or platform setting is not final.\n\n## Confirmation\n\nShow the exact content, account labels, platforms, caption, timezone, and final scheduled time or immediate action. Get explicit user approval before calling the operation-specific tool named in the prepared result's `confirmationTool` field. Do not treat approval of the content itself as approval to publish. Do not confirm if preflight is stale or if the prepare call already executed.\n\n## Job polling\n\nAfter confirmation, poll durable mutation state with `reelsfarm_get_operation` when an operation identifier is returned. Poll the post with `reelsfarm_get_publish_status` when a scheduled post identifier is available. Stop polling when each platform is scheduled, published, failed, or cancelled. Report partial platform failures separately.\n\n## Result integrity\n\nUse `executionState` as the authoritative mutation state. Treat `NOT_STARTED` and `PREPARED` as no execution. Treat `ENQUEUED` and `PROCESSING` as unfinished. Report a ReelsFarm schedule or publish action as complete only when `provider` is `reelsfarm` and the durable operation or publish status confirms the final state. Do not report a prepared action as scheduled or published.\n\n## Idempotency\n\nUse one stable `idempotencyKey` for each logical schedule or publish request. Reuse the same key after a timeout, connection error, or uncertain response. Use a new key only when the user changes the content, target, caption, time, or publish format.\n\n## Error recovery\n\nIf the mutation result is ambiguous, call `reelsfarm_get_operation` before any retry. Do not prepare or confirm a duplicate post until the durable operation and publish status are known. If preflight or confirmation expires, rerun preflight, prepare again, and request approval again. If one platform fails, do not republish successful platforms without a new explicit request.\n\n## Safe stopping\n\nStop when paid access is inactive, no eligible account exists, the account is ambiguous, caption validation fails, preflight fails, the time or timezone is unclear, the content is not approved, or the user does not approve confirmation. Do not link or disconnect accounts. Do not change billing, security settings, or publishing credentials.\n"
}