Skills/ClawHub/nvc-communication-guide

nvc-communication-guide@1.0.1

CAUTION· static only

Publisher claims: "左侧定投决策计算器。输入当前指数点位、近一年最高点、持仓成本、汇率，输出是否触发定投、加仓倍数、换汇建议、风险提示。基于以近一年最高点为锚的左侧定投策略。触发词：定投、基金、纳斯达克、指数、加仓、换汇、人民币、汇率、投资、贬买、买入、锁定成本、持仓、成本。" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher 987618350-cmd · publishing for 101 daysInstalls 520Last detonated 5d 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-09 and scored it 68/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

LOW
Unpinned dependency.github/workflows/clawhub-publish.yml:20 · Unpinned dependencyrun: npm install -g clawhub@latestFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
AST06

No other findings across 394 lines in 5 files.

Cost to the agent

Instructions loaded
≈883 tok
1 file · 5 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

12 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim 987618350-cmd: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Unpinned dependencies≈ +1 on the totalPin exact versions (and ideally hashes) in package.json, requirements or the install script so the bundle cannot change under you.
  3. Unpinned dependency≈ +1 on the totalPin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim 987618350-cmdPropose a patch to the maintainer