Dlazy Merge

Audio/video merging tool for merging multiple video and audio tracks based on clips and timeline config, suitable for final cuts, scoring, and post-production.

Security Scan

The skill is an instruction-only wrapper for the dlazy CLI that is internally consistent with its stated purpose (merging audio/video via a cloud API); it asks the agent to run the CLI and upload media to dlazy's servers — behavior that matches the description.

Purpose & Capability

The name/description (audio/video merging) aligns with the declared requirements: npm/npx (used to run/install the CLI) and references to api.dlazy.com and oss.dlazy.com. Nothing requested (binaries, endpoints, config path) appears unrelated to a cloud-based media-merge CLI.

Instruction Scope

SKILL.md instructs the agent to run `dlazy merge` and informs that any local media paths provided will be uploaded to dlazy's media storage. This is coherent with the purpose, but it does mean the agent will transmit user media files to a third-party endpoint when those paths are supplied. The instructions also include prescriptive behavior for certain error codes (e.g., tell user to recharge or to set API key) which is reasonable but notable.

Install Mechanism

There is no platform install spec in the registry (instruction-only), but SKILL.md metadata suggests installing a pinned npm package (@dlazy/cli@1.0.6) or using npx. Using npx is lower-risk (no global install); a global `npm install -g` will execute third-party package code on the host — expected for a CLI but worth reviewing the package source before installing. Minor version mismatch across fields: the SKILL.md header/version (1.0.2) and registry metadata (1.0.4) vs install pin (1.0.6) — inconsistent but not necessarily malicious.

Credentials

The skill does not declare required environment variables but documents that the CLI uses an API key (stored in ~/.dlazy/config.json or via `DLAZY_API_KEY`). Requesting an API key for a hosted service is proportional to the task. Note the CLI will persist the key in the user's config directory if `dlazy auth set` is used — standard but important to be aware of.

Persistence & Privilege

always is false and the skill does not request system-wide changes. The skill may cause the CLI to create a per-user config file (~/.dlazy/config.json) to store the API key if the user runs `dlazy auth set`, which is expected behavior for a CLI client.

Assessment

This skill is a thin wrapper around the official dlazy CLI and is consistent with that purpose. Before installing or running it: (1) review the dlazy GitHub repo and npm package if you plan a global install; prefer `npx @dlazy/cli@...` if you want to avoid installing third-party code globally; (2) be aware any local media paths you pass will be uploaded to dlazy's storage (oss.dlazy.com) — don’t pass private/confidential media unless you trust the service and its policy; (3) the CLI stores your API key under your user config (~/.dlazy/config.json) if you run `dlazy auth set`; consider using per-invocation env var (DLAZY_API_KEY) if you prefer not to persist credentials; (4) note minor version inconsistencies in the skill metadata (SKILL.md vs registry vs install pin) — verify the exact package version you intend to run. If you need further assurance, ask for the package's exact publish tarball URL or a link to the release SHA to review code before installing.

English · 中文

Audio/video merging tool: merges multiple video and audio tracks based on clips and timeline config, suitable for final cuts, scoring, and post-production.

Trigger Keywords

• merge

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: Execute dlazy merge to get the result.

dlazy merge -h

Options:
  --videos <videos...>                 Videos [video: url or local path]
  --audios <audios...>                 Audios [audio: url or local path]
  --videoOptions <videoOptions...>     End
  --audioOptions <audioOptions...>     Track
  --resolution <resolution>            Resolution [default: auto] (choices: "auto", "1080P", "720P", "4K")
  --fps <fps>                          Frame Rate
  --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"
    ]
  }
}

Examples

dlazy merge --prompt 'prompt content' 

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.