Skills/ClawHub/stickman-video

stickman-video@1.0.2

CAUTION· static only

Publisher claims: "Make a viral stickman video in code, with no video model: a jointed SVG stick figure (round head, two-bone arms and legs with fixed bone lengths, poses written as joint angles) acts out a survival-choice story, a POV story, a "fake friend vs real friend" contrast, a history explainer or a stick fight, with a DAY counter, rules that appear one at a time, word-timed captions, procedural sound and a two-choice "FOLLOW FOR DAY 2" ending, rendered to a 1080x1920 MP4 with HyperFrames. Ships the working rig (planted-foot walk, breathing idle, head turns, blinks, shock, crouch), script templates with word counts, the fixes for stiff head-only stickman animation, and a 24 s example whose voice cost $0.04 (4 credits). Use when someone asks for a stickman video, stick figure animation, a faceless stickman channel, a survival choice story, POV stickman, or wants to "make videos like the viral stickman reels". For Google Flow or Veo clip prompts use kaomei/stickman-video-director instead." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher vargai · publishing for 215 daysInstalls 102Last detonated 12 h ago
What would fix thisWatchDispute verdict

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-14 and scored it 65/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: HTML comment carrying imperative instructions to the agent. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

CRITICAL
HTML comment carrying imperative instructions to the agentREADME.md:1 · HTML comment carrying imperative instructions to the agentGenerated by .github/readme/build.ts from SKILL.md files and .github/readme/*.json. Edit those and run `bun .github/readme/build.ts`; CI fails when this file isFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
AST01
MEDIUM
npx invocation of non-well-known packageSKILL.md:17 · npx invocation of non-well-known package — may execute untrusted codeHyperFrames 0.9 (bunx hyperframes or npx hyperframes; brings Chrome, needs Node 22 andFix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈5,712 tok
1 file · 11 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

What would make this Verified

15 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim vargai: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
  3. npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim vargaiPropose a patch to the maintainer