Skills/ClawHub/continuous-discovery

continuous-discovery@1.0.3

CAUTION

Publisher claims: "Activate when: a team ships features on opinion instead of evidence; 'we need a discovery habit', 'how often should we talk to users', building a product roadmap; connecting weekly customer contact to decisions. Do NOT activate when: pre-first-customer (use the-mom-test first) or the org has no product to iterate. More: deciqai.com/c/continuous-discovery" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher deciqai · joined 8 days agoInstalls 1,043Last detonated 19 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-02 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 96 lines in 2 files.

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 deciqai: 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 deciqai