分镜脚本 Storyboard#

English · 中文

storyboard to video, character animation, animated short, AI anime, multi-shot video — script, characters and shot prompts, ref-sheets and first/last frames, i2v shot videos, voice/TTS plus music/SFX/subtitles, then Remotion assembles and renders. Use for a multi-shot animated short with consistent characters.

Trigger Keywords#

• storyboard
• 分镜
• character animation
• 角色动画
• 动画短片
• multi-shot short

Authentication#

All requests require a dLazy API key. The recommended way to authenticate is:

bash

dlazy login

This runs a device-code flow (also works in remote shells) and automatically saves your API key to the local CLI config — no manual copy/paste required.

Alternative: Set the Key Manually#

If you already have an API key, you can save it directly:

bash

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 Manually#

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/dlazy-ai/cli
• Maintainer: dlazyai
• npm package: @dlazy/cli (pinned to 1.2.3 in this skill's install spec)
• Homepage: dlazy.com

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

bash

npx @dlazy/cli@1.2.3 <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.2.3). Review the GitHub source before installing.

How It Works#

This skill is a thin client over the dLazy hosted sandbox agent. When you invoke it:

• Your messages and options are sent to the dLazy API ( api.dlazy.com), which streams the agent's reply back to your terminal.
• Any local files you attach via --files are uploaded to dLazy's media storage ( files.dlazy.com) first, then referenced by url.
• Chat sessions are tracked per project so follow-up turns keep context; project ids come from dlazy projects list.

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#

This skill talks to the dlazy sandbox agent, pinned to the storyboard template — a project-scoped assistant that runs the template end-to-end across multiple turns.

Discover Projects#

bash

# List existing projects in your organization
dlazy projects list

Start or Continue#

bash

# Start a new project with this template
dlazy chat --skill storyboard --prompt "..."

# Continue an existing project (skips --skill)
dlazy chat --project <project_id> --prompt "..."

# Attach local files (uploaded to storage first)
dlazy chat --project <project_id> --prompt "Use this reference" --files ref.png

# Session control
dlazy chat --project <project_id> --clear      # drop the saved session, start fresh
dlazy chat --project <project_id> --compact    # compact the current session's context

On a TTY, dlazy chat stays interactive after the first turn — type follow-up messages, or exit to leave.

CRITICAL INSTRUCTION FOR AGENT:

1. For a new task, run dlazy chat --skill storyboard --prompt "...".
2. To continue earlier work, use --project <id> (find ids via dlazy projects list) — never pass both --skill and --project.
3. Always pass --prompt for non-interactive (no-TTY) runs.
4. Run dlazy chat -h to see every option.

Error Handling#

CodeError TypeExample Message401Unauthorized (No API Key)ok: false, code: "unauthorized", message: "API key is missing or invalid"501Missing required parametererror: required option '--prompt <prompt>' not specified502Local file read errorError: file not found: C:\path\to\your\file503API request failed (no balance)ok: false, code: "insufficient_balance"503API request failed (server error)HTTP status code error (500 server crash)504Asynchronous task execution failed=== Generation Failed === / {Specific error reason returned by backend}

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.