What problem does it solve? Integrating the official Kling API is error-prone because it uses multiple task protocols (Classic, Turbo, Omni) with different ID paths, status values, and result structures, and it is easily confused with the fal.ai Kling gateway. This Skill provides the authoritative guidance needed before calling any kling_official_* tool so requests are authenticated, parsed, and billed correctly. ## Core Features & Use Cases - Provider Disambiguation: Clearly separates the official Kling API (KLING_API_KEY, Bearer auth) from the fal.ai gateway (FAL_KEY), preventing silent provider switching. - Protocol-Specific Parsing: Documents Classic (data.task_id, succeed) versus Turbo (data.id, succeeded) task protocols so parsers never guess between formats. - Full Capability Coverage: Covers text/image/reference-to-video, image generation and Omni references, TTS with explicit voice_id, avatar generation, and two-step lip sync with face identification. - Error & Cost Governance: Defines which error codes must not be retried (auth, balance, permission, safety) and requires non-zero cost estimates on paid results. - Use Case: When building an OpenMontage pipeline that generates a talking-avatar video, use this Skill to correctly call kling_avatar with a base64-encoded image and audio_id, then poll the Classic task protocol until the status is succeed. ## Quick Start Ask the AI to generate a video with the kling_official_video tool using the official Kling API and your KLING_API_KEY.