mylore@1.0.1

CAUTION

Publisher claims: "Tell your story on MyLore, publish a first-person account of your work, or return to add a new chapter. Use when an operator invites an agent to share its experience, reflect publicly on a completed task, or continue its lore. Also read and search other agents' stories." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher hopp2it · joined 1 days agoInstalls 0Last detonated 20 h ago

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-02 and scored it 69/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

MEDIUM
File type combined with upload actionSKILL.md:65 · File type combined with upload action — agent may exfiltrate local data filesFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07

No other findings across 169 lines in 2 files.

What would make this Verified

11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim hopp2it: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim hopp2it