Update to Poolday

{
  "description": "How to brief, follow and steer a Poolday video or media production task from the chat. Use whenever the user wants a video, clip, image, voiceover, captions or other media made or edited, or asks about a Poolday task.",
  "included_files": [],
  "name": "poolday",
  "skill_md_contents": "---\nname: poolday\ndescription: How to brief, follow and steer a Poolday video or media production task from the chat. Use whenever the user wants a video, clip, image, voiceover, captions or other media made or edited, or asks about a Poolday task.\n---\n\n# Working with Poolday\n\nPoolday is an AI video editing platform. Its agent does the production work\nin the user's Poolday workspace; you brief it and relay what comes back.\nEverything happens in the one workspace the user connected, as that user.\n\n## When to use it\n\n- The user wants a video, clip, image, voiceover, music track, captions or\n  a brand-kit application made or changed.\n- The user refers to a Poolday task (\"my video\", \"the clip from yesterday\").\n\nDo not use it for writing that is not media production, for Poolday billing\nor plan changes, or for editing inside another application.\n\n## Starting a task\n\nCall `start_task` once with a brief written as for a skilled editor:\n\n- goal and audience\n- length, format and aspect ratio (for example 20 s, vertical 9:16)\n- tone and pace\n- must-haves: text on screen, captions, a call to action, a voice\n- media to use: `asset:<id>` for files already in the Poolday library,\n  pasted links (YouTube, TikTok, Instagram, web pages), or `attachments`\n  for files the user gave you in the chat\n\nA task runs for minutes in the background. Tell the user it has started and\nstop. Do not call `get_task` in a loop; the panel follows the task itself.\n\nModes: `build` (default) goes straight to making it; `clarify` lets Poolday\nask questions first; `align` has it propose a plan and wait for approval.\nPick `clarify` or `align` when the brief is thin or the stakes are high.\nLeave `tier` unset unless the user asks for a specific production tier.\n\nThe brief says what to make, nothing else. Never write answers to questions\nPoolday has not asked yet into a brief, and never tell it how to behave when\nit asks: wait for the question, then send the user's answer with\n`answer_question`.\n\n## Files on the user's computer\n\nCall `add_files` before `start_task`. The panel takes drops and uploads;\nonce a file is in, reference it by the returned asset reference or by name.\n\n## Following a task\n\nCall `get_task` only when the user asks. Report the status in words:\n\n- `working` or `preparing`: say so, no need to poll\n- `needs_input`: relay `question` to the user, then send their reply with\n  `answer_question` (or `skip: true` if they want Poolday to decide)\n- `done`: list the outputs with their links\n- `failed`: relay the reason and offer to start again with a clearer brief\n\n`list_tasks` finds a task id when the user refers to earlier work.\n\n## Changing a finished task\n\nSend the change with `send_message` (\"make it 15 seconds\", \"use the\nsecond voice\"). It works only while the task is not running; if Poolday\nrefuses because the task is still working or waiting on a question, say so\nand do not start a second task for the same job.\n\n## Credits\n\nStarting and messaging a task uses the workspace's Poolday credits. If a\ntool reports there are not enough, tell the user plainly and stop.\n"
}