Smart Router

Intelligent multi-model router — automatically selects the best AI model based on task type (vision, image generation, video generation, audio, reasoning, co...

This skill is plausible for routing prompts to different LLM/image/video/audio providers, but there are a few issues to check before installing: - Metadata mismatch: the registry claims no required env vars or binaries, but the scripts require SMART_ROUTER_BASE_URL and SMART_ROUTER_API_KEY and rely on curl, jq, and base64. Ask the publisher to update the manifest to declare these requirements. - Trust the provider URL: the skill will send all prompts, attached images, and any content to whatever BASE_URL you configure. Only point it at an API endpoint you trust (your provider, not an unknown third-party URL). Consider using a monitored proxy if you must use an unfamiliar endpoint. - Temporary files: generated images/audio are written to /tmp. If you handle sensitive data, clear these files after use or run in an environment where /tmp is secure. - Minimal runtime review: the shell scripts are readable and perform straightforward curl calls, but they run arbitrary model IDs from models.json. Review and edit models.json to whitelist only providers/models you want to allow. If you cannot confirm the publisher or don't want user content sent to an arbitrary endpoint, do not install. If you proceed, require the author to correct the manifest and consider running the skill in a restricted/test environment first.

Type: OpenClaw Skill Name: smart-models Version: 1.0.0 The OpenClaw Smart Router skill is designed to route user requests to various AI models via an OpenAI-compatible API. The `SKILL.md` grants `Bash(smart-router:*)` permissions, which is broad but necessary for the skill's functionality. The `scripts/call-model.sh` and `scripts/sync-models.sh` scripts handle user input (e.g., prompt, model ID) by constructing JSON payloads using `jq --arg` and `jq --argjson`, which correctly escapes strings and prevents shell injection vulnerabilities. API keys and base URLs are securely retrieved from environment variables, which is standard practice. There is no evidence of intentional malicious behavior such as data exfiltration, persistence, or unauthorized remote control, and the code appears to mitigate common injection risks.