Dlazy Veo 3.1

Generate high-quality cinematic effects videos with Google Veo 3.1.

Security Scan

The skill is a thin CLI client for the dLazy video generation service and its declared requirements and instructions are consistent with that purpose.

Purpose & Capability

The skill advertises using 'Google Veo 3.1' but all runtime artifacts (CLI package @dlazy/cli, api.dlazy.com, oss.dlazy.com) point to dLazy as the provider; this may be a naming/marketing mismatch but the requested binaries (npm/npx) and CLI installation are coherent with a Node-based thin client.

Instruction Scope

SKILL.md instructs the agent to run the dLazy CLI (dlazy veo-3.1). It explicitly states that local files specified by the user are uploaded to dLazy's media storage; there are no instructions to read unrelated system files, probe other credentials, or exfiltrate data to unexpected endpoints.

Install Mechanism

No install spec is enforced by the registry (instruction-only skill), but the skill metadata recommends installing a pinned npm package (@dlazy/cli@1.0.6) or using npx. This is a standard public-registry install pattern and not an arbitrary URL download. You should still review the GitHub/npm source before installing.

Credentials

The skill legitimately requires a dLazy API key (saved in ~/.dlazy/config.json or supplied via DLAZY_API_KEY). The registry lists no required env vars, which is acceptable, but the doc's mention of DLAZY_API_KEY means the agent or user could provide that variable — this is proportionate to the service's needs and there are no unrelated secrets requested.

Persistence & Privilege

always:false and autonomous invocation is allowed (platform default). The skill does not request system-wide privileges or modifications to other skills. The CLI will store the API key in its own user-scoped config (~/.dlazy/config.json), which is normal for a CLI client.

Assessment

This appears to be a legitimate thin client for dLazy's video API. Before installing or using it: 1) inspect the GitHub repo and npm package referenced (@dlazy/cli@1.0.6) to confirm source code matches the published package and there are no unexpected behaviors; 2) prefer using npx for one-off runs to avoid installing a global binary; 3) avoid uploading sensitive local files (they will be sent to oss.dlazy.com); 4) supply the API key only if you trust the service, verify file permission on ~/.dlazy/config.json after saving, and rotate/revoke the key if you later stop using the skill; 5) note the marketing mention of 'Google Veo 3.1' — confirm with dLazy whether that attribution is accurate if that matters to you.

English · 中文

Generate high-quality cinematic effects videos with Google Veo 3.1.

Trigger Keywords

• veo 3.1
• generate video
• text to video, image to video

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 veo-3.1 command to get results.

dlazy veo-3.1 -h

Options:
  --prompt <prompt>                    Prompt
  --images <images...>                 Images [image: url or local path] (max 3) [default: ] [only when generation_mode="components"]
  --generation_mode <generation_mode>  Generation Mode [default: frames] (choices: "frames", "components")
  --firstFrame <firstFrame>            First Frame [image: url or local path] [only when generation_mode="frames"]
  --lastFrame <lastFrame>              Last Frame [image: url or local path] [only when generation_mode="frames"]
  --size <size>                        Size [default: 16:9] (choices: "16:9", "9:16")
  --resolution <resolution>            Resolution [default: 720P] (choices: "720P", "1080P", "4K")
  --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 veo-3.1 --prompt 'prompt text' --image '/path/to/image.png'

# complex call:
dlazy veo-3.1 --prompt 'prompt text' --image 'https://oss.dlazy.com/image.png'

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.