Update to PostQuickAI

{
  "description": "Draft and schedule a week of social media content for a PostQuickAI content group. Use when the user says \"plan my week\", \"batch this week's content\", \"weekly content\", or references scheduling multiple posts at once.\n",
  "included_files": [],
  "name": "weekly-content-batch",
  "skill_md_contents": "---\nname: weekly-content-batch\ndescription: >\n  Draft and schedule a week of social media content for a PostQuickAI content\n  group. Use when the user says \"plan my week\", \"batch this week's content\",\n  \"weekly content\", or references scheduling multiple posts at once.\n---\n\n# Weekly Content Batch\n\n## Goal\nPrepare 5–7 brand-aligned drafts, get approval, then schedule them across the week.\n\n## Workflow\n\n1. **Pick the brand.** Call `listContentGroups`. If multiple groups exist, ask the user which brand.\n\n2. **Load brand context.** Call `getInstructions` and `getBrandContext` for that group. Use the returned voice, audience, tone, and topics.\n\n3. **Check destinations.** Call `listAccounts`. Ask the user to choose among connected accounts if the destination is not clear.\n\n4. **Collect topic seeds.** Ask for 5–7 topics, or propose topics based on the saved brand context. Wait for approval.\n\n5. **Prepare each draft.** For each approved topic:\n   - Call `generateCaption`, `generateCarouselCaption`, or `generateVideoCaption` for the requested format.\n   - Call `createPost` to save text or carousel content as a draft. Use `createVideo` only when the user supplied a public video URL.\n   - Keep the returned ID and content preview.\n   - If a tool returns `LIMIT_EXCEEDED`, stop and say how many drafts were created.\n\n6. **Preview the batch.** Show every draft, destination, date, time, and timezone. Do not schedule anything until the user confirms the full batch.\n\n7. **Schedule the approved batch.** Call `bulkSchedule` once with the approved post, video or story IDs, destinations and timestamps. The batch either succeeds together or makes no schedule changes. Use `getCalendar` to check the saved campaign. Respect the user's requested spacing; ask if two items conflict.\n\n8. **Return a summary.** Include date, time, timezone, platforms, content preview, and draft ID.\n\n## Error handling\n\n- `LIMIT_EXCEEDED` — stop; never retry silently.\n- A missing content group or account — refresh with `listContentGroups` or `listAccounts`; never invent an ID.\n- A failed or timed-out write — check each saved item and `getCalendar` before deciding whether another attempt is safe. Never blindly retry a write.\n\n## Never do\n\n- Never schedule before showing the full batch and receiving approval.\n- Never exceed the requested post count.\n- Never skip the saved brand instructions when they are available.\n- For cancellation, show the affected future schedules and obtain approval before `cancelSchedule`. Cancellation cannot recall already published items or accepted publishing work.\n"
}