Executes a plan's flat shape list end-to-end. Each shape is dispatched through /api/ai/tool in dependency order (resolved from shape://name: refs); upstream outputs are substituted into downstream input, and promptRefs text is prepended to the consumer's prompt. IMPORTANT: only shapes whose props.status is idle actually run — any other status (completed / failed / processing) is treated as already-done and its existing props.url is reused as the producer output. To resume after a failure, set the failed shapes (and any you want re-run) back to idle, optionally edit their props.input, then call execute again.
All requests require a dLazy API key. The recommended way to authenticate is:
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.
If you already have an API key, you can save it directly:
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.
Each key is scoped to your dLazy organization and can be rotated or revoked at any time from the same dashboard.
@dlazy/cli (pinned to 1.0.9 in this skill's install spec)
You can install on demand without persisting a global binary by running:
npx @dlazy/cli@1.0.9 <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.9). Review the GitHub source before installing.
This skill is a thin client over the dLazy hosted API. When you invoke it:
api.dlazy.com) for inference.
files.dlazy.com) so the model can read them — the same flow as any cloud-based generation API.
files.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.
CRITICAL INSTRUCTION FOR AGENT:
Execute dlazy execute to get the result.
dlazy execute -h
Options:
--shapes [shapes...] Flat shape list to execute (typically plan.shapes). Cross-shape references inside `props.input` use either `shape://name:<name>` (resolves to the producer matching `props.name`) or `shape://shape:<id>` (resolves to the producer matching `id`); refs whose target is not in this array are dropped as if the param were absent. Each shape's `props.status` controls scheduling: only `idle` shapes run; shapes with any other status are treated as already-done and their `props.url` is reused as the producer output for downstream refs. To resume a failed run, set the failed/affected shapes back to `idle` (optionally edit their `props.input`) and call execute again.
--projectId [projectId] Optional project id forwarded to every downstream tool call (used for asset scoping and credit accounting).
--sessionId [sessionId] Optional execution session id; pass the same value across resume attempts so logs can be correlated.
--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
> Any flag also accepts pipe references — - (auto-pick from upstream stdin), @N (n-th output), @N.path (jsonpath into output), @* (all primary values), @stdin / @stdin:path (whole envelope). See dlazy --help for details.
{
"ok": true,
"result": {
"tool": "execute",
"modelId": "execute",
"outputs": [
{
"type": "shape",
"id": "o_xxxxxxxx",
"shape": {}
}
]
}
}
> Async tasks (when --no-wait is passed) return outputs: [] and a task: { generateId, status } field instead. Use dlazy status to poll.
dlazy execute --prompt 'prompt content'
| 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 |
| 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 and resume the task.
Visit https://dlazy.com for more information.
共 2 个版本