Model Routing Skill
v1.0.1Automatically routes requests to the optimal model based on task type, prioritizing code, reasoning, simplicity, and normal tasks with fallback and concurren...
⭐ 0· 149·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the SKILL.md routing rules. All declared requirements (none) align with a pure instruction-only routing policy; nothing requested is extraneous to model routing.
Instruction Scope
Instructions stay within routing behavior (model selection, fallbacks, concurrency, caps). Two items are underspecified and warrant attention: the telemetry line ('record {taskType, chosenModel, capsApplied} to internal trace') does not describe storage location/retention/access controls, and 'may be tuned by admin' implies external configuration but does not say how the skill obtains or enforces those admin settings. Also the skill assumes specific model IDs (gpt-5-codex, gpt-5, gpt-5-mini, gpt-4.1-nano); if those IDs don't exist in your environment the routing could fail or route incorrectly.
Install Mechanism
No install spec and no code files: the skill is instruction-only so nothing is written to disk or downloaded.
Credentials
Skill requests no environment variables, credentials, or config paths. This is proportional to its stated purpose.
Persistence & Privilege
always:false and no self-install behavior. The skill mentions admin-tunable defaults and internal traces but does not request persistent privileges or system-wide changes in the current text.
Assessment
This skill is coherent and low-risk in that it only provides routing instructions and requires no installs or credentials. Before enabling it: 1) confirm the model IDs used by the skill match the models available in your environment (otherwise update the SKILL.md or mapping); 2) ask where 'internal trace' telemetry is stored, who can access it, and how long it is retained—avoid recording PII in taskType if possible; 3) verify how 'admin tuning' and org/channel/session model locks are surfaced to the agent so the skill won't conflict with enforced policies; 4) test fallback, retry, concurrency, and budget behaviors in a safe environment to ensure they behave as expected and respect billing limits. If those operational details are acceptable, the skill appears benign and appropriate to use.Like a lobster shell, security has layers — review code before you run it.
latestvk977q6tshvz7p73kfyg4qzv99s83v6nf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.