Dlazy Superres

Enhances image resolution and clarity from a URL or local path, returning an improved image URL for low-res restoration and upscaling.

Security Scan

The skill's instructions and embedded metadata expect installing a third‑party CLI and an API key and will upload local files to dlazy servers, but the registry listing omitted those requirements — the mismatch and data‑upload behavior warrant caution.

Purpose & Capability

The declared skill purpose (image super‑resolution) matches the instructions (calls a dlazy CLI which calls api.dlazy.com). However the registry-level metadata provided to the platform lists no required binaries or env vars, while the SKILL.md (and its embedded metadata) requires npm/npx and an API key and documents a config path (~/.dlazy/config.json). The omission in the registry manifest is an inconsistency.

Instruction Scope

The SKILL.md explicitly instructs the agent to run the dlazy CLI and to upload local image/video files to oss.dlazy.com so the remote API can process them. That's coherent with the stated purpose, but it means the agent will read local files and transmit them off‑host — a privacy-sensitive action that users should be aware of.

Install Mechanism

No install spec exists in the registry entry, but the SKILL.md's embedded metadata recommends installing a pinned npm package (@dlazy/cli@1.0.6) or using npx. Installing from the public npm registry is a moderate-risk action (fetches third‑party code). The lack of an explicit install spec in the registry is an implementation mismatch rather than an obviously malicious indicator.

Credentials

Registry requirements list no env vars, yet SKILL.md requires a dLazy API key (can be set via `dlazy auth set` or DLAZY_API_KEY) and documents a user config file location. Requesting an API key is proportionate to the service, but the registry's omission of that requirement is misleading and should be corrected/clarified.

Persistence & Privilege

The skill does not request always:true, does not claim elevated platform privileges, and will only store the user's API key in its own config (~/.dlazy/config.json) if the user runs the CLI auth command. There is no evidence it attempts to modify other skills or global agent settings.

Scan Findings in Context

[no_code_files_detected] expected: The package is instruction-only (no code files); the regex scanner had nothing to analyze. This makes the SKILL.md the primary security surface.

What to consider before installing

This skill appears to be a thin client for a cloud service (dlazy) and will upload any local images you provide to dlazy's storage (oss.dlazy.com). Before installing or running it: 1) Review the dlazy CLI source (GitHub link in SKILL.md) and prefer on-demand invocation via `npx` instead of a global npm install. 2) Be aware you must supply a dLazy API key; the CLI will store it at ~/.dlazy/config.json — rotate or revoke keys if needed. 3) Do not pass sensitive or private images unless you trust dlazy's service and terms. 4) The registry metadata omits required binaries/env info that the SKILL.md expects — treat that mismatch as a red flag and ask the skill author to correct it. If you need higher assurance, request the upstream CLI repository and verify the npm package and transport/endpoints before use.

English · 中文

Image super-resolution tool: enhances image clarity and details, returning enhanced URL, suitable for low-res asset restoration and upscaling.

Trigger Keywords

• superres

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: Execute dlazy superres to get the result.

dlazy superres -h

Options:
  --image <image>                      Image (URL) [image: url or local path]
  --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"
    ]
  }
}

Examples

dlazy superres --prompt 'prompt content' 

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.