Update to Aixcut

{
  "description": "Generate images, videos, or music in Aixcut and track asynchronous jobs. Use for new visual or audio assets and generation progress. Do not use to edit existing media or assemble a complete video.",
  "included_files": [
    {
      "relative_path": "references/providers.md",
      "size_in_bytes": 6430
    }
  ],
  "name": "aixcut-generation",
  "skill_md_contents": "---\nname: aixcut-generation\ndescription: \"Generate images, videos, or music in Aixcut and track asynchronous jobs. Use for new visual or audio assets and generation progress. Do not use to edit existing media or assemble a complete video.\"\n---\n\n# Aixcut Generation\n\n## Conversation guidance\n\nState whether generation is being prepared, queued, running, or complete, and what happens next. Continue safe status checks when possible. Pause before an unaccepted cost or credits, or when a missing creative choice would materially change the result. Do not describe a submitted Job as a finished asset.\n\nGeneration creates a durable Job; it is not a synchronous operation.\n\n## Short path\n\n1. Confirm the target Project; read `aixcut_read(view=\"project\")` if needed.\n2. If generation may consume credits and the user has not accepted a quoted amount, call `aixcut_generate(action=\"quote\")`. It does not create a Job. If the quote is nonzero, explain the amount and wait for the user's acceptance before submitting; pass the accepted amount as `accepted_quoted_credits`.\n3. Submit using `aixcut_generate(action=\"submit\")` only after required creative choices are clear and any quoted charge is accepted.\n4. If the envelope returns `status: \"async\"`, retain its top-level `job_id` and use `aixcut_generate(action=\"get\")` to read the durable Job; ClipOS runs accepted Jobs independently of polling or the browser connection. Never resubmit a queued or running Job.\n5. Use top-level `next_action.after_seconds` for the next poll. Stop when top-level `terminal` is true.\n6. Report `result.data.job.phase`: `waiting` (queued), `processing` (generating), or `finalizing` (publishing to the Project). Do not report only “in progress.”\n7. After generation, place the result on a timeline when the user asked for it.\n\nFor multiple video versions, the assembly Skill first lists and duplicates timelines with `aixcut_timeline(action=\"list\")`. `aixcut_generate` creates Project-level assets that can be reused by multiple `timeline_id`s. Place and verify the result on each requested timeline.\n\n## Content language and prompt\n\nFollow the user's requested content language and target audience for visible text, dialogue, lyrics, or other language-bearing parts of the asset. A prompt may be written in English for model reliability, but the prompt must still explicitly state the requested spoken/on-screen language when relevant. Do not silently translate the user's creative brief or switch the asset to English because this Skill is in English. Preserve the creative direction and wording unless asked to adapt it. Apply the shared language policy from `aixcut-basics`.\n\nResolve only the language choice relevant to the requested asset: visible text for images; dialogue and on-screen text for videos; lyrics for songs (instrumental music has no content language); and script language for voiceover. If the user says “song” but does not indicate lyrics or instrumental music, ask which they want before quoting or submitting. Do not ask about language for instrumental music.\n\n## Generation types\n\n- Generation Jobs use `kind=image`, `video`, or `music`; the server processes music as audio. To discover providers/models, `aixcut_generate(action=\"catalog\")` also supports `kind=speech`. If `kind` is omitted from `catalog`, the server returns speech models by default.\n- If the user does not specify a provider, use the server default. Override only on explicit request.\n- Prompt, style, duration, and language-bearing content should follow the user's brief; do not rewrite the creative direction without reason.\n\n## Asset source\n\nGeneration creates images, videos, and music in the Project library; it does not create Motion Graph source assets, import files, or perform post-production on existing audio. Do not use a generic video-generation Job as a substitute for an editable Motion Graph. If no supported MG asset or creation path is available, report that limitation rather than substituting captions. Use `aixcut-timeline-editing` to place, trim, mix, or fade audio, and use its local-media flow to import media. Documents must be uploaded through the Project page because the hosted MCP service cannot read a path on the user's computer. Provider-supported image editing with reference images remains a generation operation.\n\nGenerated media does not guarantee exact beat alignment, lyric timing, or caption timing. Do not promise frame-accurate synchronization from a generation prompt; use timeline tools and read-back evidence for placement and synchronization.\n\n- Generated assets enter the Project library. Final video export happens in the open Project page.\n- Do not invent URLs or send local paths as links.\n\n## Boundaries\n\n- Submission is not completion. Do not report success while the Job is `queued`, `running`, or `publishing`.\n- On failure, report `result.data.job.error_code`.\n- Top-level `retryable` appears only for failed Jobs. `true` means the same request may work later; `false` means fix parameters, media, or configuration first. Do not retry automatically when absent.\n- Use `action=\"cancel\"` to cancel and `action=\"list\"` to list Jobs.\n- Generation download URLs are short-lived signed URLs. Do not store them in Project documents or retain them long term.\n\n## Completion\n\nThe Job must be terminal, the asset must be placed if requested, and a timeline read must show the corresponding clip. Report `job_id`, final status, and placed ref.\n\n## Brief, anchors, and recovery\n\nFor video or image generation, keep a compact brief with subject, action, camera/composition, lighting/style, duration/aspect ratio, language-bearing text or dialogue, negative constraints, and acceptance evidence. Use stable reference media or first/last-frame anchors when continuity matters; inspect the returned asset before placing it. A `submission_unknown` result is recovered with the original idempotency identity and the same request through the durable Job state. Never submit a fresh Job to resolve an uncertain submission.\n\nAfter two failed attempts for the same creative goal, inspect the failure evidence and change the approach: use supported reference/edit or anchor inputs, reduce scope with the user's existing authorization, or report the capability limit. Never loop through new paid Jobs just by rewriting prompts. Each separately authorized retry preserves completed assets and records what changed.\n"
}