video-script@1.0.8
CAUTION· static onlyPublisher claims: "Write the script for any video before anything is generated: what is said, shown and heard in every beat, sized to the clock and the video model. A brief and a facts file in; one script table out (time, spoken line, on-screen text, visual, sound), three hooks, and a check that measures pace, hook timing, shot length, unsourced numbers and AI-sounding lines. Six structures with one example script each, plus variations for demo and launch videos, product reviews, ads and UGC, social shorts and short-form drama, and a loop for testing and improving the skill. Use for "write a script", "video script", "ad script", "UGC script", "TikTok, Reels or Shorts script", "YouTube script", "voiceover script", "demo or launch video script", "product review script", "short drama episode", "skit", "hooks", "how many words for 30 seconds", or any video that has no script yet. Not for the look (find-references) or the shot prompts (varg-video-prompting)." Observed in sandbox: static analysis only — behavior not yet observed.
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-13 and scored it 64/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 onlyThis 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
Generated 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.| Chip & Dan Heath | authors of Made to Stick | the curse of knowledge: replace abstractions with concrete examples | [HBR](https://hbr.org/2006/12/the-curse-of-knowledge) |Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.…h concrete examples | [HBR](https://hbr.org/2006/12/the-curse-of-knowledge) | | Dan Harmon; Blake Snyder; Syd Field | Community; Save the Cat; Screenplay | story c…Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.Cost to the agent
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
16 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- 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.
- 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.