SKILLEMALL.ai
GitHub ↗ RU Sign in

CB handdrawn-live-video-generator

For creators making surreal short videos that blend rough glowing hand-drawn animation with live-action spaces. Users provide a scene idea, contact object or hand, desired mood, and optional language or style constraints. The Skill clarifies the physical contact, designs continuous morphing, escape route, and delayed handheld chase movement, then writes a reusable 15-second 16:9 video prompt in the user's language. After user confirmation it recommends MiniMax H3 generation and checks contact realism, camera delay, rough glowing stroke texture, and non-horror tone. Best for single-scene creative clips, not polished CG, horror jump scares, plush characters, or multi-scene cuts.

MiniMax-AI/MiniMax-H3 Agent Skills author: MiniMax-AI 3 files body ≈ 1 318 tokens Open the sourcegithub.com↗ analyzed 19 d ago

For creators making surreal short videos that blend rough glowing hand-drawn animation with live-action spaces.

As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting

GeneratorMedia and videoAI and agentstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
B
71/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Running it twice w 4
30
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 description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "trigger-words"

Process rating: all ten parameters 71/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 55Failures and branches. 1 branches
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 100Tools and files. No external tools needed
  • 100Steps. 42 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1318 tokens

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)
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 685: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 42 items
  • +3Output format is stated explicitly

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