llm-integrations

Configure multi-provider LLM integrations with API key management, cost controls, and throttling.

44|9|Updated May 7, 2026
One-click install
npx skills add https://github.com/Omar-Obando/qwen-orchestrator --skill llm-integrations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-integrations
Source: https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/llm-integrations
Command: npx skills add https://github.com/Omar-Obando/qwen-orchestrator --skill llm-integrations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of securely integrating multiple LLM providers while controlling spend, managing rate limits, and ensuring reliable fallbacks across projects.

Core Features & Use Cases

  • Provider setup & authentication: Configure API keys for OpenAI, DeepSeek, OpenRouter, Anthropic, and Google, including environment-variable workflows.
  • Cost optimization: Apply model selection guidance, track tokens/costs, and reduce spend with cost-aware routing.
  • Reliability & governance: Implement request throttling (rate limiting), error handling patterns, and multi-provider fallback strategies.

Quick Start

Ask your AI assistant to help you set up API keys and a cost-optimized, rate-limited multi-provider LLM calling strategy for your current project.

Frequently Asked Questions about llm-integrations

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

FAQPage Schema
How do I configure multiple LLM providers with API keys and rate limiting?

Configuring multiple LLM providers involves using YAML-defined skill metadata to establish environment-variable workflows for API key authentication, while applying request throttling to manage rate limits and ensure reliable fallbacks across projects.

What is the best way to manage OpenAI and OpenRouter costs during model selection?

Managing OpenAI and OpenRouter costs requires applying cost-aware routing and model selection guidance to track token usage, optimize spend, and automatically reduce costs across general reasoning and coding tasks.

How do I set up multi-provider fallback strategies for LLM integration?

Setting up multi-provider fallback strategies involves implementing operational guidance and error-handling patterns that route requests to alternative providers like Anthropic or Google when primary API calls fail or hit rate limits.

Can I use environment variables to securely authenticate LLM API keys for my project?

Yes, you can use environment-variable workflows to securely authenticate API keys for supported LLM providers including OpenAI, DeepSeek, OpenRouter, Anthropic, and Google within your current project setup.

Why does my LLM integration fail when request throttling is not configured?

LLM integrations often fail without request throttling because providers enforce strict rate limits, so implementing proper error-handling patterns and request throttling is required to prevent API failures and ensure reliable fallback behavior.