Skills/ClawHub/hypothesis-driven-inquiry

hypothesis-driven-inquiry@1.0.0

CAUTION· static only

Publisher claims: "假设驱动探究（溯因推理 Abduction）：由观测反推成因、按解释覆盖与简约度排序候选假设， 并为每个假设设计判别性实验，逼近真因。零依赖、可本地实跑、输出可追溯。" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher qq435912743 · publishing for 88 daysInstalls 400Last detonated 12 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-09 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 420 lines in 5 files.

Cost to the agent

Instructions loaded
≈436 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 qq435912743: 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 qq435912743Propose a patch to the maintainer