Skills/ClawHub/fishing-spot-analyzer

fishing-spot-analyzer@1.0.0

CAUTION· static only

Publisher claims: "智能钓鱼选点分析助手。上传钓点照片后，自动尝试提取 EXIF GPS 定位，失败则提示用户手动输入位置，结合天气、地形、鱼情输出完整钓鱼报告和装备推荐。当用户提到：帮我分析钓点、智能选钓点、这个地方钓鱼怎么样、今天这个钓点能上什么鱼 时触发。" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher wangzhanchao883 · publishing for 166 daysInstalls 545Last detonated 19 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 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 424 lines in 2 files.

Cost to the agent

Instructions loaded
≈1,844 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 wangzhanchao883: 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 wangzhanchao883Propose a patch to the maintainer