Skills/ClawHub/batch-invoice-verify

batch-invoice-verify@1.0.0

CAUTION· static only

Publisher claims: "面向企业财务场景的发票批处理 AI 助手，实现发票批量查验、重复报销风险识别及台账自动生成与维护。 本 Skill 面向财务批量发票处理场景，自动多格式发票识别、真伪核验、查重风控，一键输出标准化发票台账，一站式解决人工逐票核对、重复报销管控难题。" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher ningmengyun12366 · publishing for 135 daysInstalls 567Last detonated 2d 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-12 and scored it 71/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 430 lines in 5 files.

Cost to the agent

Instructions loaded
≈2,035 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

9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim ningmengyun12366: 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 ningmengyun12366Propose a patch to the maintainer