Rei-Clawd

Set up Rei Qwen3 Coder as a model provider. Use when configuring coder.reilabs.org, adding Rei to Clawdbot, or troubleshooting 403 errors from Rei endpoints.

Security Scan

The skill is internally consistent with its stated purpose: it adds a Rei model provider to the user's Clawdbot config, toggles the active model, and can revert the change; it modifies the local ~/.clawdbot/clawdbot.json and restarts the gateway as expected.

Purpose & Capability

Name/description match the files and instructions: setup, switch, and revert scripts operate on ~/.clawdbot/clawdbot.json and restart the Clawdbot gateway to add/use the Rei provider. No unrelated credentials, binaries, or network endpoints are requested beyond coder.reilabs.org (the declared provider).

Instruction Scope

SKILL.md instructs either running the included scripts or editing the Clawdbot config manually. The scripts legitimately read/modify ~/.clawdbot/clawdbot.json, create a .bak backup, and restart the gateway. Note: setup.sh embeds the provided API key directly into a JSON here-document and then passes it to jq with --argjson; this can break if the API key contains unexpected characters and could corrupt the config (see JSON/string handling risk below). Otherwise, the instructions do not attempt to read other unrelated files or exfiltrate data.

Install Mechanism

No install spec; this is instruction-plus-scripts only. The scripts are simple bash utilities with no external downloads or extracted archives. They require jq to be present, which the script checks for and errors if missing.

Credentials

The skill requests no environment variables or external credentials up front, which is proportional. The setup flow does require the user to supply their Rei API key; that key is stored in plaintext in ~/.clawdbot/clawdbot.json (expected for provider config). Users should be aware the API key ends up in their local config file. Also, because setup.sh substitutes the raw API key into a JSON here-doc, malformed or specially constructed keys could break or alter the resulting JSON.

Persistence & Privilege

always:false (no forced inclusion). The skill modifies only the user's Clawdbot config and writes a backup; it does not modify other skills or system-wide settings beyond restarting the Clawdbot gateway (as intended). The agent-default ability to invoke skills autonomously is platform default — not a specific elevated privilege of this skill.

Assessment

This skill appears to do what it claims: add Rei as a model provider by editing ~/.clawdbot/clawdbot.json and restarting the gateway. Before installing or letting an agent run the setup script: (1) Verify you trust coder.reilabs.org and are willing to store your Rei API key in plaintext in ~/.clawdbot/clawdbot.json. (2) Inspect the scripts yourself (they are short) and keep the created .bak backup if you want to revert. (3) Be cautious about automatic agent invocation: running the setup script will immediately modify your Clawdbot config and restart the gateway. (4) Note a robustness/security issue: setup.sh injects the API key directly into a JSON here-doc and then passes it to jq with --argjson; if your API key contains quotes/newlines or maliciously crafted content it could corrupt the JSON. To be safer, run the script interactively or manually edit the config using a JSON-safe method (e.g., use jq --arg to set string fields) if you have concerns.

Rei Qwen3 Coder

Rei provides Qwen3 Coder via an OpenAI-compatible endpoint at coder.reilabs.org.

Setup via Script

./skills/rei/scripts/setup.sh YOUR_REI_API_KEY

This adds the provider, adds it to the model allowlist, and restarts the gateway.

Setup via Agent

Ask your agent:

"Set up Rei with API key: YOUR_KEY"

The agent will read this skill and run the setup script for you.

Switching Models

Via chat:

/model rei
/model opus

Via script:

./skills/rei/scripts/switch.sh rei
./skills/rei/scripts/switch.sh opus

Via agent:

"Switch to Rei" or "Switch back to Opus"

Revert

If something breaks, restore the backup:

./skills/rei/scripts/revert.sh

Manual Setup

Add to ~/.clawdbot/clawdbot.json:

{
  "models": {
    "providers": {
      "rei": {
        "baseUrl": "https://coder.reilabs.org/v1",
        "apiKey": "YOUR_API_KEY",
        "api": "openai-completions",
        "headers": { "User-Agent": "Clawdbot/1.0" },
        "models": [{
          "id": "rei-qwen3-coder",
          "name": "Rei Qwen3 Coder",
          "contextWindow": 200000,
          "maxTokens": 8192
        }]
      }
    }
  },
  "agents": {
    "defaults": {
      "models": {
        "rei/rei-qwen3-coder": { "alias": "rei" }
      }
    }
  }
}

Then restart: clawdbot gateway restart

Troubleshooting

403 errors: The User-Agent: Clawdbot/1.0 header is required. The setup script adds this automatically. If you configured manually, make sure the header is present.

"Model not allowed": Rei must be in agents.defaults.models to switch to it. The setup script handles this. For manual setup, add the allowlist entry shown above.