Multi-model automatic fallback system

v1.0.0

Multi-model automatic fallback system. Monitors model availability and automatically falls back to backup models when the primary model fails. Supports MiniM...

0· 487·3 current·3 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The skill claims to provide an automatic multi-model fallback service, but there is no implementation, no install spec, and no declared binaries. For a runtime feature that 'automatically handles model failures' you would expect either embedded code or an install step to deploy a background service; instead this is only documentation. The declared configuration paths (e.g., ~/.openclaw/skills/model-fallback/config.json) and script references imply additional components that are not present.
!
Instruction Scope
The SKILL.md instructs agents to run scripts (/scripts/model-fallback.sh), read and edit config files (~/.openclaw/skills/...), check logs (~/.openclaw/logs/...), read environment variables (MODEL_FALLBACK_ENABLED), and call a local health endpoint (http://localhost:18789/api/models/health). Those actions go beyond simple documentation: they assume local files, scripts, and a local HTTP service exist. Because the skill will be followed by an agent with power to read files and call local endpoints, these instructions could cause the agent to attempt file access or network calls to a local service that isn't provided here.
Install Mechanism
No install spec is provided (instruction-only). This reduces the risk of arbitrary remote code being fetched, but also means the skill cannot actually provide the promised automatic functionality on its own. The lack of an install step is coherent only if the user already has the required service/scripts installed — which is not made explicit.
Credentials
The skill does not request any credentials or sensitive environment variables in the registry metadata. The SKILL.md documents optional vars (MODEL_FALLBACK_ENABLED, MODEL_FALLBACK_LOG_LEVEL) which are reasonable. It does, however, suggest checking API keys and provider dashboards in troubleshooting, but it never asks for or defines provider-specific secrets — so declared environment/credential requests are proportionate.
Persistence & Privilege
The skill is not marked 'always' and does not request persistent system-wide changes in its metadata. The instructions reference writing and reading files under the user home (~/.openclaw) which is normal for a per-user skill; nothing in the manifest requests elevated or persistent platform privileges.
What to consider before installing
This package is documentation-only and does not include the service or scripts it references. Before installing or enabling it: (1) Confirm there is an actual implementation you can inspect (scripts at /scripts/model-fallback.sh, a service listening on localhost:18789, and the ~/.openclaw/skills/model-fallback/config.json). (2) If you expect the skill to run automatically, require an install spec from a trusted source (or provide the code) — otherwise the agent may attempt file reads or local network calls that do nothing or expose data. (3) Audit any scripts/configs that will be placed under ~/.openclaw and any local service binaries; ensure they come from a trusted release. (4) If you do not trust or cannot audit the implementation, do not enable automatic invocation; consider manual testing in an isolated environment first.

Like a lobster shell, security has layers — review code before you run it.

fallbackvk978pmhmp06eqf212w5pkebw3181zs51latestvk978pmhmp06eqf212w5pkebw3181zs51modelvk978pmhmp06eqf212w5pkebw3181zs51multi-modelvk978pmhmp06eqf212w5pkebw3181zs51

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments