Dlazy Kling Audio Clone

Generate customized speech that highly restores the timbre by uploading reference audio using Kling Audio Clone.

Security Scan

The skill's declared purpose (a thin CLI client for dlazy's Kling audio-clone service) matches its instructions and requirements; nothing in the package suggests hidden or unrelated behavior.

Purpose & Capability

Name/description align with the provided instructions: it wraps the dlazy CLI and interacts with dlazy API endpoints. Requiring npm/npx to run or install the CLI is proportionate to the stated purpose.

Instruction Scope

SKILL.md instructs the agent to run the dlazy CLI and to upload local audio files (if given) to dlazy's media host (oss.dlazy.com). It also instructs storing or providing an API key (via dlazy auth set or DLAZY_API_KEY). These behaviors are expected for a cloud audio-clone CLI but mean user audio and an API key will be sent to an external service — the agent is not instructed to read arbitrary unrelated system files.

Install Mechanism

This is an instruction-only skill with no install spec in the registry; the SKILL.md suggests installing a pinned npm package (@dlazy/cli@1.0.6) or using npx. Using npm/npx and a GitHub/npm source is a standard, low-risk install pattern; no arbitrary download URLs or archives are present in the instructions.

Credentials

The skill requires a dLazy API key to operate (documented in SKILL.md) and can accept it via dlazy auth set or the DLAZY_API_KEY env var. The registry metadata lists no required env vars — this is reasonable because the key is user-provided, but users should be aware that the CLI will persist the key to ~/.dlazy/config.json by default.

Persistence & Privilege

always:false and normal autonomous invocation are used. The skill does not request elevated persistent privileges or system-wide changes. The only persistence noted is the CLI's normal behavior of storing its own config (API key) in the user's config directory, which is expected.

Assessment

This skill is a thin wrapper around dlazy's official CLI. Before installing or using it: (1) Review the upstream GitHub repo and npm package (@dlazy/cli@1.0.6) if you plan to install globally; prefer npx for one-off use to avoid installing a global binary. (2) Understand that any local audio files you provide will be uploaded to dlazy's servers (oss.dlazy.com) and outputs are hosted externally — do not upload material you do not want transmitted. (3) The CLI stores your API key in ~/.dlazy/config.json by default; only use keys you trust and rotate/revoke them if needed. (4) Check dlazy's privacy and terms for voice-cloning implications (consent, legal/regulatory considerations). If you are uncomfortable with external uploads or storing a key locally, do not install or use the skill.

English · 中文

Generate customized speech that highly restores the timbre by uploading reference audio using Kling Audio Clone.

Trigger Keywords

• kling audio clone
• clone voice
• custom speech
• audio cloning

Authentication

All requests require a dLazy API key, configured through the CLI:

dlazy auth set YOUR_API_KEY

The CLI saves the key in your user config directory (~/.dlazy/config.json on macOS/Linux, %USERPROFILE%\.dlazy\config.json on Windows), with file permissions restricted to your OS user account. You can also supply the key per-invocation via the DLAZY_API_KEY environment variable.

Getting Your API Key

1. Sign in or create an account at dlazy.com
2. Go to dlazy.com/dashboard/organization/api-key
3. Copy the key shown in the API Key section

Each key is scoped to your dLazy organization and can be rotated or revoked at any time from the same dashboard.

About & Provenance

• CLI source code: github.com/dlazyai/cli
• Maintainer: dlazyai
• npm package: @dlazy/cli (pinned to 1.0.6 in this skill's install spec)
• Homepage: dlazy.com

You can install on demand without persisting a global binary by running:

npx @dlazy/cli@1.0.6 <command>

Or, if you prefer a global install, the skill's metadata.clawdbot.install field declares the exact pinned version (npm install -g @dlazy/cli@1.0.6). Review the GitHub source before installing.

How It Works

This skill is a thin client over the dLazy hosted API. When you invoke it:

• Prompts and parameters you provide are sent to the dLazy API endpoint (api.dlazy.com) for inference.
• Any local file paths you pass to image / video / audio fields are uploaded to dLazy's media storage (oss.dlazy.com) so the model can read them — the same flow as any cloud-based generation API.
• Generated output URLs returned by the API are hosted on oss.dlazy.com.

This is the standard SaaS pattern; the skill itself does not access network or filesystem resources beyond what the dLazy CLI already handles. See dlazy.com for the full service terms.

Usage

CRITICAL INSTRUCTION FOR AGENT: Run the dlazy kling-audio-clone command to get results.

dlazy kling-audio-clone -h

Options:
  --audio_url <audio_url>              Audio URL [audio: url or local path]
  --name <name>                        Name
  --input <spec>                       JSON payload: inline string, @file, or - (stdin)
  --dry-run                            Print payload + cost estimate without calling API
  --no-wait                            Return generateId immediately for async tasks
  --timeout <seconds>                  Max seconds to wait for async completion (default: "1800")
  -h, --help                           display help for command

Output Format

{
  "ok": true,
  "kind": "urls",
  "data": {
    "urls": [
      "https://oss.dlazy.com/result.mp4"
    ]
  }
}

Command Examples

# basic call:
dlazy kling-audio-clone --prompt 'prompt text'

# complex call:
dlazy kling-audio-clone --prompt 'prompt text'

Error Handling

Code	Error Type	Example Message
401	Unauthorized (No API Key)	ok: false, code: "unauthorized", message: "API key is missing or invalid"
501	Missing required parameter	error: required option '--prompt <prompt>' not specified
502	Local file read error	Error: Image file/Video file not found: C:\path\to\your\file
503	API request failed (no balance)	ok: false, code: "insufficient_balance"
503	API request failed (server error)	HTTP status code error (500 server crash)
504	Asynchronous task execution failed	=== Generation Failed === / {Specific error reason returned by backend, for example "Prompt violates safety policy"}

AGENT CRITICAL INSTRUCTION:

1. If the execution result returns code: "insufficient_balance", you MUST explicitly inform the user that their credits are insufficient and guide them to recharge: https://dlazy.com/dashboard/organization/settings?tab=credits
2. If the execution result returns code: "unauthorized" or indicates missing API key, you MUST inform the user to get their API key from https://dlazy.com/dashboard/organization/api-key and save it using dlazy auth set <key> and resume the task.

Tips

Visit https://dlazy.com for more information.