skills.rest
Umbral-Bot
Umbral-BotOFFICIAL
Explore all skills by this author →
GitHub

provider-status

Query the Worker API for LLM provider status, quota usage, and routing configurations.

Updated Feb 26, 2026
Search Tags:#monitoring#routing#llm#status#quota#provider
One-click install
npx skills add https://github.com/Umbral-Bot/umbral-agent-stack --skill provider-status
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: provider-status
Source: https://github.com/Umbral-Bot/umbral-agent-stack/tree/main/openclaw/workspace-templates/skills/provider-status
Command: npx skills add https://github.com/Umbral-Bot/umbral-agent-stack --skill provider-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides visibility into the operational status, current usage, and routing configurations of various Large Language Model (LLM) providers.

Core Features & Use Cases

  • Provider Health Check: Determine if configured LLM providers are active and responsive.
  • Quota Monitoring: Track current usage against defined quotas for each LLM provider.
  • Routing Configuration: Understand which LLM providers are preferred for specific task types.
  • Use Case: Before initiating a critical task, a user can ask "What's the status of our LLM providers?" to ensure the most suitable and available model is selected, preventing task failures due to quota exhaustion or provider downtime.

Quick Start

Ask the provider-status skill to show the current quota status for all configured LLM providers.

Frequently Asked Questions about provider-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check LLM provider status and quota usage?▼

You can check LLM provider status by asking the system to retrieve operational health, current quota consumption, and model routing configurations for all configured providers.

What is LLM routing configuration and when do I need to verify it?▼

LLM routing configuration maps providers to specific task types. You need to verify it before initiating critical tasks to select the most suitable available model and prevent failures.

Do I need a Worker API token to monitor provider health?▼

Yes, monitoring provider health requires a valid WORKER_TOKEN to authenticate with the Worker API, and Redis access is necessary to retrieve current quota usage data.

How can I prevent task failures caused by LLM quota exhaustion?▼

Prevent task failures from quota exhaustion by monitoring current usage against defined quotas for each LLM provider. This visibility helps you select an available model before starting critical tasks.

Why does my multi-LLM provider status check fail to return quota data?▼

A multi-LLM provider status check fails to return quota data if the environment lacks a valid WORKER_TOKEN for the Worker API or if Redis access is not properly configured.

Related Skills

Explore More Software Engineering Skills→
heinschulieheinschulie

database

Provision managed PostgreSQL, Redis, MySQL, and MongoDB databases via Railway templates.

Community
Intermediate
ryasrkryasrk

cost-aware-model-routing

Assign LLM model tiers to agents based on task complexity and reasoning needs.

Community
Intermediate
Alex1980AlexAlex1980Alex

llm-rotation

Coordinate multi-provider LLM generation with automatic fallback and health checks.

Community
Advanced
AlbertLin821AlbertLin821
2

caveman-stats

Analyze Claude Code JSONL session logs to calculate token usage and cost savings.

Community
Basic