Skills/ClawHub/aikey-decide

aikey-decide@0.2.5

CAUTION

Publisher claims: "AI KEY·拿不准的时候 ——拿不准的时候用。三种情况：①这件事要不要做（决策推演）②我这问题到底是什么问题（拆到本质）③知道该做但就是动不了（先排除结构性原因，再谈心理）。不替你决定，但会把问题问对、把约束摆平、把判据给死，最后落成一条到期会自动回来找你的承诺。 触发方式：/aikey-decide、/拿不准、/要不要做、/卡住了、「这个单接不接」「要不要开第二家」「该不该investment」「我这问题到底是什么」「知道该做但就是不动」「想不清楚」 For owner-operators facing a fork or a stall. Three modes: decide whether to do something, dissolve the question down to what is actually being asked, or diagnose why a known task is not moving — structural causes ruled out before psychological ones. Trigger: /aikey-decide, "should I take this deal", "should I open a second location", "what is my actual problem", "I know what to do but can't start" —— AI KEY · 不给公式，给判据。每条规则都标了实测代价。" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher iamzifei · joined 10 days agoInstalls 346Last detonated 7 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-07 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 587 lines in 3 files.

Cost to the agent

Instructions loaded
≈2,492 tok
1 file · 3 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 iamzifei: 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 iamzifeiPropose a patch to the maintainer