Smart Router V3
v3.0.0Dynamic AI model router with intent classification and automatic provider discovery
⭐ 0· 97·0 current·0 all-time
byEarl Co@earlvanze
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description, SKILL.md, and router.py are consistent: the server discovers providers from ~/.openclaw/openclaw.json, classifies intent, selects a provider chain, and forwards chat requests. There are no unrelated env vars, binaries, or config paths requested.
Instruction Scope
SKILL.md and router.py stick to routing behavior. Note that the runtime explicitly reads ~/.openclaw/openclaw.json (documented in SKILL.md) and will forward the final user message(s) to provider endpoints discovered there. That means prompts/messages will be sent to external provider endpoints listed in your OpenClaw config.
Install Mechanism
No install spec; the skill is run directly (python router.py). No remote downloads or archive extraction are performed by the skill itself, minimizing install-time risk.
Credentials
The skill requests no env vars, which is proportionate. However it reads ~/.openclaw/openclaw.json, which can contain provider base URLs and potentially sensitive config (and depending on how OpenClaw stores credentials, that file could include tokens or endpoints). The router will use those base URLs to make outbound HTTP requests, so confirm the config does not contain secrets you don't want forwarded.
Persistence & Privilege
always is false and the skill is user-invocable only. It does not modify other skills or system-wide configs by itself. Running it as a long-lived service (systemd) is an explicit user action and not forced by the skill.
Assessment
This skill appears to be what it says: a local router that discovers providers from ~/.openclaw/openclaw.json and forwards chat messages to those endpoints. Before running it: (1) inspect ~/.openclaw/openclaw.json for any credentials, API keys, or untrusted endpoints—remove or protect secrets you don't want the router to access; (2) run it on localhost (it binds to 127.0.0.1 by default) and consider firewalling or limiting network access if you don't trust discovered providers; (3) if you plan to run as a service (systemd), be aware it will persistently forward requests while active; (4) review provider base_url values in your OpenClaw config to ensure they point to trusted services. If you need the router to include authentication headers, the current code does not add auth headers automatically—update the code or configuration to supply credentials securely.Like a lobster shell, security has layers — review code before you run it.
aivk97891sdcmbnkve5k4rmrcjj1d84ks8bfallbackvk97891sdcmbnkve5k4rmrcjj1d84ks8blatestvk9718j88j9zetfrv5k4ccaf3ch84mt6emodelsvk97891sdcmbnkve5k4rmrcjj1d84ks8bopenclawvk97891sdcmbnkve5k4rmrcjj1d84ks8broutingvk97891sdcmbnkve5k4rmrcjj1d84ks8b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.