> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/claude-skills/claude-skills/post-scheduler.md).

# post-scheduler

Schedule approved posts through Blotato MCP, select the destination and timezone, verify results, and avoid duplicate submissions.

Use this skill to publish or schedule an approved post through Blotato MCP. It selects the connected destination, checks the request, and reports the returned result. Drafting or grading alone does not authorize publishing.

## Install

Follow the [client-specific installation guide](https://help.blotato.com/claude-skills/claude-skills.md#how-to-install). Install the whole skill folder in the location for your client. Installing the skill does not establish a Blotato MCP connection. For the connection, follow [Connect your client](https://help.blotato.com/start-with-an-ai-agent/mcp/setup.md).

## SKILL.md

```md
---
name: post-scheduler
description: Publish or schedule approved social posts through Blotato MCP. Select the connected destination, resolve timing, verify the result, and avoid duplicate submissions. Use when the user requests publishing or scheduling, including a handoff from another writing skill. Draft-only requests do not authorize publishing.
---

Arguments: `[post text or path] [destination] [publish now or date/time/timezone]`.

# Post Scheduler

Preserve the user's approved text and media. Writing, grading, and generating media are separate tasks. A handoff from another skill does not expand the user's authorization.

## 1. Resolve the request

Confirm the post, media, destination, and timing from the conversation. Ask only for missing decisions. Do not default to immediate publication or the next free slot.

- For a timed post, resolve the calendar date and timezone, including daylight saving time on that date.
- For the next free slot, use `useNextFreeSlot: true` only when the user chose this option. If no slot is available, ask for another time instead of publishing now or creating slots.
- Publish immediately only when requested. Approval of wording alone is not approval of an unspecified account or time.
- Do not treat style preferences, hashtag recommendations, or a grader's score as platform requirements. Do not offer to override an enforced platform limit. Ask before revising approved content.

## 2. Verify the connection and destination

Use the Blotato tools exposed by the current client. A client-specific prefix might appear before the tool names below.

1. Call `blotato_list_accounts`. Select the requested account from its returned IDs and platform values. Ask if several accounts match.
2. For Facebook, select a Page from the account's subaccounts and set `pageId`. For LinkedIn, use `pageId` for a company Page and omit it for the personal profile. Ask which destination the user means when unclear.
3. For Pinterest, call `blotato_list_pinterest_boards` for the selected account and use the returned `boardId`.
4. For Slack or Discord, select the requested channel from the account's subaccounts and set `channelId`. Each channel is a separate destination. Do not default to the first channel in `requiredFields`. Ask which channel the user means when unclear.
5. For Discord, also set `title`. Forum channels require it, and other channels use it only to name a thread.

An authenticated empty account list is not an authentication failure. If a destination is missing, direct the user to [Accounts](https://my.blotato.com/accounts), under Add a new account. After they connect it, run account lookup again. If a Slack channel is missing, direct the user to reconnect the Slack workspace in Accounts and check the channel. For a private channel, the user must first run `/invite @Blotato` in the channel, before reconnecting. If a Discord channel is missing, the user gives the Blotato bot the View Channel and Send Messages permissions in the channel's settings in Discord, then reconnects the server in Accounts and checks the channel. Do not connect, disconnect, or change account permissions without authorization.

If the MCP connection is missing, ask which client the user uses and follow its section in [Connect your client](https://help.blotato.com/start-with-an-ai-agent/mcp/setup.md). Do not ask the user to paste credentials into the chat.

## 3. Prepare the request

Read the connected `blotato_create_post` input schema. The [tool reference](https://help.blotato.com/start-with-an-ai-agent/mcp/tools.md) covers related operations. MCP arguments are flat. They are not the nested REST `post.content` and `post.target` objects.

Use `accountId`, `platform`, `text`, and `mediaUrls`, plus the selected timing and platform fields. Publicly accessible media URLs belong in `mediaUrls`. An agent-local path is not a public URL. If media needs upload or processing, finish the supported media workflow before submitting the post. Do not create paid media as an unrequested fallback.

Platform-specific decisions include:

| Platform | Fields to check |
| --- | --- |
| Facebook | Required `pageId`. A personal Facebook profile is not a publishing destination. |
| LinkedIn | Optional `pageId` for a company Page. Omit for the personal profile. |
| Instagram | Media is required. Select the requested format and its supported options. |
| TikTok | `privacyLevel`, `disabledComments`, `disabledDuet`, `disabledStitch`, `isBrandedContent`, `isYourBrand`, and `isAiGenerated`. Do not invent privacy or disclosure choices. |
| Pinterest | Required `boardId` from board lookup. |
| YouTube | `title`, `privacyStatus`, and `shouldNotifySubscribers`. Check audience and synthetic-media options when applicable. |
| Slack | Required `channelId` from the account's subaccounts. A workspace is not a publishing destination. |
| Discord | Required `channelId` from the account's subaccounts. `title` for a forum channel. A server is not a publishing destination. |

TikTok privacy values are `PUBLIC_TO_EVERYONE`, `MUTUAL_FOLLOW_FRIENDS`, `FOLLOWER_OF_CREATOR`, and `SELF_ONLY`. Use an option supported by the selected account and authorized by the user. Use `PUBLIC_TO_EVERYONE` for a normal public post. `SELF_ONLY` means only you can see the post. The flags are named `disabledComments`, `disabledDuet`, and `disabledStitch`, not `disableComment`, `disableDuet`, or `disableStitch`.

## 4. Submit and verify

Call `blotato_create_post` once for each approved destination. A destination includes its account and, when relevant, its Page, board, or channel. Save every returned `postSubmissionId` before continuing.

| Result | Action |
| --- | --- |
| Submission ID and resolved `scheduledTime` | Report scheduled for the returned time in the user's timezone. No extra poll is needed to confirm the schedule. This is not confirmation of publication. |
| `published` | Report published and include `publicUrl` when returned. |
| `failed` | Report the returned error for this destination. Stop this submission. |
| `in-progress`, or a scheduling response without a resolved time | Call `blotato_get_post_status` with the saved submission ID. Wait at least 10 seconds between checks. Stop after a bounded wait, such as 2 minutes, and report the unresolved state and saved ID. |

Immediate publishing polls internally for up to 20 seconds. Continue status checks if it returns unfinished. Never replace a status check with another create request.

For a batch, report each destination separately. Do not recreate successful submissions or cancel them to undo another destination's failure. Review schedules in the [Blotato calendar](https://my.blotato.com/calendar). For changing or cancelling an existing item, follow [Schedule and manage posts](https://help.blotato.com/agent-workflows/agent-workflows/schedule.md) and use the existing schedule ID instead of creating another post.

## 5. Recover without duplicates

- After a timeout, network error, or lost response, the write outcome is uncertain. If an ID exists, check it. Otherwise inspect matching recent posts or schedules through the available read tools and the user's calendar. Do not assume absence proves the write failed. Stop and report uncertainty if the result remains unresolved.
- A 401 points to authentication. A 403 also involves subscription or access restrictions. Use the returned error details and setup guide instead of diagnosing every error as an expired OAuth session.
- For rate limits, follow the returned retry timing. Before retrying a write, establish the original result. Do not blindly retry a create request.
- Offer a copy-paste file when automated submission is unavailable. Save it only with permission, choose a new filename, and label it `NOT SCHEDULED OR PUBLISHED`. Include the requested timing as intent, not a completed action. Do not overwrite an existing file or call an uncertain remote submission failed.
```

## Related skills

* [post-writer](https://help.blotato.com/claude-skills/claude-skills/post-writer.md): prepares the post text.
* [post-grader](https://help.blotato.com/claude-skills/claude-skills/post-grader.md): reviews the draft.
* [content-coach](https://help.blotato.com/claude-skills/claude-skills/content-coach.md): coordinates the writing workflow.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.blotato.com/claude-skills/claude-skills/post-scheduler.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
