Model Routing Orchestrator
v2026.3.27Route each user request to the most cost-effective model or multi-model workflow based on task type, complexity, risk, latency, budget, tool needs, and verif...
⭐ 2· 134·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (model routing/orchestration) matches the SKILL.md content: heuristics for choosing model tiers, workflows, and verification strategies. There are no unrelated env vars, binaries, or install steps requested that would be inconsistent with routing decisions.
Instruction Scope
The instructions enumerate inputs to collect from the request and the 'system context' and give a detailed taxonomy and routing rules. However, 'system context' is open-ended and could be interpreted to include logs, environment variables, agent state, or other data sources not strictly needed for routing. The SKILL.md does not explicitly instruct reading secrets or files, but lacks explicit bounds on what counts as system context.
Install Mechanism
No install specification or code files; this is instruction-only, so nothing will be written to disk or downloaded at install time.
Credentials
The skill declares no required environment variables, credentials, or config paths. That matches the described functionality (routing heuristics) and is proportionate. Be aware the runtime wording could prompt the agent to consult environment data if available.
Persistence & Privilege
always is false and it uses normal autonomous invocation defaults. The skill does not request elevated or permanent presence or modification of other skills/configs.
Assessment
This skill appears coherent for deciding which model or workflow to use and does not request credentials or install code. Before enabling it in production, confirm what your deployment supplies as 'system context' (do not expose secrets, full logs, or unrelated environment variables). Test routing decisions in a sandbox with limited agent privileges, and add explicit constraints or a policy that prevents the agent from reading sensitive files or env vars when applying the routing rules. If you plan to connect provider-specific models, prefer making those provider credentials explicit in the deployment (so the skill cannot implicitly access broad environment state).Like a lobster shell, security has layers — review code before you run it.
latestvk97b8z2xwpbnx5cxy4kdpggy2s83mwt4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.