Dlazy Keling Sfx

Generate matching scene sound effects based on text descriptions or video frames using Kling SFX.

Security Scan

The skill's requests and instructions are consistent with a CLI that uploads media to a hosted SaaS API to generate sound effects, but there are small metadata omissions and normal risks from running an external npm CLI that you should understand first.

Purpose & Capability

Name/description match the behavior: the skill is a thin client for the dLazy Kling SFX service and requires the dLazy CLI (npm/npx). Declared required binaries (npm, npx) are appropriate. The skill relies on networked API and media uploads to api.dlazy.com / oss.dlazy.com as expected.

Instruction Scope

SKILL.md limits actions to running the dlazy CLI and uploading any user-supplied media; it does not instruct the agent to read unrelated system files or exfiltrate arbitrary data. It does reference the CLI's config path (~/.dlazy/config.json) only to explain where the API key is stored, not to instruct reading other local state.

Install Mechanism

This is an instruction-only skill (no install spec in registry), but the README recommends using npm install -g @dlazy/cli@1.0.6 or npx @dlazy/cli@1.0.6. Installing/running from npm is a common pattern; npx executes code from the npm registry (moderate risk). The recommended package is on npm and points to a GitHub repo—review source before installing globally.

Credentials

The service requires a dLazy API key (can be set with dlazy auth or via DLAZY_API_KEY). That credential is proportional to the skill's purpose, but the top-level registry metadata lists no required env vars or primary credential — a minor inconsistency that could confuse users or automation expecting required env declarations.

Persistence & Privilege

The skill is not always-enabled, does not claim elevated persistence, and does not request changes to other skills or system-wide settings. Installing the CLI globally would write a binary to the system (normal for npm installs) but this is a user action.

Assessment

Before installing or invoking this skill: (1) Know that any local video/audio files you pass will be uploaded to dlazy's OSS domain — do not send sensitive or private files. (2) The service requires a dLazy API key (can be set via dlazy auth or DLAZY_API_KEY); the registry metadata does not list this required key, so supply it manually. (3) Prefer using npx for one-off runs to avoid globally installing a third-party CLI; if you install globally, review the GitHub repo and npm package source first. (4) The CLI will store your API key in ~/.dlazy/config.json (or %USERPROFILE%\.dlazy\config.json on Windows) — ensure that file permissions are appropriate and rotate keys if needed. (5) Review dLazy's terms and the CLI source if you run it in a shared or production environment. If you want stronger assurance, ask the skill author to declare the API key in the metadata and provide a link to a reproducible audit (SHA sums or source commit) for the npm package version pinned in the skill.

English · 中文

Generate matching scene sound effects based on text descriptions or video frames using Kling SFX.

Trigger Keywords

• kling sfx
• generate sound effects
• video dubbing

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 keling-sfx command to get results.

dlazy keling-sfx -h

Options:
  --prompt <prompt>                    Prompt [default: ] [only when videos is empty]
  --videos <videos...>                 Videos [video: url or local path] (max 1) [default: ]
  --duration <duration>                Duration (s) [default: 5] (choices: "3", "4", "5", "6", "7", "8", "9", "10") [only when videos is empty]
  --prompt_mode <prompt_mode>          Prompt Mode [default: 音效] (choices: "音效", "配乐", "无") [only when videos non-empty]
  --sound_effect_prompt <sound_effect_prompt>Sound Effect Prompt [default: ] [only when videos non-empty] [hidden when prompt_mode!="音效"]
  --bgm_prompt <bgm_prompt>            BGM Prompt [default: ] [only when videos non-empty] [hidden when prompt_mode!="配乐"]
  --asmr_mode <asmr_mode>              ASMR Mode [default: false] [only when videos non-empty]
  --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 keling-sfx --prompt 'prompt text'

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