posting-queuelisted

Configure and inspect the Upload-Post posting queue — the recurring time slots that queued content drips into. Use when the user wants a posting schedule or rhythm, asks when their next post goes out, wants to change posting times or days, or says they want to queue content instead of picking exact timestamps.
Upload-Post/upload-post-plugin · ★ 1 · AI & Automation · score 63

Install: claude install-skill Upload-Post/upload-post-plugin

# Manage the posting queue The queue is a recurring weekly grid of slots per profile. Anything uploaded with `addToQueue: true` fills the next free slot instead of needing an explicit timestamp. This is how a user gets a consistent rhythm without picking dates by hand. ## 1. Read the current setup Call `get_queue_settings` with `profile_username`. The schema marks it optional, but the API rejects the call with `400 profile_username is required` — always pass it. Get the name from `list_users` first if you do not have it. It returns `timezone`, `slots`, `days_of_week`, `max_posts_per_slot`, and `full_slots` (slots already at capacity). Then call `preview_queue` (same `profile_username`) to show what is actually lined up. Pass `nextSlot: true` when the user only asks "when does my next post go out?" — it returns just `next_slot` with `datetime_utc`, `datetime_local` and `timezone`, instead of the whole grid. Quote the **local** time back to the user; the UTC field is for your own arithmetic. Present it as a compact weekly view, not raw JSON. For example: ``` Europe/Madrid · Mon–Fri 10:00 → "Behind the scenes" (Thu) 16:00 → free ``` ## 2. Change it `update_queue_settings` takes: - `profile_username` — required. - `timezone` — IANA name (`Europe/Madrid`, `America/New_York`). Slots are local to this, so changing it moves every slot. - `slots` — array of `{ hour, minute }` in 24-hour local time, sorted by time, max 24. `minute` defaults to 0. - `days_of_week` — allo