provider-env-matrix

Validate provider configuration and API key management across shared and chatbot scopes.

7|2|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/SkastVnT/AI-Assistant --skill provider-env-matrix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: provider-env-matrix
Source: https://github.com/SkastVnT/AI-Assistant/tree/main/.github/skills/provider-env-matrix
Command: npx skills add https://github.com/SkastVnT/AI-Assistant --skill provider-env-matrix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Work safely with provider configuration, API keys, model routing, and environment dependencies for the core chatbot. Use when adding or changing an LLM provider, modifying API key loading, changing model defaults or fallback chains, debugging missing-key errors, or reviewing config drift across .env files.

Core Features & Use Cases

  • Enforces a single source of truth for provider keys and environment variables in config.py
  • Validates model registry, base URLs, and fallback chains across shared and chatbot scopes
  • Guides safe change management when adding or updating LLM providers or modifying config loading

Quick Start

Review your current provider setup and verify that environment variables, model registries, and shared env contracts align with the documented sources.

Frequently Asked Questions about provider-env-matrix

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

FAQPage Schema
How do I manage multiple LLM provider API keys in a single config file?

To manage multiple LLM provider API keys safely, this Skill enforces a single source of truth in config.py. It validates environment variables and shared env contracts to ensure predictable key loading across your chatbot scopes.

How do I configure model fallback chains for a multi-provider chatbot?

Configuring model fallback chains requires validating your model registry and base URLs across shared and chatbot scopes. This Skill reviews documented fallback behavior to ensure safe, predictable operation when a primary provider fails.

Why does my chatbot throw a missing API key error during provider routing?

A missing API key error occurs when environment variables drift from the documented sources. This Skill debugs missing-key errors by validating environment files and verifying that config.py loading aligns with shared env contracts.

What is the best way to add a new LLM provider to an existing chatbot environment?

The best way to add a new LLM provider is through guided change management. This Skill validates base URLs, model registries, and fallback chains to ensure safe integration without disrupting existing environment variables.

How does environment file validation work for multi-provider model routing?

Environment file validation for model routing works by checking config drift across .env files. This Skill enforces a single source of truth in config.py, ensuring API key loading and provider defaults match the shared env contracts.

Can I use this to modify config loading for changing API key defaults?

Yes, you can use this to modify config loading and change API key defaults safely. It guides change management when updating provider configuration, ensuring that model defaults and fallback chains remain valid across scopes.