SKILLEMALL.ai
GitHub ↗ RU Sign in

BC dlazy-idea2video

Turn a user's idea into the full pipeline: **story → characters → 3-view portraits → scenes → shots → keyframes → shot videos → concat**. First emit a **plan template** for the user to confi

ClawHub Agent Skills author: dlazy v1.3.19 MIT-0 3 files body ≈ 2 990 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 55/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

ProcedureInfrastructureMedia and videotype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
64
Run on models
none yet
Process rating
C
55/100
Has gaps
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 3, column 14: description: Turn a user's idea into the full pipeline: **story → characters → … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "triggers"

Process rating: all ten parameters 55/100

  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 7 mutating operations with no state check
  • 60Tools and files. Uses tools (node) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 82 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2990 tokens
  • low 13 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (8 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +1No license
  • +2Single-language instructions
  • +3Description length 190: enough signal without eating the budget
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 82 items
  • +3Output format is stated explicitly
  • +4Has examples (8 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.

External checks

ClawHub: suspicious
The skill is purpose-aligned for dLazy media generation, but it asks agents to install and run an external npm CLI with persistent credentials and inconsistent execution guidance.
LLM: suspicious (high) · 10 Sept 2026