Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Verify Matrix device
v0.1.0Verify and cross-sign the active Matrix device for one OpenClaw-managed account. Use when a user needs to repair trust for an OpenClaw Matrix device, confirm...
⭐ 0· 324·0 current·0 all-time
byMaxime Lumeau@mlumeau
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description, prompts, and code all align: the scripts read an OpenClaw config (openclaw.json) or accept direct credentials, restore the self-signing key from a recovery key, sign the active device, and confirm the signature server-side. Required binaries (node, npm) and the listed dependency matrix-js-sdk are reasonable for this purpose.
Instruction Scope
SKILL.md instructions are specific: ask for homeserver/username/recovery key, optionally read openclaw.json, ensure node_modules exists (npm install if missing), and run the included script which performs Matrix client calls to the provided homeserver only. The instructions do require an interactive TTY for hidden secret prompts, and they explicitly avoid passing the recovery key on the command line.
Install Mechanism
No remote download/install spec is embedded — the skill instructs to run npm install --prefix {baseDir} to fetch matrix-js-sdk from the public npm registry. This is a standard approach but does write node_modules into the skill folder and will pull dependencies from npm; no custom or remote URLs, shorteners, or archives are used.
Credentials
The skill requests no environment variables or credentials up-front. It reads openclaw.json (defaulting to ~/.openclaw/openclaw.json or OPENCLAW_JSON if set) to obtain an OpenClaw access token, or accepts direct interactive credentials (access token or password). These data needs are expected for signing a Matrix device and are proportionate to the stated task.
Persistence & Privilege
The skill is not always-enabled, does not demand persistent platform privileges, and does not modify other skills or global agent config. It does write node_modules when npm install is run (local to the skill folder) but otherwise does not request elevated or persistent system privileges.
Assessment
This skill appears to do what it claims, but review and run it with these precautions: 1) Inspect the included scripts locally (they are provided) and confirm the homeserver you supply is correct. 2) Be aware the script will read your openclaw.json (default ~/.openclaw/openclaw.json or path from OPENCLAW_JSON) to obtain access tokens — only use this skill if you trust the repository/run context. 3) npm install will fetch dependencies from the public npm registry into the skill folder; consider running installs in an isolated environment (container or VM) and run npm audit if desired. 4) Provide recovery keys, access tokens, or passwords only interactively in a secure terminal as instructed. 5) If you need greater assurance, run the scripts in a sandbox and verify network requests (they target only the homeserver you provide and Matrix endpoints).Like a lobster shell, security has layers — review code before you run it.
latestvk9789a67azws2eca8pq79pb3tn824t8e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔐 Clawdis
Binsnode, npm