Update to ImagineArt

{
  "name": "motion",
  "description": "Camera-driven and cinematic video — dolly, orbit, crane, FPV, drone and aerial shots, plus food and recipe video. Use when the user describes how the camera moves or wants a cinematic clip of a subject. Not for preset viral looks on an uploaded photo (use Effects) and not for fashion motion (use Fashion).",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 470
    },
    {
      "relative_path": "assets/ATTRIBUTION.md",
      "size_in_bytes": 942
    },
    {
      "relative_path": "assets/icon.svg",
      "size_in_bytes": 427
    },
    {
      "relative_path": "references/errors.md",
      "size_in_bytes": 2325
    },
    {
      "relative_path": "references/models.md",
      "size_in_bytes": 3809
    },
    {
      "relative_path": "references/qa.md",
      "size_in_bytes": 656
    },
    {
      "relative_path": "references/recipes.md",
      "size_in_bytes": 1814
    }
  ],
  "skill_md_contents": "---\nname: motion\ndescription: Camera-driven and cinematic video — dolly, orbit, crane, FPV, drone and aerial shots, plus food and recipe video. Use when the user describes how the camera moves or wants a cinematic clip of a subject. Not for preset viral looks on an uploaded photo (use Effects) and not for fashion motion (use Fashion).\n---\n\n# Motion\n\nRead `references/recipes.md` for the move library and `references/models.md` before any\ncall — model choice here is a quality choice.\n\n## Tokens\n\n| Token | What it does |\n|---|---|\n| `/dolly` `/crane` `/push` `/track` | Camera moves |\n| `/fpv` `/drone` `/aerial` | Drone and FPV footage |\n| `/recipe` `/cooking` `/food` | Food and recipe video |\n| `/cinematic` | General cinematic treatment |\n\n## Overlap with Effects\n\n**`/orbit` belongs to Effects**, which owns preset looks applied to an uploaded photo. Use\nMotion when the user describes a camera move for a scene being generated, or supplies a\nstill to move *through* rather than a subject to orbit. When both could apply and the user\nuploaded a photo, Effects wins.\n\n## Resolving the move\n\n`list_camera_movements` and `list_camera_angles` hold the valid values. **Never invent\none** — match the user's words to a real entry.\n\n**Do not use `list_durations` or `list_resolutions` here** — those describe ad generation.\nVideo durations and resolutions are per-model allow-lists in `references/models.md`.\n\n| Request | Tool |\n|---|---|\n| Aerial / drone footage | `generate_drone_video` |\n| Food and recipe | `generate_cooking_video` |\n| Everything else | `generate_video` with the movement written into the prompt |\n\nIf the user supplied a still to move through, pass it as `image_url` with **exactly one**\nURL — that switches the call to image-to-video.\n\n## Model choice is the quality decision\n\nCamera control and resolution ceiling vary sharply. From `references/models.md`:\n\n- **Controlled, specific moves** → `seedance-2.5` has the strongest adherence, but caps at\n  **720p** and **refuses people**.\n- **Quality first** → `ltx-2.3` at 1080p+ (durations 6/8/10 only) or `seedance-2.0` at 1080p.\n- **People in frame** → never `seedance-2.5`. Open on `seedance-2.0` at 1080p.\n\nSay which model you picked in one line so the user can ask for something else.\n\n**Never omit `resolution`** — it defaults to the model's lowest tier.\n\n## Food\n\n`generate_cooking_video`. This category reads through **steam, texture and motion** — a\npour, a cut, rising steam. Warm directional light; flat light makes food look dead. Don't\ninflate portions beyond what the recipe produces.\n\n## Defaults\n\n`16:9` — these are cinematic shots, not feed content, unless the user says otherwise.\n`9:16` for food headed to social.\n\n## Conventions\n\nNever print `org_id`, `folder_id`, or raw asset uuids.\n\n## When something fails\n\nRead `references/errors.md`. Identify the kind of failure before responding: pending jobs\nare waited on, technical errors retried at most twice, unsupported capabilities stated\nplainly, safety refusals never routed around, and every material change disclosed.\n\n## QA before delivery\n\nRun `references/qa.md` before calling this finished. Inspect the actual output — never\nclaim quality you have not observed, and say plainly what you could not verify.\n"
}