Dlazy Jimeng Omnihuman 1.5

Generate realistic digital human broadcast videos from portrait images and audio/text using Jimeng OmniHuman 1.5.

Security Scan

The skill is internally consistent with its stated purpose (a thin CLI client for the dLazy Jimeng OmniHuman service), but it will upload local media and store an API key locally — review provenance and be careful with sensitive files before using.

Purpose & Capability

Name, description, declared binaries (npm, npx), documented endpoints (api.dlazy.com, oss.dlazy.com), and install instructions all align with a CLI wrapper for a cloud media-generation service. The requested capabilities are expected for the described functionality.

Instruction Scope

The SKILL.md clearly instructs the agent to run the dlazy CLI which will upload any local image/audio paths to oss.dlazy.com and send prompts to api.dlazy.com. This is expected for a cloud generation service, but it does mean local files (which may contain PII or sensitive content) are transmitted to a third-party service. The skill does not instruct reading unrelated system files or environment secrets.

Install Mechanism

This is an instruction-only skill with no install spec executed by the agent. Metadata suggests installing @dlazy/cli from npm (or using npx) which is a normal, traceable registry package. There is no arbitrary download URL or archive extraction in the skill itself.

Credentials

No credentials are strictly required by the skill metadata; the SKILL.md documents an API key (DLAZY_API_KEY or via dlazy auth) which is appropriate for a cloud API client. No unrelated secrets or multiple unrelated credentials are requested.

Persistence & Privilege

The skill is not always-enabled and does not request elevated system-wide persistence. It does document that the CLI stores the API key in the user config (~/.dlazy/config.json). Also note the platform default allows autonomous invocation — the agent could run the CLI and cause uploads unless you restrict invocation or approve actions.

Assessment

This skill is coherent for calling a cloud video-generation API, but before installing/using it: 1) Review the GitHub repo and npm package (@dlazy/cli@1.0.6) to verify authenticity. 2) Be aware that any local images/audio you pass will be uploaded to dlazy's storage (oss.dlazy.com) — do not upload private or sensitive media. 3) The CLI stores your API key in ~/.dlazy/config.json (rotate/revoke keys as needed). If you prefer not to install globally, use the documented npx invocation to avoid persisting a binary. 4) Because agents can run skills autonomously by default, ensure you trust the agent's actions (or require user approval) before it invokes the CLI and uploads files.

English · 中文

Generate realistic digital human broadcast videos from portrait images and audio/text using Jimeng OmniHuman 1.5.

Trigger Keywords

• digital human
• jimeng omnihuman
• generate digital human video
• virtual human broadcast

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 jimeng-omnihuman-1.5 command to get results.

dlazy jimeng-omnihuman-1.5 -h

Options:
  --images <images...>                 Images [image: url or local path] (max 1)
  --audio <audio...>                   Audio [audio: url or local path] (max 1)
  --audioDuration <audioDuration>      Audio Duration
  --prompt <prompt>                    Prompt
  --resolution <resolution>            Resolution [default: 1080p] (choices: "720p", "1080p")
  --fast_mode <fast_mode>              Fast Mode [default: false]
  --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 jimeng-omnihuman-1.5 --prompt 'prompt text' --image '/path/to/image.png'

# complex call:
dlazy jimeng-omnihuman-1.5 --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.