← Back to Skills Marketplace
446
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install model-route-guard
Description
Diagnose and fix model routing conflicts. Ensure primary model uses correct provider endpoint without duplicate overrides.
Usage Guidance
This skill performs direct edits to OpenClaw configuration and restarts the gateway while pointing the provider to a specific external endpoint (coding.dashscope.aliyuncs.com). Before running it: 1) Back up $HOME/.openclaw/openclaw.json and any agents/*.json files; 2) Manually review the configs it will change and verify the hardcoded endpoint is correct and trusted for your environment; 3) Confirm you have the 'openclaw' CLI and permission to restart the gateway; 4) Prefer running the audit steps (Route Audit) first without applying changes, then apply fixes manually or add explicit confirmation/validation steps; 5) In environments with sensitive data, test in a staging agent to avoid accidental routing of requests to an untrusted third party. The registry metadata should have declared config file access — if you need assurance, ask the publisher for source/homepage and an explanation for the endpoint choice before installing.
Capability Analysis
Type: OpenClaw Skill
Name: model-route-guard
Version: 1.0.0
The skill performs direct file modifications and deletions on OpenClaw's configuration files (`$HOME/.openclaw/openclaw.json`, `$HOME/.openclaw/agents/main/agent/models.json`) and executes system commands (`openclaw gateway restart`). While these actions are plausibly needed for the skill's stated purpose of diagnosing and fixing model routing conflicts, they represent significant capabilities that could be misused if the skill were compromised or if there were underlying vulnerabilities. There is no clear evidence of malicious intent like data exfiltration or unauthorized remote control, but the direct manipulation of system configuration files and execution of system commands elevate it beyond benign.
Capability Assessment
Purpose & Capability
The skill's described goal (diagnose/fix model routing) aligns with the actions in SKILL.md (audit config, update provider URL, remove agent override, restart gateway). However, the registry metadata claims no required config paths or credentials while the runtime instructions explicitly read and modify $HOME/.openclaw/openclaw.json and $HOME/.openclaw/agents/main/agent/models.json. That metadata omission is an inconsistency that reduces transparency.
Instruction Scope
The instructions tell the agent to read and overwrite user config files, delete an agent override file, and restart the OpenClaw gateway. They also hardcode a specific external endpoint (https://coding.dashscope.aliyuncs.com/v1). Modifying provider endpoints can redirect model traffic to a third-party host; deleting agent files is destructive if done without backup. The SKILL.md does not include any safety checks (backup, confirmation, or validation of the endpoint) before making changes.
Install Mechanism
Instruction-only skill with no install steps or code files — lowest-risk install surface. There is nothing being downloaded or installed by the skill itself.
Credentials
The skill declares no environment variables or credentials, and it doesn't attempt to read secrets explicitly, which is consistent. However, it requires write access to OpenClaw config files and the ability to run the 'openclaw' CLI to restart the gateway. More importantly, it changes the model provider endpoint to a hardcoded third-party URL; that is a high-impact network change and should be justified and verified before applying. The skill does not request or declare this trust requirement.
Persistence & Privilege
always is false and the skill is not force-included. Still, the instructions modify persistent agent/global config and restart the gateway — an action requiring filesystem and service control privileges. The skill does not attempt to persist itself beyond those changes, nor does it modify other skills' configs, but the changes it makes are persistent and potentially disruptive.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install model-route-guard - After installation, invoke the skill by name or use
/model-route-guard - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of model-route-guard.
- Diagnose and fix model routing conflicts for Openclaw.
- Audit and resolve duplicate provider overrides and endpoint mismatches.
- Ensures primary model uses correct provider endpoint (coding.dashscope.aliyuncs.com).
- Provides step-by-step workflow for route auditing, conflict fixing, and verification.
- Safeguards privacy by not exposing API keys in output.
Metadata
Frequently Asked Questions
What is Model Route Guard?
Diagnose and fix model routing conflicts. Ensure primary model uses correct provider endpoint without duplicate overrides. It is an AI Agent Skill for Claude Code / OpenClaw, with 446 downloads so far.
How do I install Model Route Guard?
Run "/install model-route-guard" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Model Route Guard free?
Yes, Model Route Guard is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Model Route Guard support?
Model Route Guard is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Model Route Guard?
It is built and maintained by Dalomeve (@dalomeve); the current version is v1.0.0.
More Skills