providers

rozwer's avatarfrom rozwer

Use when integrating multiple LLM providers. Keep provider-specific code isolated behind a small interface.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 29, 2025

When & Why to Use This Skill

This Claude skill provides a robust framework for integrating multiple LLM providers using a clean adapter pattern. By isolating provider-specific logic behind a standardized interface, it enables developers to maintain a modular codebase, simplify API maintenance, and ensure consistent data normalization across different AI models.

Use Cases

  • Multi-Model Integration: Seamlessly switch between different LLM providers (e.g., OpenAI, Anthropic, Cohere) without refactoring core application logic.
  • Response Normalization: Standardize varying API response structures into a unified format to ensure reliable data processing across the entire software stack.
  • Secure Environment Management: Enhance application security by isolating sensitive API credentials and secrets using environment variables instead of hardcoding them.
  • Architectural Scalability: Implement a scalable 'plug-and-play' architecture that allows for the rapid addition of new AI services as they become available.
nameproviders
descriptionUse when integrating multiple LLM providers. Keep provider-specific code isolated behind a small interface.

Guidelines

  • Use an adapter/interface per provider.
  • Normalize request/response shapes at the boundary.
  • Keep secrets out of repo; use environment variables.