Skills/ClawHub/where-we-meet

where-we-meet@0.1.0

CAUTION· static only

Publisher claims: "WhereWeMeet / 约哪儿:多人聚会、约饭、聚餐、约会选址 skill。Use when the user asks “Where should we meet”“约哪儿”“找一个谁都不远的地方”“大家住得分散去哪吃/玩”“聚餐去哪”“约饭去哪”“第一个人在...第二个人在...第三个人住...”“A 在..." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher gggggyyyyy000 · publishing for 140 daysInstalls 412Last detonated 2d 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-12 and scored it 70/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

No findings across 136 lines in 2 files.

Cost to the agent

Instructions loaded
≈447 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

10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim gggggyyyyy000: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim gggggyyyyy000Propose a patch to the maintainer