oc-smart-agent-hub_skill

This skill helps manage multi-provider agent systems by automatically discovering, routing, and selecting cost-effective models across local and cloud
  • Python

2.5k

GitHub Stars

6

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill oc-smart-agent-hub

  • _meta.json300 B
  • BACKUP_REPORT.md4.3 KB
  • INTRODUCTION.md5.3 KB
  • SECURITY_NOTICE.md1.6 KB
  • SKILL.md4.3 KB
  • VERSION_CHANGELOG.md869 B

Overview

This skill is a multi-provider agent model assignment system that routes AI tasks to the best available model across cloud vendors and local deployments. It supports automatic discovery, zero-code YAML configuration, cost-aware routing, and failover to fallback models. The goal is to simplify using many model providers while optimizing performance and cost.

How this skill works

The system scans configured cloud vendors (OpenAI, Anthropic, Alibaba Cloud, Baidu, Zhipu AI, etc.) and local model services (Ollama, LM Studio, vLLM) to build an inventory of available models. Policy-driven YAML rules determine routing by task type, latency, cost, and provider health. At runtime the hub selects the optimal model, performs failover on errors, and can be reconfigured without code changes.

When to use it

  • You're operating across multiple model providers and need centralized routing
  • You run a mix of cloud-hosted and local models and want unified selection
  • You need automated failover and high availability for model inference
  • You want to optimize cost by selecting more economical providers per task
  • You prefer declarative configuration (YAML) without changing code

Best practices

  • Maintain a concise models.yaml with clear tags for task capabilities, cost, and latency
  • Run regular scans to keep the inventory up to date for local services
  • Define fallback chains per task type to guarantee continuity on provider outages
  • Use cost and latency weights in routing policies to balance budget and performance
  • Version control your YAML configs and test changes in staging before production

Example use cases

  • Route chat and retrieval tasks to high-throughput cloud models while using local models for private or low-latency needs
  • Automatically shift expensive large models to cheaper alternatives for batch processing to control costs
  • Detect a provider outage and switch to a local vLLM instance for uninterrupted service
  • Combine Anthropic or OpenAI for instruction-following while using Ollama for custom fine-tuned models
  • Scan the network to discover newly started local model services and immediately add them to the routing pool

FAQ

No. Providers and routing policies are defined in YAML. You can add, enable, or disable providers via configuration or management commands without changing code.

How does failover work?

Failover is automatic based on provider health and configured fallback lists. If a selected model fails, the hub re-routes the request to the next available model in the chain.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
oc-smart-agent-hub skill by openclaw/skills | VeilStrat