Skills/ClawHub/tiktok-shop-video

tiktok-shop-video@1.0.6

CAUTION· static only

Publisher claims: "Turn a product link into a TikTok Shop video that sells and stays compliant. Writes the script and shot list for a shoppable or affiliate video in TikTok Shop's own styles (personal review, before & after, unboxing, tutorial, problem and fix in one clip), with the product visible from the first frame, one specific number in the demo and a cart CTA, and enforces the 2025–2026 Shop rules that kill reach and accounts: a real person on screen, no AI voice as the presenter, no still-image slideshows (at least 3 s of moving footage), no price or deal that differs from the product page, no exaggerated claims or weight before/after, commercial sounds only, no near-duplicate reposts. Uses AI only for b-roll and product shots. Use when someone makes TikTok Shop videos as a seller or affiliate, asks why Shop videos stall at 200 views or got a violation, or wants Shop content plans. NOT for paid TikTok or Meta ads with AI actors (use ai-ugc-ad-video) or for editing existing footage (use ecommerce-video-edit)." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher vargai · publishing for 215 daysInstalls 344Last detonated 29 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-13 and scored it 63/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

MEDIUM
Process kill commandSKILL.md:8 · Process kill command — agent can terminate processesrules that kill reach and accounts: a real person on screen, no AI voice as the presenter, noFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
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

Cost to the agent

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

17 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. Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
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