dlazy-text-storyboard-script
This is a legitimate storyboard-script generation skill that wraps a third-party dLazy CLI for optional image/video generation; all significant capabilities (shell:WRITE, network:READ to api.dlazy.com/files.dlazy.com, API key storage in ~/.dlazy/config.json) are declared in SKILL.md and metadata, though the main SKILL.md contains an internal contradiction between its 'no image generation' disclaimer and its execution instructions that command CLI invocation.
Why this conclusion was reached
0/4 dimensions flaggedDeclared resources and inferred behavior are broadly aligned.
5 lower-risk artifacts were extracted and still need context.
There is no explicit malicious chain in the report.
Dependencies are present but no obvious high-risk issue stands out.
What drove the risk score up
SKILL.md 'Goals and Principles' says 'do not actually invoke tools to generate image/video/audio assets' but the 'CRITICAL EXECUTION INSTRUCTIONS' section explicitly commands running 'dlazy seedream-4.5 --prompt ...' CLI commands.
SKILL.md metadata.clawdbot.install specifies '1.0.9' but the documentation body references '1.2.3' for npx and npm install commands.
Skill instructs saving the dLazy API key to ~/.dlazy/config.json; credential storage on disk is declared but worth monitoring.
Most important evidence
Internal documentation contradiction
SKILL.md 'Goals and Principles' section explicitly states 'This skill is only responsible for script generation; do not actually invoke tools to generate image/video/audio assets.' However, the 'CRITICAL EXECUTION INSTRUCTIONS' section at the bottom instructs the agent to execute terminal commands via the dLazy CLI (e.g., 'dlazy seedream-4.5 --prompt "..."'). This creates user confusion about the skill's actual scope.
SKILL.md:1 Version pin mismatch in metadata vs. documentation
The SKILL.md frontmatter metadata specifies install version '1.0.9' for the npm package, but the documentation body references '1.2.3' for npx invocations. Version inconsistencies could lead to unexpected behavior or confusion during installation.
SKILL.md:7 API key storage in user config directory
The skill instructs to save the dLazy API key to ~/.dlazy/config.json. While this is standard CLI behavior, the skill does not verify the file permissions are appropriately restricted after writing. A misconfigured CLI could leave the credential world-readable.
SKILL.md:14 Declared capability vs actual capability
SKILL.md:21 — 'npm install -g @dlazy/[email protected]'; SKILL.md:47 — 'dlazy seedream-4.5 --prompt ...' SKILL.md metadata: 'apiEndpoints: ["api.dlazy.com", "files.dlazy.com"]' SKILL.md:14 — stores API key to '~/.dlazy/config.json' Suspicious artifacts and egress
https://www.npmjs.com/package/@dlazy/cli SKILL-cn.md:7
https://dlazy.com SKILL-cn.md:32
https://dlazy.com/dashboard/organization/api-key SKILL-cn.md:33
https://clawhub.ai/user/dlazyai skill-card.md:9
https://clawhub.ai/dlazyai/skills/dlazy-text-storyboard-script skill-card.md:35
Dependencies and supply chain
| Package | Version | Source | Known vuln | Notes |
|---|---|---|---|---|
| @dlazy/cli | 1.0.9 (metadata) / 1.2.3 (docs) | npm | No | Version mismatch between metadata install field and documentation body. Package not reviewed in this analysis — source at github.com/dlazy-ai/cli was not imported. |
File composition
SKILL-cn.md SKILL.md skill-card.md