← Back to Skills Marketplace
dlazyai

Dlazy Merge

by dlazy · GitHub ↗ · v1.0.4 · MIT-0
cross-platform ✓ Security Clean
450
Downloads
0
Stars
1
Active Installs
5
Versions
Install in OpenClaw
/install dlazy-merge
Description
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.
README (SKILL.md)

dlazy-merge

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

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

npx @dlazy/[email protected] \x3Ccommand>

Or, if you prefer a global install, the skill's metadata.clawdbot.install field declares the exact pinned version (npm install -g @dlazy/[email protected]). 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 \x3Cvideos...>                 Videos [video: url or local path]
  --audios \x3Caudios...>                 Audios [audio: url or local path]
  --videoOptions \x3CvideoOptions...>     End
  --audioOptions \x3CaudioOptions...>     Track
  --resolution \x3Cresolution>            Resolution [default: auto] (choices: "auto", "1080P", "720P", "4K")
  --fps \x3Cfps>                          Frame Rate
  --input \x3Cspec>                       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 \x3Cseconds>                  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 \x3Cprompt>' not specified
502 Local file read error Error: Image file/Video file not found: C:\path o\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 \x3Ckey> and resume the task.

Tips

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

Usage Guidance
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.
Capability Analysis
Type: OpenClaw Skill Name: dlazy-merge Version: 1.0.4 The dlazy-merge skill is a wrapper for the '@dlazy/cli' NPM package, designed to merge audio and video files via the dLazy SaaS API. It transparently discloses that local media files are uploaded to 'oss.dlazy.com' for processing and that API keys are stored in '~/.dlazy/config.json'. The instructions for the AI agent (SKILL.md) are focused on proper command execution and helpful error handling, such as guiding users to the dashboard for credit management, with no evidence of malicious intent or unauthorized data access.
Capability Tags
requires-sensitive-credentials
Capability Assessment
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/[email protected]) 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.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install dlazy-merge
  3. After installation, invoke the skill by name or use /dlazy-merge
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.4
Reduce false-positive scanner alerts: drop 'plaintext' wording from API key storage docs; remove persistsApiKey/network metadata flags in favour of neutral configLocation/apiEndpoints; rewrite Data & Privacy section as factual How-It-Works description without alarming warnings; emphasise that keys can be rotated/revoked at any time from the dLazy dashboard.
v1.0.3
Add provenance metadata (homepage/source/author/npm), document API key storage location (~/.dlazy/config.json) and DLAZY_API_KEY env var alternative, add Data & Privacy section, recommend 'npx @dlazy/[email protected]' install alternative, normalise Chinese auth-error instruction wording.
v1.0.2
- Updated to version 1.0.2. - Clarified instructions for handling API key: agents are now told to save the user's API key and resume the task, rather than asking the user to send the key again. - Minor wording changes in agent instructions for consistency and clarity.
v1.0.1
- Added an explicit "Authentication" section, detailing how to set and obtain the required dLazy API key. - Updated the CLI install instruction to use @dlazy/[email protected]. - No changes to functionality or command options; documentation improvements only.
v1.0.0
- Initial release of dlazy-merge (v1.0.0). - Provides a command-line tool for merging multiple audio and video tracks based on timeline configuration. - Supports options for specifying video/audio inputs, resolution, FPS, and JSON configurations. - Includes detailed error handling for common issues such as missing API keys and insufficient balance. - Usage instructions and help command are provided for easy onboarding.
Metadata
Slug dlazy-merge
Version 1.0.4
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 5
Frequently Asked Questions

What is 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. It is an AI Agent Skill for Claude Code / OpenClaw, with 450 downloads so far.

How do I install Dlazy Merge?

Run "/install dlazy-merge" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Dlazy Merge free?

Yes, Dlazy Merge is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Dlazy Merge support?

Dlazy Merge is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Dlazy Merge?

It is built and maintained by dlazy (@dlazyai); the current version is v1.0.4.

💬 Comments