What problem does it solve?
Adding a model provider to OpenClaw requires careful credential handling, validated configuration writes, and a live proof that the route actually works. This Skill enforces a non-interactive, auditable workflow that never exposes secret values and always ends with a verifiable probe result.
Core Features & Use Cases
- SecretRef-only credential wiring: Stage API keys via file or environment references instead of inline values, keeping secrets out of config and logs.
- Validated config mutation: All changes go through
openclaw config set with --dry-run previews, so schema errors surface before persistence.
- Live proof of route: Run a roster-safe probe (
openclaw agent --agent <id> --model ...) that returns an exact expected string, confirming the provider is reachable end-to-end.
- Use Case: An operator needs to onboard OpenAI as a new provider for a multi-agent OpenClaw deployment. They stage the key in a
0600 file, write the SecretRef, run the probe, and record the model id and latency as proof.
Quick Start
Add the OpenAI model provider to OpenClaw using a file-based SecretRef and prove the route with a roster-safe probe.