providers

Switch between LLM providers and access raw SDKs via get_provider().

3|Updated Aug 17, 2025
One-click install
npx skills add https://github.com/juanre/llmring --skill providers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: providers
Source: https://github.com/juanre/llmring/tree/main/skills/providers
Command: npx skills add https://github.com/juanre/llmring --skill providers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing multiple LLM providers (OpenAI, Anthropic, Google, Ollama) often means dealing with different APIs and SDKs, hindering flexibility and access to unique features. This Skill unifies access and enables provider-specific optimizations, saving you integration effort.

Core Features & Use Cases

  • Unified Provider Access: Switch between LLM providers with minimal code changes, leveraging a consistent interface for core functionalities.
  • Raw SDK Access: Directly access underlying provider SDKs (e.g., openai.AsyncOpenAI) for advanced, provider-specific features like OpenAI's logprobs or Anthropic's prompt caching.
  • Multi-Provider Fallbacks: Configure automatic failover to alternative providers in case of outages or rate limits, ensuring application resilience and continuous operation.
  • Use Case: Optimize costs by trying a cheaper provider first, then falling back to a more expensive but reliable one, or use Anthropic's prompt caching for long system prompts to save up to 90% on token costs.

Quick Start

Use the providers skill to get the raw OpenAI client and make a chat completion request to 'gpt-4o' with 'logprobs' enabled.

Frequently Asked Questions about providers

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

FAQPage Schema
How do I switch between multiple LLM providers like OpenAI, Anthropic, and Google in the same application?

Switching between LLM providers uses a unified interface that abstracts provider differences. This Skill provides get_provider() to return a consistent wrapper around each provider, letting you swap providers with minimal code changes while maintaining the same core API across OpenAI, Anthropic, Google Gemini, and Ollama.

Can I access provider-specific features like OpenAI's logprobs or Anthropic's prompt caching?

Yes, raw SDK access is available through the .client property on each provider wrapper. You can directly use OpenAI's AsyncOpenAI or Anthropic's SDK to unlock provider-specific features including logprobs, prompt caching, and custom parameters without losing the multi-provider abstraction layer.

What's the best way to set up automatic failover between LLM providers?

Configure multi-provider fallbacks by defining backup providers that activate on outages or rate limits. The Skill supports chaining providers so requests automatically retry with an alternative if the primary fails, ensuring resilience across OpenAI, Anthropic, Google, and Ollama without manual intervention.

Do I need to manually initialize SDK credentials for each provider?

No, providers auto-initialize from environment variables. The Skill reads standard provider credentials and API keys automatically, eliminating manual setup for OpenAI, Anthropic, Google Gemini, and Ollama—you only configure env vars once.

How can I reduce LLM costs while maintaining reliability across providers?

Use provider switching to route requests to cheaper models first, then fall back to premium providers if needed. Anthropic's prompt caching saves up to 90% on token costs for repeated long system prompts, combining cost optimization with failover protection in multi-provider setups.