antwork-calendarlisted
Install: claude install-skill polynode-co/antwork-skills
# Planning a content calendar with Antwork
Antwork is an MCP-native social scheduler. A calendar is just a set of drafts each bound to one account and a `scheduled_for` time. The job is to plan the whole grid *first*, get approval, then create and schedule each slot. This workflow codifies the mistakes assistants make when batch-scheduling.
## 1. Read the existing calendar before proposing anything
Never schedule into a vacuum. First call:
- `list_posts(date_from, date_to, group_by_day=true)` — what's already scheduled or published in the target window. Plan *around* it; don't double-book a slot or repeat a topic that just went out.
- `get_post_context` — its `workspace` block holds the configured posting times (`preferredTimes`) and `timezone`. These times are your default slots.
- `list_social_accounts` — the accounts you can target (with `account_id`, platform, handle, token health). Skip accounts whose `tokenHealthStatus` isn't `healthy` — flag them for reconnect instead of scheduling onto a dead token.
If multiple workspaces exist and none is default, resolve with `set_default_workspace` before anything else.
## 2. Present the calendar as a plan — and wait
Editing a plan is cheaper than editing fifteen drafts. Present the calendar as a **numbered table** and stop for explicit approval before creating a single post. One row per slot:
`# | date · time (tz) | account / platform | hook | goal`
Use `templates/content-calendar.md` as the skeleton. Space slots across t