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.jsonwhen 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-sdkis missing, runnpm 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-tokenbypassesopenclaw.jsonand prompts for the Matrix user ID plus access token (--directand-tare compatibility aliases). - If the access token is missing,
--password(or-p) can log in with the Matrix password and sign a specific targetdevice_id, then log out the temporary helper session.