How do I install the Verify Matrix Device skill?

Run npx skillmds@latest add dvcrn/verify-matrix-device in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Verify Matrix Device safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: executes scripts, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Verify Matrix Device?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Verify Matrix Device free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Verify Matrix Device?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Verify Matrix Device by dvcrn — Agent Skill

Name: Verify Matrix Device
Rating: 4.2 (5 reviews)
Author: dvcrn

Verify Matrix Device

Verify 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 the current device is self-signed, or recover cross-signing with a recovery key.

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

OpenClaw Matrix Device Verification

Use this skill when the user wants to verify the currently active Matrix device for an OpenClaw-managed account.

Required Inputs

homeserver: Matrix homeserver base URL.
username: OpenClaw account id, full Matrix user id, or unique localpart.
recovery key: the Matrix recovery key. Treat this as a secret.
Optional: path to openclaw.json when it is not in the default location.

Workflow

If any required input is missing, ask the user for it.
Ensure dependencies are installed in this skill folder. If {baseDir}/node_modules/matrix-js-sdk is missing, run npm install --prefix {baseDir}.
Run the verifier from this skill folder: node {baseDir}/scripts/verify_matrix_device.mjs --homeserver "<homeserver>" --username "<username>"
If the user gave a non-default config path, append: --openclaw-json "<path>"
Let the script prompt for the recovery key in the terminal. Do not pass the recovery key on the command line or in environment variables.
Report whether the device was already cross-signed or was signed successfully.

Notes

The skill uses the existing OpenClaw access token from openclaw.json; it does not create a helper Matrix device.
The verifier signs the active device directly and confirms the signature server-side.
Use a real TTY so the hidden recovery-key prompt works correctly.
For local testing outside OpenClaw, --access-token bypasses openclaw.json and prompts for the Matrix user ID plus access token (--direct and -t are compatibility aliases).
If the access token is missing, --password (or -p) can log in with the Matrix password and sign a specific target device_id, then log out the temporary helper session.

---name: verify-matrix-devicedescription: Verify 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 the current device is self-signed, or recover cross-signing with a recovery key.---# OpenClaw Matrix Device VerificationUse this skill when the user wants to verify the currently active Matrix device for an OpenClaw-managed account.## Required Inputs- `homeserver`: Matrix homeserver base URL.- `username`: OpenClaw account id, full Matrix user id, or unique localpart.- `recovery key`: the Matrix recovery key. Treat this as a secret.- Optional: path to `openclaw.json` when it is not in the default location.## Workflow1. If any required input is missing, ask the user for it.2. Ensure dependencies are installed in this skill folder. If `{baseDir}/node_modules/matrix-js-sdk` is missing, run `npm install --prefix {baseDir}`.3. Run the verifier from this skill folder: `node {baseDir}/scripts/verify_matrix_device.mjs --homeserver "<homeserver>" --username "<username>"`4. If the user gave a non-default config path, append: `--openclaw-json "<path>"`5. Let the script prompt for the recovery key in the terminal. Do not pass the recovery key on the command line or in environment variables.6. Report whether the device was already cross-signed or was signed successfully.## Notes- The skill uses the existing OpenClaw access token from `openclaw.json`; it does not create a helper Matrix device.- The verifier signs the active device directly and confirms the signature server-side.- Use a real TTY so the hidden recovery-key prompt works correctly.- For local testing outside OpenClaw, `--access-token` bypasses `openclaw.json` and prompts for the Matrix user ID plus access token (`--direct` and `-t` are compatibility aliases).- If the access token is missing, `--password` (or `-p`) can log in with the Matrix password and sign a specific target `device_id`, then log out the temporary helper session.

Frequently asked questions