Skills/ClawHub/team-memory

team-memory@3.0.1

CAUTION

Publisher claims: "管理者的团队长期记忆。自动保存相关沟通原话、成员与公司资料、事件、反馈、判断、待办及摘要,支持可追溯查询、1:1、周报、绩效材料和团队看板;独立JSON记忆库通过Notion在Amoo、OpenClaw等设备间合并同步,提供旧记忆导入、导出恢复及安全升级。" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher jichengkai · joined 7 days agoInstalls 1,498Last detonated 3d ago

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-10-31 and scored it 66/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
Python subprocess execution detectedscripts/tm3/sync.py:266 · Python subprocess execution detectedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

No other findings across 2,025 lines in 17 files.

What would make this Verified

14 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim jichengkai: 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.
  3. Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim jichengkai