Skills/ClawHub/multisim-verify-requirements

multisim-verify-requirements@1.0.0

CAUTION· static only

Publisher claims: "将电路设计要求转成可计算判据并依据实验数据给出 PASS、FAIL 或未验证；use for acceptance testing, tolerance checks, and evidence-backed design review" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher yxy050208 · publishing for 73 daysInstalls 372Last detonated 17 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-07 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 89 lines in 2 files.

Cost to the agent

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

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