Skills/ClawHub/product-video-hooks

product-video-hooks@1.0.3

CAUTION· static only

Publisher claims: "Turn a product into scroll-stopping video hooks. Writes the first 3 seconds of TikTok, Reels and Meta product videos as three agreeing layers (what is on screen, the spoken line, the text overlay), from the buyer's own words, across 20+ hook types taken from Meta's Hooks Menu, Motion's 2026 hook data, Hormozi's callouts and the TikTok openers that spread in 2026 (late discovery, compliment then reveal, problem and fix in one clip, reply to a comment). It matches each hook to the buyer's awareness, checks it against platform claim rules, and, when footage exists, makes one MP4 per hook for testing. Use when someone asks for hooks, openers, the first 3 seconds, a better intro, or new hook variants for a product video or ad. NOT for whole ad plans (use ecommerce-video-ads), generating a viral-style product-in-use hook clip from photos (use varg-product-hook), app or SaaS hooks, or YouTube titles and thumbnails." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher vargai · publishing for 215 daysInstalls 342Last detonated 4d ago

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-11 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 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

No other findings across 333 lines in 4 files.

Cost to the agent

Instructions loaded
≈1,841 tok
1 file · 4 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

16 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.
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