alphaclaw
Analysis
AlphaClaw’s purpose is coherent, but it asks users to install an unreviewed global npm CLI that stores AK/SK credentials and can install or publish skills.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
npm install -g 1688alphaclaw
The skill tells users to globally install an external npm CLI, but the reviewed artifact set contains no package source or install spec and the registry lists the source as unknown. That creates a provenance gap for a tool that will later receive credentials and manage skills.
`alphaclaw install <技能名称> [选项]` ... `--force` 强制覆盖已安装的技能 ... `alphaclaw publish [目录路径] [选项]` ... `--yes, -y` 跳过确认提示,直接发布
The documented commands can overwrite local installed skills and publish skill packages. These actions are purpose-aligned and user-directed, but they can change local agent behavior or submit public/account content.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
AlphaClaw 使用 AK/SK(Access Key / Secret Key)认证。... 凭证保存在 `~/.alphaclaw/auth.json`,后续请求自动使用 JWT Token 认证(有效期 30 分钟,自动刷新)。
The CLI asks for account access keys and persists authentication material locally, while the registry metadata declares no primary credential. The artifacts do not show the credential scope or storage protections.
