Update to Kling AI
Snapshot Nov 21, 2026 · 18:11 UTC · version 1.2.0
Collection source: downloaded plugin package.
Payment or plan references changed
Full description — Now says: Plan Kling AI image prompts and video storyboards, prepare or submit authorized Kling generations, and manage Elements, saved motions, credits, known tasks,...
Observed in published text. Live prices and checkout terms have not been verified by this change.
Up to 3 plugins free · no card required.
All fields and original values.
Full description
Oct 24, 2026 · 12:58 UTC
Generate images or videos with Kling AI in Codex, or handle existing tasks, conversation references, subject and motion libraries, credits, and account connections. Capabilities depend on the current account's live CLI response. Do not u...
Nov 21, 2026 · 18:11 UTC
Plan Kling AI image prompts and video storyboards, prepare or submit authorized Kling generations, and manage Elements, saved motions, credits, known tasks, and account access.
Skill instructions
Oct 24, 2026 · 12:58 UTC
Generate images or videos with Kling AI in Codex, or handle existing tasks, conversation references, subject and motion libraries, credits, and account connections. Capabilities depend on the current account's live CLI response. Do not u...
Nov 21, 2026 · 18:11 UTC
Plan Kling AI image prompts and video storyboards, prepare or submit authorized Kling generations, and manage Elements, saved motions, credits, known tasks, and account access. # Kling AI ## Route the request - For prompt-only work, retu...
Supporting files
Oct 24, 2026 · 12:58 UTC
[{"relative_path":"agents/openai.yaml","size_in_bytes":300},{"relative_path":"references/asset-workflows.md","size_in_bytes":7805},{"relative_path":"references/audio-options.md","size_in_bytes":1521},{"relative_path":"references/capabili...
Nov 21, 2026 · 18:11 UTC
[{"relative_path":"agents/openai.yaml","size_in_bytes":338},{"relative_path":"references/cli-contract.md","size_in_bytes":7730},{"relative_path":"references/elements-motion-feedback.md","size_in_bytes":7784},{"relative_path":"references/...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,49 +1,32 @@ --- name: kling-ai -description: Generate images or videos with Kling AI in Codex, or handle existing tasks, conversation references, subject and motion libraries, credits, and account connections. Capabilities depend on the current account's live CLI response. Do not use for media analysis that does not call Kling. +description: Plan Kling AI image prompts and video storyboards, prepare or submit authorized Kling generations, and manage Elements, saved motions, credits, known tasks, and account access. --- -# Kling AI for Terminal +# Kling AI -Use only the pinned Global CLI in the [CLI contract](references/cli-contract.md). This is a local Skills-only plugin. The CLI owns browser OAuth; do not request or log credentials, private account fields, or signed URLs. +## Route the request -## Load rules by request +- For prompt-only work, return the requested prompt or storyboard. For a missing required reference, ask for the asset and explain its role. Neither needs an account query. +- For `text_to_image` or `image_to_image`, use the [image Skill](../kling-ai-generate-image/SKILL.md). For `text_to_video`, `image_to_video`, `omni_ref_video`, or `motion_control`, use the [video Skill](../kling-ai-generate-video/SKILL.md). +- For Elements, browsing saved motions, or authorized feedback, use [the relevant tools](references/elements-motion-feedback.md). Resolve real IDs before use. An attachment or library operation does not authorize a generation. +- Check credits through the selected runtime. Model availability comes from `who_am_i`. A direct status request runs `query_tasks` once for the known `generationId`. -- Image generation, editing, posters, and reference-based creation: use `kling-ai-generate-image`. -- Video generation, keyframes, omni references, motion control, and shot planning: first read the [video Skill](../kling-ai-generate-video/SKILL.md) and follow its entry-point routing before choosing a model. Reading only this core Skill and the submission workflow is insufficient. -- Progress, existing results, or refreshed output links: read only [task results](references/task-results.md), without generation recommendations, model parameters, or creative references. -- New generation, edits, or authorized retries: select through the relevant creative Skill, then follow [generation submission](references/tool-workflows.md). Execute dependent steps in order. -- Subject library, motion library, or conversation references: read [asset workflows](references/asset-workflows.md). Read-only asset queries never submit generation. -- Before generation, read [capability discovery](references/capability-discovery.md). After selecting an available model, use the [parameter module table](references/model-parameters.md) to load only supported rules needed for this request. -- Authorization, upload, model, or service errors: read [troubleshooting](references/troubleshooting.md). Read [examples](references/prompt-examples.md) when examples are needed. +## Connection and account -## Account visibility and rollout +Read [host routing](references/host-routing.md) to select the runtime before any tool call, account check, or login. Keep one backend, account, and region per objective. Use logout or switch accounts only on request. If authorization is required, explain the return-to-client step and let the original login process finish. Only report login complete after `who_am_i` succeeds with an authenticated identity on that same connection. -- The current account's live `who_am_i` response governs models, parameters, specifications, input types, and combination limits. `tool_list` establishes tool availability and call structure; membership pages, tool descriptions, and static examples cannot override account capabilities. -- Display, recommend, or call a model name only when the current `tool_list` exposes its tool and `who_am_i.availableModels` lists it under that tool. Tool counts, newly exposed omni tools, example names, and default-model fields are not substitutes for membership in that model set. -- Compare "latest" only within available models supporting the required output type and intent. Do not mix image and video versions; `defaultModel` does not mean latest. Qualify the conclusion as the latest image/video model available to the current account. If no suitable new model is returned, use an available model without mentioning higher versions, unreleased names, allowlists, or better hidden models. Never fill gaps from Skills, snapshots, other accounts, or earlier sessions. -- If a requested model is absent from filtered discovery, expand discovery as described in [capability discovery](references/capability-discovery.md). If it exists only for another output type, explain the mismatch and let the user choose whether to keep the requested medium or use the model's supported medium; do not switch silently. After complete discovery, report only that the current connection did not return the requested model, without repeating hidden names. Alternatives must be actually available and suitable. -- Rediscover tools and models after reconnecting or changing account/environment. If discovery fails or model membership cannot be established, do not submit using a static fallback. +## Prepare and submit -## Creative and capability selection +1. Follow [model discovery and request validation](references/generation-settings.md). Prefer directly attached images and map each reference to its live input slot. Preserve one UUIDv7 `taskTraceId` for the objective where supported. Retain the returned `generationId` as the task number. +2. Show the final tool and model, prompt summary, output count, resolution, duration and ratio as applicable, reference roles, and requested audio, HDR or shot settings. Explain live billing rules, including per-second billing and input video duration when declared. A proposal ends here. Before generation, get explicit authorization for the final settings, reusing approval already given for these settings. +3. Verify the actual request against the live schema. Immediately before submission, check the same account's balance. Pause if verification fails, the balance is nonpositive, or the service confirms it is insufficient for these settings. A positive balance without a live estimate provides no cost guarantee. Each authorization covers at most one submission attempt. Keep at most one non-terminal paid task for a dependent workflow. +4. Preserve the returned task number and query only that task. If submission is ambiguous or the CLI exits with code 3, query a known task ID or report that creation and billing are unconfirmed. A trace ID or new balance cannot resolve an unknown submission. An explicitly rejected attempt requires fresh authorization before retry. A failed preview never authorizes generation. -Read the video Skill even for read-only video model selection. When `omni_ref_video` exists, inspect its `who_am_i` model set before choosing or falling back. Text-only input does not imply `text_to_video` is the only option: required assets depend on the selected model's input and combination rules, not the tool's name. +Read [task recovery](references/task-recovery.md) for insufficient credits, continuation, missing results, or an expired link. For a request to purchase credits or change plans, explain the account limitation and keep generation paused. Do not initiate purchases or provide transaction links. Continue dependent tasks only after their prerequisite succeeds and the intended work can be identified. -Honor supplied asset roles, model, sound, ratio, and quality requirements. Ask only about missing information that materially changes the result. Prefer a user-specified available model; otherwise use these branches without maintaining fixed model lists: +## Results -| Live capability | Selection | -| --- | --- | -| The current entry point, or a new one supporting the same intent, returns a suitable newer-generation model | Prefer the newer model. Use live descriptions for quality or speed preferences and actual billing information for budget comparisons. | -| No suitable new model is returned, including a new tool exposing only existing models | Keep the existing entry point and its available `defaultModel`; if that default does not meet requirements, select a suitable model within its available set. Do not mention unopened models. | +Follow the selected runtime's [media and result rules](references/host-routing.md#media-and-result-boundaries). Give the task number and current status when helpful. Avoid parallel polling and duplicate media. If responsible for refresh, query only the original task within the [task recovery limits](references/task-recovery.md). -Determine newer generations from current descriptions and comparable versions within the same family, not tool count, a new tool, or speed-related names alone. If uncertain, use the existing branch without guessing. Include a new entry point only when it supports the user's asset roles and intent; never move models between tools. - -Both branches require live parameters and account visibility. Stop selection when capability reading fails. Required identity/product consistency, text, motion, and sound come before version preferences. Defaults cannot override assets, duration, speed, or budget; do not silently raise resolution/count or reduce requirements. "Best quality" is not synonymous with maximum resolution or fastest generation, and does not justify claims about uninspected results. - -Status, display, and link refresh are read-only. Explicit edits, variants, or video creation are new authorized steps: refresh and select the source work, then submit through the shared workflow. A dependent step must wait for a successful predecessor and a clearly selected work. - -## Runtime and delivery - -Require local shell access and Node.js 18+. Execute the pinned runtime from the CLI contract; explain the npm dependency before first use and respect execution approvals. Capture `who_am_i` stdout in a private temporary regular file and parse it after the process exits; CLI 0.2.1 may truncate a large capability response when stdout is a pipe. Delete the temporary file after reading and do not expose account identity fields. A zero exit code with incomplete JSON is a discovery failure. Start with `who_am_i`; if unauthorized, execute `login --skill-name kling-ai-cli --skill-version 1.1.2`, let the user complete browser consent, then verify identity. Account switching requires an explicit request and `logout` → `login` → `who_am_i`; stop on failure. Never read credentials or call HTTP/MCP directly. - -Submit each confirmed paid step at most once. An accepted task is not a completed work: require terminal success and a usable primary media URL of the requested type; a video cover is not a video. Preserve `generationId` and the CLI trace identifier. Use `query_tasks` for status and returned result links for delivery; this CLI does not mount an MCP App. Do not author Markdown image/video syntax, a separate media attachment, or a duplicate download link. Do not claim visual/audio inspection without actually inspecting the result. +Use the task number plus work index when reusing or reporting a result. Check task and work-level status, media type, and actual usable count. A video cover is preview art. Deliver available works and report partial counts when fewer succeed. Report the actual cost when returned. Claim visual or audio inspection only after inspecting that media.
Full technical diff · 3 changed fields
changed /description
"Generate images or videos with Kling AI in Codex, or handle existing tasks, conversation references, subject and motion libraries, credits, and account connections. Capabilities depend on the current account's live CLI response. Do not use for media analysis that does not call Kling."
"Plan Kling AI image prompts and video storyboards, prepare or submit authorized Kling generations, and manage Elements, saved motions, credits, known tasks, and account access."
changed /included_files
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 300
},
{
"relative_path": "references/asset-workflows.md",
"size_in_bytes": 7805
},
{
"relative_path": "references/audio-options.md",
"size_in_bytes": 1521
},
{
"relative_path": "references/capability-discovery.md",
"size_in_bytes": 2060
},
{
"relative_path": "references/cli-contract.md",
"size_in_bytes": 5801
},
{
"relative_path": "references/model-parameters.md",
"size_in_bytes": 1726
},
{
"relative_path": "references/output-options.md",
"size_in_bytes": 2204
},
{
"relative_path": "references/prompt-examples.md",
"size_in_bytes": 2643
},
{
"relative_path": "references/reference-inputs.md",
"size_in_bytes": 2788
},
{
"relative_path": "references/task-results.md",
"size_in_bytes": 2049
},
{
"relative_path": "references/tool-workflows.md",
"size_in_bytes": 2048
},
{
"relative_path": "references/troubleshooting.md",
"size_in_bytes": 1823
}
][
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 338
},
{
"relative_path": "references/cli-contract.md",
"size_in_bytes": 7730
},
{
"relative_path": "references/elements-motion-feedback.md",
"size_in_bytes": 7784
},
{
"relative_path": "references/generation-settings.md",
"size_in_bytes": 3641
},
{
"relative_path": "references/host-routing.md",
"size_in_bytes": 1656
},
{
"relative_path": "references/task-recovery.md",
"size_in_bytes": 2605
}
]changed /skill_md_contents
"---\nname: kling-ai\ndescription: Generate images or videos with Kling AI in Codex, or handle existing tasks, conversation references, subject and motion libraries, credits, and account connections. Capabilities depend on the current account's live CLI response. Do not use for media analysis that does not call Kling.\n---\n\n# Kling AI for Terminal\n\nUse only the pinned Global CLI in the [CLI contract](references/cli-contract.md). This is a local Skills-only plugin. The CLI owns browser OAuth; do not request or log credentials, private account fields, or signed URLs.\n\n## Load rules by request\n\n- Image generation, editing, posters, and reference-based creation: use `kling-ai-generate-image`.\n- Video generation, keyframes, omni references, motion control, and shot planning: first read the [video Skill](../kling-ai-generate-video/SKILL.md) and follow its entry-point routing before choosing a model. Reading only this core Skill and the submission workflow is insufficient.\n- Progress, existing results, or refreshed output links: read only [task results](references/task-results.md), without generation recommendations, model parameters, or creative references.\n- New generation, edits, or authorized retries: select through the relevant creative Skill, then follow [generation submission](references/tool-workflows.md). Execute dependent steps in order.\n- Subject library, motion library, or conversation references: read [asset workflows](references/asset-workflows.md). Read-only asset queries never submit generation.\n- Before generation, read [capability discovery](references/capability-discovery.md). After selecting an available model, use the [parameter module table](references/model-parameters.md) to load only supported rules needed for this request.\n- Authorization, upload, model, or service errors: read [troubleshooting](references/troubleshooting.md). Read [examples](references/prompt-examples.md) when examples are needed.\n\n## Account visibility and rollout\n\n- The current account's live `who_am_i` response governs models, parameters, specifications, input types, and combination limits. `tool_list` establishes tool availability and call structure; membership pages, tool descriptions, and static examples cannot override account capabilities.\n- Display, recommend, or call a model name only when the current `tool_list` exposes its tool and `who_am_i.availableModels` lists it under that tool. Tool counts, newly exposed omni tools, example names, and default-model fields are not substitutes for membership in that model set.\n- Compare \"latest\" only within available models supporting the required output type and intent. Do not mix image and video versions; `defaultModel` does not mean latest. Qualify the conclusion as the latest image/video model available to the current account. If no suitable new model is returned, use an available model without mentioning higher versions, unreleased names, allowlists, or better hidden models. Never fill gaps from Skills, snapshots, other accounts, or earlier sessions.\n- If a requested model is absent from filtered discovery, expand discovery as described in [capability discovery](references/capability-discovery.md). If it exists only for another output type, explain the mismatch and let the user choose whether to keep the requested medium or use the model's supported medium; do not switch silently. After complete discovery, report only that the current connection did not return the requested model, without repeating hidden names. Alternatives must be actually available and suitable.\n- Rediscover tools and models after reconnecting or changing account/environment. If discovery fails or model membership cannot be established, do not submit using a static fallback.\n\n## Creative and capability selection\n\nRead the video Skill even for read-only video model selection. When `omni_ref_video` exists, inspect its `who_am_i` model set before choosing or falling back. Text-only input does not imply `text_to_video` is the only option: required assets depend on the selected model's input and combination rules, not the tool's name.\n\nHonor supplied asset roles, model, sound, ratio, and quality requirements. Ask only about missing information that materially changes the result. Prefer a user-specified available model; otherwise use these branches without maintaining fixed model lists:\n\n| Live capability | Selection |\n| --- | --- |\n| The current entry point, or a new one supporting the same intent, returns a suitable newer-generation model | Prefer the newer model. Use live descriptions for quality or speed preferences and actual billing information for budget comparisons. |\n| No suitable new model is returned, including a new tool exposing only existing models | Keep the existing entry point and its available `defaultModel`; if that default does not meet requirements, select a suitable model within its available set. Do not mention unopened models. |\n\nDetermine newer generations from current descriptions and comparable versions within the same family, not tool count, a new tool, or speed-related names alone. If uncertain, use the existing branch without guessing. Include a new entry point only when it supports the user's asset roles and intent; never move models between tools.\n\nBoth branches require live parameters and account visibility. Stop selection when capability reading fails. Required identity/product consistency, text, motion, and sound come before version preferences. Defaults cannot override assets, duration, speed, or budget; do not silently raise resolution/count or reduce requirements. \"Best quality\" is not synonymous with maximum resolution or fastest generation, and does not justify claims about uninspected results.\n\nStatus, display, and link refresh are read-only. Explicit edits, variants, or video creation are new authorized steps: refresh and select the source work, then submit through the shared workflow. A dependent step must wait for a successful predecessor and a clearly selected work.\n\n## Runtime and delivery\n\nRequire local shell access and Node.js 18+. Execute the pinned runtime from the CLI contract; explain the npm dependency before first use and respect execution approvals. Capture `who_am_i` stdout in a private temporary regular file and parse it after the process exits; CLI 0.2.1 may truncate a large capability response when stdout is a pipe. Delete the temporary file after reading and do not expose account identity fields. A zero exit code with incomplete JSON is a discovery failure. Start with `who_am_i`; if unauthorized, execute `login --skill-name kling-ai-cli --skill-version 1.1.2`, let the user complete browser consent, then verify identity. Account switching requires an explicit request and `logout` → `login` → `who_am_i`; stop on failure. Never read credentials or call HTTP/MCP directly.\n\nSubmit each confirmed paid step at most once. An accepted task is not a completed work: require terminal success and a usable primary media URL of the requested type; a video cover is not a video. Preserve `generationId` and the CLI trace identifier. Use `query_tasks` for status and returned result links for delivery; this CLI does not mount an MCP App. Do not author Markdown image/video syntax, a separate media attachment, or a duplicate download link. Do not claim visual/audio inspection without actually inspecting the result.\n"
"---\nname: kling-ai\ndescription: Plan Kling AI image prompts and video storyboards, prepare or submit authorized Kling generations, and manage Elements, saved motions, credits, known tasks, and account access.\n---\n\n# Kling AI\n\n## Route the request\n\n- For prompt-only work, return the requested prompt or storyboard. For a missing required reference, ask for the asset and explain its role. Neither needs an account query.\n- For `text_to_image` or `image_to_image`, use the [image Skill](../kling-ai-generate-image/SKILL.md). For `text_to_video`, `image_to_video`, `omni_ref_video`, or `motion_control`, use the [video Skill](../kling-ai-generate-video/SKILL.md).\n- For Elements, browsing saved motions, or authorized feedback, use [the relevant tools](references/elements-motion-feedback.md). Resolve real IDs before use. An attachment or library operation does not authorize a generation.\n- Check credits through the selected runtime. Model availability comes from `who_am_i`. A direct status request runs `query_tasks` once for the known `generationId`.\n\n## Connection and account\n\nRead [host routing](references/host-routing.md) to select the runtime before any tool call, account check, or login. Keep one backend, account, and region per objective. Use logout or switch accounts only on request. If authorization is required, explain the return-to-client step and let the original login process finish. Only report login complete after `who_am_i` succeeds with an authenticated identity on that same connection.\n\n## Prepare and submit\n\n1. Follow [model discovery and request validation](references/generation-settings.md). Prefer directly attached images and map each reference to its live input slot. Preserve one UUIDv7 `taskTraceId` for the objective where supported. Retain the returned `generationId` as the task number.\n2. Show the final tool and model, prompt summary, output count, resolution, duration and ratio as applicable, reference roles, and requested audio, HDR or shot settings. Explain live billing rules, including per-second billing and input video duration when declared. A proposal ends here. Before generation, get explicit authorization for the final settings, reusing approval already given for these settings.\n3. Verify the actual request against the live schema. Immediately before submission, check the same account's balance. Pause if verification fails, the balance is nonpositive, or the service confirms it is insufficient for these settings. A positive balance without a live estimate provides no cost guarantee. Each authorization covers at most one submission attempt. Keep at most one non-terminal paid task for a dependent workflow.\n4. Preserve the returned task number and query only that task. If submission is ambiguous or the CLI exits with code 3, query a known task ID or report that creation and billing are unconfirmed. A trace ID or new balance cannot resolve an unknown submission. An explicitly rejected attempt requires fresh authorization before retry. A failed preview never authorizes generation.\n\nRead [task recovery](references/task-recovery.md) for insufficient credits, continuation, missing results, or an expired link. For a request to purchase credits or change plans, explain the account limitation and keep generation paused. Do not initiate purchases or provide transaction links. Continue dependent tasks only after their prerequisite succeeds and the intended work can be identified.\n\n## Results\n\nFollow the selected runtime's [media and result rules](references/host-routing.md#media-and-result-boundaries). Give the task number and current status when helpful. Avoid parallel polling and duplicate media. If responsible for refresh, query only the original task within the [task recovery limits](references/task-recovery.md).\n\nUse the task number plus work index when reusing or reporting a result. Check task and work-level status, media type, and actual usable count. A video cover is preview art. Deliver available works and report partial counts when fewer succeed. Report the actual cost when returned. Claim visual or audio inspection only after inspecting that media.\n"
Full snapshot data
{
"description": "Plan Kling AI image prompts and video storyboards, prepare or submit authorized Kling generations, and manage Elements, saved motions, credits, known tasks, and account access.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 338
},
{
"relative_path": "references/cli-contract.md",
"size_in_bytes": 7730
},
{
"relative_path": "references/elements-motion-feedback.md",
"size_in_bytes": 7784
},
{
"relative_path": "references/generation-settings.md",
"size_in_bytes": 3641
},
{
"relative_path": "references/host-routing.md",
"size_in_bytes": 1656
},
{
"relative_path": "references/task-recovery.md",
"size_in_bytes": 2605
}
],
"name": "kling-ai",
"skill_md_contents": "---\nname: kling-ai\ndescription: Plan Kling AI image prompts and video storyboards, prepare or submit authorized Kling generations, and manage Elements, saved motions, credits, known tasks, and account access.\n---\n\n# Kling AI\n\n## Route the request\n\n- For prompt-only work, return the requested prompt or storyboard. For a missing required reference, ask for the asset and explain its role. Neither needs an account query.\n- For `text_to_image` or `image_to_image`, use the [image Skill](../kling-ai-generate-image/SKILL.md). For `text_to_video`, `image_to_video`, `omni_ref_video`, or `motion_control`, use the [video Skill](../kling-ai-generate-video/SKILL.md).\n- For Elements, browsing saved motions, or authorized feedback, use [the relevant tools](references/elements-motion-feedback.md). Resolve real IDs before use. An attachment or library operation does not authorize a generation.\n- Check credits through the selected runtime. Model availability comes from `who_am_i`. A direct status request runs `query_tasks` once for the known `generationId`.\n\n## Connection and account\n\nRead [host routing](references/host-routing.md) to select the runtime before any tool call, account check, or login. Keep one backend, account, and region per objective. Use logout or switch accounts only on request. If authorization is required, explain the return-to-client step and let the original login process finish. Only report login complete after `who_am_i` succeeds with an authenticated identity on that same connection.\n\n## Prepare and submit\n\n1. Follow [model discovery and request validation](references/generation-settings.md). Prefer directly attached images and map each reference to its live input slot. Preserve one UUIDv7 `taskTraceId` for the objective where supported. Retain the returned `generationId` as the task number.\n2. Show the final tool and model, prompt summary, output count, resolution, duration and ratio as applicable, reference roles, and requested audio, HDR or shot settings. Explain live billing rules, including per-second billing and input video duration when declared. A proposal ends here. Before generation, get explicit authorization for the final settings, reusing approval already given for these settings.\n3. Verify the actual request against the live schema. Immediately before submission, check the same account's balance. Pause if verification fails, the balance is nonpositive, or the service confirms it is insufficient for these settings. A positive balance without a live estimate provides no cost guarantee. Each authorization covers at most one submission attempt. Keep at most one non-terminal paid task for a dependent workflow.\n4. Preserve the returned task number and query only that task. If submission is ambiguous or the CLI exits with code 3, query a known task ID or report that creation and billing are unconfirmed. A trace ID or new balance cannot resolve an unknown submission. An explicitly rejected attempt requires fresh authorization before retry. A failed preview never authorizes generation.\n\nRead [task recovery](references/task-recovery.md) for insufficient credits, continuation, missing results, or an expired link. For a request to purchase credits or change plans, explain the account limitation and keep generation paused. Do not initiate purchases or provide transaction links. Continue dependent tasks only after their prerequisite succeeds and the intended work can be identified.\n\n## Results\n\nFollow the selected runtime's [media and result rules](references/host-routing.md#media-and-result-boundaries). Give the task number and current status when helpful. Avoid parallel polling and duplicate media. If responsible for refresh, query only the original task within the [task recovery limits](references/task-recovery.md).\n\nUse the task number plus work index when reusing or reporting a result. Check task and work-level status, media type, and actual usable count. A video cover is preview art. Deliver available works and report partial counts when fewer succeed. Report the actual cost when returned. Claim visual or audio inspection only after inspecting that media.\n"
}SHA-256 of public snapshot: b895e3f2baf45d3b212335409cc549728ea7b1b80c94e930ff4a287f9ec0f8a8