Skills/ClawHub/cue-competitive-brief

cue-competitive-brief@0.3.31

CAUTION

Publisher claims: "给你主体 + 竞品清单，产出简报：结论先行（一页以内、含可执行建议），对比表每格对应证据表单元格——fact 直接可证 / inference 由多事实推导 / opinion 无可引用来源就标 opinion、置信度宁可空着不填「高」。流程硬规矩：证据表没填的维度不写进简报；结论性主张必须先进表；简报末尾列行数、置信度分布与完全没覆盖的维度。适合：尽调背景、会前准备、策略讨论。不适合：法律合规结论、非公开数据推断。 Do NOT use for: legal conclusions, non-public inference, guesses as sources." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher huhoo · joined 4 days agoInstalls 127Last detonated 1 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario) on 2026-10-26 and scored it 75/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: npx invocation of non-well-known package; Destructive file system command detected; npx invocation of non-well-known package. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 1 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessscript backend runs setup only
0.0sprocessscript backend runs setup only

Static findings

HIGH
npx invocation of non-well-known packagereferences/cue-onboarding.md:36 · npx invocation of non-well-known package — may execute untrusted codeFix: Pin versions and sources; vendor anything fetched at install time.
AST06
CRITICAL
Destructive file system command detectedREADME.en.md:42 · Destructive file system command detectedFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
npx invocation of non-well-known packageCHANGELOG.md:154 · npx invocation of non-well-known package — may execute untrusted codeFix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
npx invocation of non-well-known packageCHANGELOG.md:125 · npx invocation of non-well-known package — may execute untrusted codeFix: Pin versions and sources; vendor anything fetched at install time.
AST06

What would make this Verified

5 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Destructive file system command detected≈ +9 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
  2. Unclaimed publisher≈ +8 on the totalClaim huhoo: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  3. npx invocation of non-well-known package≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
  4. 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 huhoo