Back to skill
Skillv1.0.0

ClawScan security

Matrix Channel Fix · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignFeb 25, 2026, 8:26 AM
Verdict
benign
Confidence
high
Model
gpt-5-mini
Summary
The instructions are coherent with the stated purpose (fixing a Matrix channel for OpenClaw) and do not request unrelated credentials or hidden installs, though they do ask the operator to run potentially destructive or privilege-requiring commands that deserve care.
Guidance
This SKILL.md appears to be a straightforward troubleshooting guide for the OpenClaw Matrix channel. Before running commands: back up ~/.openclaw/ and your OpenClaw configuration; confirm the homeserver URL and bot credentials; verify you have pnpm, curl, and jq installed and run commands intentionally (global pnpm add may require sudo and will modify system node_modules); avoid blindly copying rm -rf commands — ensure you target the correct path; understand that openclaw config set storing a password may persist it in plaintext in configuration; consider testing changes in a staging environment or container, and verify the package @matrix-org/matrix-sdk-crypto-nodejs from its upstream source before installing. If you need higher assurance, ask the skill author for source/homepage or a cryptographic checksum for the module to be installed.

Review Dimensions

Purpose & Capability
okThe skill describes troubleshooting Matrix encryption, token expiry, DNS, reconfiguration, and room-leave operations; all runtime instructions (pnpm install of the crypto module, removing account files, resetting channel config, using the homeserver login API) align with that purpose.
Instruction Scope
noteInstructions include destructive operations (rm -rf ~/.openclaw/matrix/accounts) and modifying global node_modules (/usr/local/lib/node_modules/openclaw). They also instruct use of curl to log in with bot credentials and to write passwords into openclaw config. These actions are within scope for repairing the Matrix channel but require user caution: back up data first, verify the homeserver URL and credentials, and be aware that storing plain passwords in config may persist secrets.
Install Mechanism
noteThere is no install spec in the registry (instruction-only). The SKILL.md recommends running pnpm add and pnpm rebuild in a global node_modules path — this is a manual global package change and may require elevated privileges. That is plausible for rebuilding a missing native crypto module but is noteworthy because it modifies system-wide Node modules.
Credentials
okThe skill does not request extra environment variables or unrelated credentials. The credentials referenced (bot username/password, access token for the homeserver) are appropriate for reauthenticating and leaving rooms. However, the instructions do involve placing passwords into openclaw config and obtaining access tokens via curl, so users should understand these credentials will be used/stored locally.
Persistence & Privilege
okalways is false and there is no installable code or persistent background component in the skill bundle. The skill does not request elevated platform privileges itself; the user-run commands may require elevated privileges (for global pnpm installs) but that is a consequence of the remediation steps, not the skill claiming extra privilege.