Update to Kling AI for Terminal

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,40 +1,66 @@
 ---
 name: kling-ai-generate-video
-description: Generate Kling videos through the Global CLI from text, images, reusable Elements, or a motion video/saved motion; supports live audio and multi-shot options.
+description: Use Kling AI in Codex for text-to-video, image-to-video, omni references, keyframes, or motion control, including ads, short films, and single- or multi-shot creation. Use current account capabilities and the shared lifecycle for existing tasks.
 ---
 
-# Kling video generation
+# Kling AI video generation
 
-Follow [the core workflow](../kling-ai/SKILL.md) and [CLI contract](../kling-ai/references/cli-contract.md); submit each authorized step at most once. For reusable subjects or motion transfer, read [Element and motion rules](../kling-ai/references/elements-motion-feedback.md).
+Turn the request into coherent motion direction and one authorized remote generation. Follow the [core Skill](../kling-ai/SKILL.md) and [CLI contract](../kling-ai/references/cli-contract.md). Invoke the CLI only, with live command/model definitions.
 
-- Use `text_to_video` without controlling source media; `image_to_video` for image-based animation; `motion_control` for a subject driven by a video or saved motion. A single image with “animate this” normally supplies the first frame. Clarify roles only when materially ambiguous.
-- Pass image references with `--image` and a live-supported tail frame with `--tailImage`. Motion control needs a subject image and exactly one `--video` or `--motionId`; it always requires `--model`, never `--omni`.
-- Write the opening state, subject action, camera movement, and ending. Preserve identity/product facts. Keep shots within the supported duration; do not submit a task per shot unless separate outputs were requested.
-- Preserve the model's declared resolution default. Infer ratio/duration only from supported values and user intent. Omit it when undeclared; never reuse another model's flags.
-- When declared, map `prefer_multi_shots` to the planned shot structure. Set `enable_audio` true only for requested sound and otherwise false; use `enable_asmr` only for requested ASMR. Pass `audio_prompt` and `music_prompt` only when declared and requested. For motion control, source-motion constraints take precedence over ordinary video defaults.
-- Element binding requires both `<<<id>>>` and live-supported `--elements`; check tool-description restrictions as well as model parameters. Conflicting declarations stop submission.
-- Resolve references, check credits, submit, poll, and return results using the core workflow. Do not invent dialogue, claims, or an extra paid generation step.
+## Operating rules
 
-## Quality workflow
+- Use CLI browser OAuth. Never request or expose API keys, tokens, cookies, authorization headers, or upload tickets. Requested preview/download URLs may be delivered, but never logged or used as permanent identities.
+- Before paid generation, show the final tool/model, prompt summary, resolution or duration, ratio, count, reference roles, and actual billing information when available. Obtain explicit confirmation of these settings immediately before submission; an already confirmed unchanged step needs no repeated confirmation. If a live tool requires billing disclosure, explain its actual returned billing scope before submission without inventing prices or billing methods.
+- Submit each explicitly authorized step once. Run distinct tasks and cross-media dependencies serially through the shared workflow. Never automatically retry failed or ambiguous generation.
+- Discover live tools and definitions at runtime. Never hardcode model names, input roles, durations, or multi-shot fields from examples.
+- Prefer media attached directly in the conversation. Pass supported CLI resource flags for auto-upload; preserve input roles and order.
 
-Before every video generation, read [motion and shot planning](references/motion-and-shots.md). For product, UGC, explainer, multi-shot, or social-format requests, also read the relevant section of [scene patterns](references/scene-patterns.md). A simple single-shot animation does not need every scenario guide.
+Read [asset workflows](../kling-ai/references/asset-workflows.md) for subjects, motions, or reference preparation.
 
-1. Establish opening/ending states, duration, destination, reference roles, protected identity/product facts, and requested sound. Choose a live model that can support these requirements.
-2. Write in time order. Separate subject action, camera motion, and environmental response; describe direction, speed, amplitude, and an observable endpoint. Default to one primary action and one camera path for a short shot.
-3. For image animation, treat the first frame as the factual baseline. State what stays fixed and what moves. For motion control, preserve source-motion intent; do not invent conflicting choreography or camera moves.
-4. Use multiple shots only when requested or needed for changes in place, time, scale, or information. Give each shot one purpose and a duration; total timing must close. Preserve faces, clothing, product geometry, lighting, screen direction, and location anchors across cuts.
-5. Map dialogue, narration, music, ambience, or ASMR only when requested and supported. Never claim a completed voiced video when the model lacks the required sound controls, or invent testimonials, product claims, or copy.
-6. Before submission, check that actions fit the duration, camera moves do not conflict, the ending is achievable, and profile-specific continuity checks pass. Inspect output before claiming visual QA; report defects without automatically submitting another paid task.
+Before generation, obtain candidates through [capability discovery](../kling-ai/references/capability-discovery.md) and honor [account visibility](../kling-ai/SKILL.md#account-visibility-and-rollout). After selection, read the [parameter module table](../kling-ai/references/model-parameters.md), loading only applicable files. Submit through [generation submission](../kling-ai/references/tool-workflows.md). For existing tasks, go directly to [task results](../kling-ai/references/task-results.md).
 
-## Minimal calls
+## Load recommendations by capability
 
-These show arguments after the npm command prefix in the CLI contract. Replace `<model>` with the selected live model and use actual media paths. Append the shared telemetry flags.
+Existing-task queries skip recommendations and creative references. For new generation, read the current CLI `tool_list` response, then read exactly one file:
 
-```bash
-kling text_to_video --model <model> "Sunset over the sea; gentle waves, slow forward camera movement"
-kling image_to_video --model <model> --image ./first-frame.png "Animate the waves; preserve the horizon and composition"
-```
+| Tool discovery | Read |
+| --- | --- |
+| No `omni_ref_video` | [Standard video recommendations](references/standard-video.md) |
+| `omni_ref_video` exists | [Omni and new-model recommendations](references/omni-video.md), which branches further using actual model availability |
 
-For a requested ending frame, add `--tailImage ./last-frame.png` only when supported. Add `--duration` or `--aspectRatio` only with live-supported values. Describe multi-shot timing in the prompt and use declared shot/audio flags; a storyboard does not imply one paid task per shot. Motion transfer uses the separate `motion_control` workflow, not ordinary image animation.
+Then discover models through [CLI capability discovery](../kling-ai/references/capability-discovery.md). When `omni_ref_video` exists, ordinary text/image video requests must inspect its returned models together with the existing entry point in the full `who_am_i` response before deciding whether its models meet input requirements. Recommendation files govern selection; parameter modules govern payloads. Do not preload both files or branch on tool count. Discovery failure is not absence of a new tool: explain the inability to read capabilities and stop selection. Re-evaluate after reconnecting or switching account/environment; discard the invalidated branch.
 
-Before execution: resolve media roles → `who_am_i` → choose model and flags → `account` → submit once → `query_tasks <generationId>` → return selected `works[]` with task number and work index. A media failure does not authorize text-to-video fallback.
+## Workflow
+
+1. Select the tool/model pair using recommendations and live responses, preferring a requested available model. Use the module table for specifications, required/optional inputs, and sound; do not preload irrelevant modules.
+2. Read [motion and shot planning](references/motion-and-shots.md) for every new generation, edit, or variant. Select a profile governing motion budget, camera path, continuity anchors, and acceptance checks. Only read-only queries and authorized retries with unchanged parameters may skip it. Add [scene patterns](references/scene-patterns.md) when products, UGC, explainers, multi-shot stories, or social formats need further decisions. A complete existing plan does not replace motion planning.
+3. Internally establish intended use, protected subjects, and target action. Ask only about blocking assets/dialogue or conflicting requirements; choose ordinary camera movement, lighting, and unspecified options reasonably instead of requiring a questionnaire.
+4. Write a motion-centered prompt covering subject/camera/environment movement, rhythm, continuity, and protected elements. Translate abstract quality into lighting, materials, depth, and composition.
+5. Validate parameters, check credits, and submit once through the shared workflow. After acceptance, follow task results. Do not generate comparison samples automatically or create an unrequested final version after a preview.
+
+## Creative constraints
+
+Load applicable modules for reference roles, frame order, combination caps, sound controls, and output specifications. Never silently discard unsupported inputs, convert them to text, guess fields/models/enums, or switch account/endpoint to probe availability.
+
+Focus the prompt on requested action and visuals. Do not add unrequested narration, on-screen text, characters, or claims. Match single/multi-shot structure to narrative intent and supported parameters; do not split into multiple paid tasks merely to add shots.
+
+## Quality gates
+
+Before submission, align duration, ratio, shot structure, and sound switches with the prompt. Actions need a beginning, progression, and end; frames need plausible transitions; multi-shot continuity must be explicit. Each ad/explainer shot needs a communication purpose.
+
+When the host can inspect video, check opening, key action, transitions, and ending for identity drift, deformation, flicker, discontinuity, and cropping. Listen to required dialogue/audio for wording, lip sync, and original-sound intent. Covers or still frames cannot establish motion or audio quality. Follow [shared inspection rules](../kling-ai/references/task-results.md).
+
+## Failure handling
+
+- Authorization: run the pinned CLI `login`, then verify with `who_am_i`.
+- Invalid model/parameters: refresh capabilities and prepare a correction without automatically resubmitting a prior generation.
+- Insufficient credits: explain and stop until recharged; do not retry automatically.
+- Lost response: recover or report unknown through task results; never replay blindly.
+- Provider failure: summarize safely, retain the task ID, and do not automatically resubmit.
+
+
+Submit at most once per confirmed paid step. Runtime, polling, and link delivery follow the core CLI workflow.
+
+## CLI input mapping
+
+Always pass `--model` from the selected command's live set. `omni_ref_video` uses repeatable `--image`, `--video`, `--audio`, or declared named `--input`; it can be text-only when the model permits. For `image_to_video`, choose either `--image`/`--tailImage` or named `--input`, never both forms. `motion_control` needs a subject `--image` and exactly one `--video` or `--motionId`. CLI 0.2.1 removed `--omni` and `--flash`; do not use them. See the CLI contract before constructing a command.