kling-ai
Handle Kling AI / 可灵 requests in Claude Code, including prompt-only planning, missing-asset next steps, generation preparation and approved image/video creation. Route creative work to the dedicated Skills; manage Elements, motion library, uploads, credits, existing tasks and account switching through the remote MCP.
klingai-tech · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add klingai-tech/claude-plugin --skill kling-aiAbout this skill
name: kling-ai description: Handle Kling AI / 可灵 requests in Claude Code, including prompt-only planning, missing-asset next steps, generation preparation and approved image/video creation. Route creative work to the dedicated Skills; manage Elements, motion library, uploads, credits, existing tasks and account switching through the remote MCP. license: MIT
Kling AI for Claude Code
Use only the remote Global MCP configured by this plugin: https://kling.ai/mcp/plugin. .mcp.json is the connection source of truth. Do not switch regions, register a second Kling MCP, or start or depend on a local MCP server.
Request routing
- First determine the current deliverable: creative writing only, final generation settings awaiting approval, authorized submission, or an existing-task query. Creative writing ends with the requested prompt/plan. Final settings require live capability preparation; only an approved submission advances to generation.
- For image creation or editing, follow kling-ai-generate-image: text-to-image, image-to-image, posters, product photos, portraits, covers, and variants.
- For video prompts, storyboards, missing-image next steps, generation, model selection or motion transfer, follow kling-ai-generate-video. For generation preparation, discover relevant entry points including pure-text omni; prompt-only work and requesting a missing asset do not need account queries.
- Keep uploads, Elements, motion-library browsing, account operations, credit checks, and task status in this Skill. It also supplies the shared connection, billing, submission, and result rules for both generation Skills.
- Motion library: browse with
motion_library_list. Resolve the selected motion, then follow the video Skill formotion_controlwith a subject image and exactly one motion source. - Subject library / Elements: use
element_list,element_get,element_create,element_update, orelement_deletefor the requested operation. Resolve real IDs before reuse. - Account and credits: use
query_membership_and_credits; model capabilities come fromwho_am_i. - Existing tasks: use
query_taskswith a knowngenerationId. A status or library request never creates a generation. - Sign-out or account switching: act only on an explicit user request, stay on the Global endpoint, and complete native Claude Code OAuth before further Kling calls.
Call only tools present in the live tool list. An attachment alone does not determine its role; clarify only when first frame, tail frame, identity/product reference, editable source, motion source, or style reference would materially change the request.
Read asset workflows for Elements, the motion library, or uploads. Before generation, follow capability discovery, then model parameters, tool workflows, and the MCP contract. Use prompt examples for creative direction and troubleshooting after a failure.
Connection and task identity
- Use OAuth through Claude Code's native MCP connection flow (
/mcp, then the plugin'skling-aiserver). Never request an API key, token, cookie, authorization header, or credential file. Never log private account fields, upload tickets, or signed URLs. - Let Claude Code manage OAuth discovery, client registration, and credentials through its native MCP flow. This plugin does not configure a custom OAuth client name; do not invent registration overrides or block authorization because the host cannot set one. If the real OAuth flow fails, report the sanitized error and follow troubleshooting.
- Create one UUIDv7
taskTraceIdfor each unrelated new objective. Reuse it across discovery, upload, generation, and querying for that objective wherever the live tool accepts it. - Preserve exact returned IDs. Present
generationIdas the task number; exposetaskTraceIdonly when troubleshooting requires it.
Billing and single submission
- Image, video, and motion generation consume credits. Call
who_am_iduring preparation and select only models returned in the current account'savailableModelsfor the chosen tool, with their declared arguments, inputs, and combination limits. Follow capability discovery for cross-tool selection and refresh stale definitions before proceeding. Do not infer model access from a tool's existence, membership tier, or static examples. - Show the final workflow, model, prompt summary, duration/resolution, aspect ratio, output count, and reference roles. Honor existing explicit authorization for the same unsubmitted intent and unchanged final settings; otherwise obtain confirmation before submission. An upload, library operation, or credit check is not generation approval.
- Include any billing disclosure required by the live model/tool in those final settings. For omni reference that declares per-second billing with input video duration included, explain both facts before submission; output duration alone is not the total billed duration. Do not invent a rate or total credit estimate.
- Submit at most once per approved intent. Never automatically retry or silently change models after a failure, timeout, ambiguous response, or rendering problem.
- Do not save an Element automatically during ordinary generation. Element writes and deletion must follow the user's explicit request as described in asset workflows.
Generation and results
- Resolve reference roles, Elements, and motion sources; prepare local media before submission. Use the returned provider references exactly as the selected live schema requires.
- Confirm the final billable settings, then call the chosen generation tool once. A m