Update to PostZen

{
  "description": "Set up and manage PostZen posting queues — recurring time slots that posts fill automatically. Use when the user wants to create, review, or reorganize their posting schedule, see upcoming slots, or post at their best-performing times.",
  "included_files": [],
  "name": "queue",
  "skill_md_contents": "---\nname: queue\ndescription: Set up and manage PostZen posting queues — recurring time slots that posts fill automatically. Use when the user wants to create, review, or reorganize their posting schedule, see upcoming slots, or post at their best-performing times.\n---\n\n# Manage PostZen queues\n\nHelp the user build and maintain a posting queue. The user's request follows: \"$ARGUMENTS\"\n\nA queue is a set of recurring weekly time slots (e.g. Mon/Wed/Fri at 9:00) tied to a profile and timezone. Posts added \"to the queue\" are scheduled into the next open slot automatically.\n\n## Workflow\n\n1. **Show current state.** Call `listQueueSlots` and summarize the existing schedule as a compact weekly view (day + time + timezone). If empty, say so and move to setup.\n2. **Setting up or changing slots:**\n   - First resolve the profile with `listProfiles` and read its queue with `listQueueSlots`. `createQueue` creates an entire queue, not a single slot. To add or move slots on an existing queue, use `updateQueue` with its queue ID and the complete slot list, preserving all slots the user did not ask to change. Do not duplicate an existing day/time. Create a queue only when a new queue is requested or none exists. Confirm the timezone — use the user's profile timezone unless they specify one, and echo it back (\"9:00 AM America/Edmonton\").\n   - If the user asks for \"good times\" or doesn't specify, call `getBestTimeToPost` for their connected accounts and propose a concrete slot set built from the top suggestions (e.g. 3 slots/week to start). Create the slots only after they approve the proposal.\n   - To remove one slot, use `updateQueue` with the remaining slots. `deleteQueue` deletes a whole queue; omitting queueId deletes every queue on the profile. Always supply the intended queueId and obtain confirmation before deleting a queue. Existing posts retain their scheduled times. Reshuffling existing posts requires an explicit update with reshuffleExisting=true; do not request it unless the user authorized rescheduling.\n3. **Review what's coming.** `previewQueue` shows how queued posts map onto upcoming slots — use it after any slot change so the user sees the effect, and whenever they ask \"what's going out this week?\" (combine with `listPosts` filtered to scheduled/queued for the full picture).\n4. **Filling the queue.** Queue a post by calling `createPost` with `queuedFromProfile` (plus `queueId` for a non-default queue) instead of `scheduledFor` — PostZen assigns the next free slot atomically and returns it as the post's `scheduledFor`. Queuing several posts in sequence lands them in consecutive slots automatically. Never fetch `getNextQueueSlot` and pass its time back as `scheduledFor`: the slot isn't reserved by that call, so a concurrent create can take it and the post ends up scheduled outside the queue. `getNextQueueSlot` is for *telling the user* when their next slot is, nothing more.\n\n## Notes\n\n- Slots are per-profile. If the user has multiple profiles, confirm which one before creating or deleting anything.\n- Keep proposals modest: a new queue with 3–5 slots a week is easier to sustain than a dense one; the user can always add more.\n- All times shown to the user should include the timezone; silent UTC is how posts end up publishing at 3 AM.\n"
}