Dlazy Grok 4.2

Efficient text generation, dialogue QA, and logical reasoning using Grok 4.2 text model.

Security Scan

This is an instruction-only skill that acts as a thin wrapper around the dLazy CLI/API; its declared requirements and runtime instructions are coherent with the stated purpose and do not ask for disproportionate access.

Purpose & Capability

The skill advertises Grok 4.2 text generation and simply delegates to the dLazy CLI and hosted API. Requiring npm/npx (to run or npx the CLI) and an API key for the service is consistent with that purpose.

Instruction Scope

SKILL.md limits actions to calling the dlazy CLI, sending prompts to api.dlazy.com, and uploading media files (via oss.dlazy.com) when the user provides local paths. The instructions do not request unrelated system data or other credentials. The file includes agent-facing 'MUST' guidance about handling common error codes, which is explicit but within scope.

Install Mechanism

The skill is instruction-only (no install spec in the registry) but the embedded metadata advertises an install command (npm install -g @dlazy/cli@1.0.6) and an npx alternative. This isn't a security problem by itself, but users should be aware installing the npm package will execute third‑party code on their machine — using npx avoids persistent installation.

Credentials

No platform or unrelated credentials are requested by the registry. The SKILL.md explains the CLI stores a DLAZY API key in ~/.dlazy/config.json (or via DLAZY_API_KEY), which is appropriate and proportional for a hosted-model client.

Persistence & Privilege

The skill does not request always:true and does not claim elevated or system-wide privileges. The only persistent artifact described is the CLI's own config file (~/.dlazy/config.json) used to store the API key, which is expected for a CLI-based SaaS client.

Assessment

This skill is a thin client for the dLazy service. Before using: (1) review the upstream GitHub/npm package if you plan to install it globally; (2) consider using npx to avoid installing third‑party code persistently; (3) understand that any local image/audio/video paths you provide will be uploaded to oss.dlazy.com; (4) the CLI stores your API key in ~/.dlazy/config.json — only use keys you trust and rotate/revoke them from the dLazy dashboard if needed.

English · 中文

Efficient text generation, dialogue QA, and logical reasoning using Grok 4.2 text model.

Trigger Keywords

• grok 4.2
• generate text
• qa
• chat

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 grok-4.2 command to get results.

dlazy grok-4.2 -h

Options:
  --prompt <prompt>                    Prompt
  --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 grok-4.2 --prompt 'prompt text'

# complex call:
dlazy grok-4.2 --prompt 'prompt text'

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.