Dlazy Vidu Audio Clone

Clone voice and generate new text reading audio with one click using Vidu Audio Clone.

Security Scan

The skill is a thin wrapper around a third‑party npm CLI for dLazy voice cloning (reasonable for its purpose) but the registry metadata omits that an API key is required and the SKILL.md directs installing/running an npm package that will store a secret on disk — review before installing or granting credentials.

Purpose & Capability

Name and description align with the instructions: this is a thin client for the dLazy Vidu audio clone service. Requiring npm/npx is coherent because the skill depends on an npm CLI. However, the SKILL.md explicitly requires a dLazy API key (and documents storing it in ~/.dlazy/config.json or using DLAZY_API_KEY), while the registry metadata lists no required env vars or primary credential — a mismatch between claimed requirements and declared requirements.

Instruction Scope

The SKILL.md stays on task: it tells the agent to run the dlazy vidu-audio-clone CLI, describes that local audio files will be uploaded to oss.dlazy.com, and instructs how to handle common errors. It does not instruct the agent to read unrelated files or exfiltrate arbitrary data. It does, however, mandate agent behavior in error cases (explicit 'MUST' guidance), which is prescriptive but within the skill's scope.

Install Mechanism

There is no registry install spec, but the SKILL.md metadata recommends installing a pinned npm package (@dlazy/cli@1.0.6) or using npx. That is a plausible install path for a CLI, but installing npm packages executes remote code and introduces typical supply‑chain risk. Prefer using the npx alternative or auditing the GitHub/npm source before a global install.

Credentials

The SKILL.md requires a dLazy API key (either via dlazy auth set or DLAZY_API_KEY) and documents storing it in ~/.dlazy/config.json, but the skill metadata in the registry declares no required env vars or a primary credential. This omission is important: the skill needs a sensitive secret to function and will persist it to disk. No unrelated credentials are requested, but the credential requirement should be declared in registry metadata.

Persistence & Privilege

always is false and the skill does not request elevated or system‑wide privileges. The only persistent side effect described is the CLI storing its own config (~/.dlazy/config.json), which is expected behavior for a CLI that stores an API key.

What to consider before installing

This skill appears to be a wrapper for the dLazy CLI to perform voice cloning and is otherwise coherent, but take these precautions before installing or using it: - Expect to provide a dLazy API key (DLAZY_API_KEY or run `dlazy auth set <key>`). The registry metadata did not declare this — confirm you are comfortable with that secret being used and stored. - The CLI will upload any local audio files you pass to dlazy's servers (oss.dlazy.com). Do not pass private/sensitive audio you do not want uploaded. - The SKILL.md recommends installing @dlazy/cli from npm; installing npm packages runs remote code. Prefer running via `npx @dlazy/cli@1.0.6` to avoid a global install, and review the GitHub/npm source (https://github.com/dlazyai/cli and https://www.npmjs.com/package/@dlazy/cli) before trusting it. - Confirm legal and ethical permissions for cloning any voice you provide. - If you need higher assurance, ask the publisher to update the registry metadata to declare the required API key (primaryEnv) and to include a formal install spec, or request a reproducible audit of the npm package version pinned by the skill.

English · 中文

Clone voice and generate new text reading audio with one click using Vidu Audio Clone.

Trigger Keywords

• vidu audio clone
• clone voice
• custom speech

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 vidu-audio-clone command to get results.

dlazy vidu-audio-clone -h

Options:
  --audio_url <audio_url>              Audio URL [audio: url or local path]
  --prompt <prompt>                    Prompt
  --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 vidu-audio-clone --prompt 'prompt text'

# complex call:
dlazy vidu-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.