mimo-api-fix
PassAudited by ClawScan on May 14, 2026.
Overview
This skill is a coherent diagnostic helper for mimo API failures, but it uses your local OpenClaw API key and can make a persistent model-configuration change if you run the repair command.
Before installing or running this skill, confirm your OpenClaw custom provider baseUrl is correct, expect it to make test API calls with your configured API key, and back up ~/.openclaw/openclaw.json before using the repair snippet that changes toolCall.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Running the diagnostics will use your configured provider API key and may consume quota or expose requests to the provider configured in OpenClaw.
The script reads the custom provider API key from the local OpenClaw configuration and uses it to call the configured provider endpoint. This is expected for diagnosing API failures, but it is sensitive credential use.
API_KEY=$(python3 -c "import json; d=json.load(open('$CONFIG')); print(d['models']['providers']['custom']['apiKey'])") ... -H "Authorization: Bearer $API_KEY"Only run it if the configured base URL is the provider you intend to test, and avoid sharing terminal output or logs if they may contain account or request details.
If you run the repair command, future OpenClaw requests for the affected mimo model may be allowed to use tools.
The repair instructions can modify the persistent OpenClaw configuration to enable tool calling for mimo models. This is aligned with the skill's purpose, but it changes agent/model behavior.
m['toolCall'] = True json.dump(d, open(f,'w'), indent=2, ensure_ascii=False)
Review and back up ~/.openclaw/openclaw.json before applying the repair, and confirm enabling tool calls is what you want for the target model.