Update to PostQuickAI

{
  "description": "Create a reply-based thread draft with two or more connected parts for X, Threads, or Bluesky. Use when the user says \"create a thread\", \"tweet storm\", \"multi-part post\", or references a numbered list of posts.\n",
  "included_files": [],
  "name": "reply-thread",
  "skill_md_contents": "---\nname: reply-thread\ndescription: >\n  Create a reply-based thread draft with two or more connected parts for X,\n  Threads, or Bluesky. Use when the user says \"create a thread\", \"tweet storm\",\n  \"multi-part post\", or references a numbered list of posts.\n---\n\n# Reply Thread\n\n## Goal\nCreate one draft whose parts can be scheduled as a reply chain.\n\n## Workflow\n\n1. **Pick the brand.** Call `listContentGroups`. Ask the user to choose when the content group is ambiguous.\n\n2. **Check accounts.** Call `listAccounts`. Only offer connected accounts.\n\n3. **Collect the parts.** Use text the user supplies, or ask for a topic and propose a complete thread. Each part must fit the smallest selected platform limit:\n   - X: 280 characters\n   - Bluesky: 300 characters\n   - Threads: 500 characters\n   Use 5–10 parts unless the user requests another count.\n\n4. **Select thread-capable platforms.** Only X, Threads, and Bluesky support reply threading. If the user asks for another platform, explain that it cannot receive the reply chain and ask whether to exclude it.\n\n5. **Preview and confirm.** Show every part and destination before creating the draft.\n\n6. **Create the draft.** Call `createPost` with the approved first-part content, selected platforms, and all approved thread parts. Keep it as a draft.\n\n7. **Schedule if requested.** Confirm the exact time and timezone, then call `schedulePost` for the returned draft ID. If the user asks to publish immediately, explain that the connector has no immediate post-publishing tool and direct them to the PostQuickAI dashboard.\n\n## Never do\n\n- Never create a thread with fewer than two parts; use a normal post instead.\n- Never target an account that `listAccounts` did not return.\n- Never silently publish a reply chain to an unsupported platform.\n- Never exceed any selected platform's character limit.\n- Never schedule before the user confirms every part, destination, and time.\n"
}