Skills/ClawHub/telegram-e2e-userbot

telegram-e2e-userbot@1.0.3

CAUTION· static only

Publisher claims: "Drive leased Telegram Test Server bots as a real QA user." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher hillstreet-ph · publishing for 7 daysInstalls 0Last detonated 7d 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-07 and scored it 66/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. 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
npx invocation of non-well-known packageSKILL.md:44 · npx invocation of non-well-known package — may execute untrusted code`bunx --no-install convex`, then `npx --offline --no --ignore-scripts convex`.Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

No other findings across 1,082 lines in 10 files.

Cost to the agent

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

14 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim hillstreet-ph: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
  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 hillstreet-phPropose a patch to the maintainer