Skills/ClawHub/freight-loss-claim-check-free

freight-loss-claim-check-free@1.0.4

CAUTION

Publisher claims: "货运破损理赔与承运商扣款明细表逐项核对（理赔金额复算、扣款不得超过理赔金额、重复运单与赔付比例超上限、关键字段缺失或负数），每条结论引用原文行号与运单号。本免费版执行引擎声明的 5 项免费检查。触发词包括 货运破损理赔、承运商扣款核对、破损理赔对账、理赔扣款明细表。" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher chenqg618 · joined 7 days agoInstalls 334Last detonated 2 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-06 and scored it 67/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 905 lines in 5 files.

Cost to the agent

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

13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim chenqg618: 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.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim chenqg618Propose a patch to the maintainer