Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Approve a pending DM pairing request without the openclaw CLI, by directly editing credential files. Use when `openclaw pairing approve` is unavailable (CLI...
Approve a pending DM pairing request without the openclaw CLI, by directly editing credential files. Use when `openclaw pairing approve` is unavailable (CLI...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Approve pending DM pairing requests by writing directly to OpenClaw credential files โ no CLI required.
Pairing state lives in two files under ~/.openclaw/credentials/: <channel>-pairing.json โ pending requests (sender ID, code, accountId) <channel>-<accountId>-allowFrom.json โ approved senders allowlist Approving = add sender ID to allowFrom file + remove code from pairing file.
python3 skills/approve-pairing/scripts/approve_pairing.py <channel> <code> Example: python3 skills/approve-pairing/scripts/approve_pairing.py telegram PWVW264M The script: Reads ~/.openclaw/credentials/<channel>-pairing.json Finds the request matching the code Appends the sender ID to the allowFrom file Removes the code from pending requests
Read ~/.openclaw/credentials/<channel>-pairing.json to get id and meta.accountId Write/update ~/.openclaw/credentials/<channel>-<accountId>-allowFrom.json: { "version": 1, "allowFrom": ["<sender_id>"] } Clear the pending request from <channel>-pairing.json
Codes expire after 1 hour โ check createdAt if approval fails A gateway restart may be needed: openclaw gateway restart If accountId is "default" or empty, the file is <channel>-default-allowFrom.json Pending requests capped at 3 per channel; old ones must expire before new ones are created
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.