Skills/ClawHub/a3-interest-watchlist-jb

a3-interest-watchlist-jb@1.0.2

CAUTION· static only

Publisher claims: "Build a short source-linked briefing for major news, travel disruptions, gaming, AI, companies, politics and creators, with dated sources and duplicate/material-change checks." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher jbarmada · publishing for 6 daysInstalls 171Last detonated 10 h 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-14 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
File type combined with upload actionSKILL.md:12 · File type combined with upload action — agent may exfiltrate local data files…installation without the A3 integration, read a workspace-only watchlist-history.json and apply the same rules in watchlist.mjs. Use standard workspace read/write tools if available. Store only public news identifiers, publication dates an…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07

No other findings across 221 lines in 4 files.

Cost to the agent

Instructions loaded
≈1,237 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

14 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim jbarmada: 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. File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim jbarmadaPropose a patch to the maintainer