skills.rest
majiayu000
majiayu000COMMUNITY
Explore all skills by this author →
GitHub

provider-development

Document architecture and best practices for adding and migrating LiteLLM-RS providers.

104|19|Updated Jul 15, 2025
Search Tags:#architecture#migration#error-handling#gateway#provider-development#LiteLLM-RS
One-click install
npx skills add https://github.com/majiayu000/litellm-rs --skill provider-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: provider-development
Source: https://github.com/majiayu000/litellm-rs/tree/main/.claude/skills/provider-development
Command: npx skills add https://github.com/majiayu000/litellm-rs --skill provider-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates architecture, error handling, and migration practices for adding and maintaining 66+ providers within LiteLLM-RS gateway.

Core Features & Use Cases

  • Unified error handling guidelines across all providers to ensure consistent failure semantics.
  • Migration strategies and tooling guidance for consolidating existing provider errors into the shared ProviderError surface.
  • Provider registration, testing, and model information workflows to support scalable evolution.

Quick Start

Apply this guide when designing a new provider or migrating an existing one to the unified error model. Example: outline a provider module, implement the ProviderError mappings, and run the provider registry tests to verify compatibility.

Frequently Asked Questions about provider-development

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

FAQPage Schema
How do I add a new provider to the LiteLLM-RS gateway?▼

Migrate legacy provider errors by consolidating them into the shared ProviderError surface, ensuring consistent failure semantics across all 66+ providers in the LiteLLM-RS gateway.

What is unified error handling for providers in LiteLLM-RS?▼

Unified error handling in LiteLLM-RS maps provider-specific failures into a shared ProviderError surface, ensuring consistent failure semantics and maintainability across 66+ gateway providers.

How do I migrate legacy errors to the unified ProviderError model?▼

Migrate legacy provider errors by consolidating them into the shared ProviderError surface using documented migration strategies, ensuring consistent failure semantics across all 66+ providers in the LiteLLM-RS gateway.

Can I use the LiteLLM-RS provider development guidelines for migrating existing providers?▼

Yes, the guidelines support migrating existing providers by specifying deployment migration steps, unified error handling, and registration workflows to maintain consistency across 66+ providers.

What are the steps to register and test a provider in the LiteLLM-RS gateway?▼

Register and test a provider by outlining the provider module, implementing the ProviderError mappings, and running the provider registry tests to verify compatibility and maintain consistency.

Why do I need unified error handling when developing providers for LiteLLM-RS?▼

Unified error handling is needed to ensure consistent failure semantics across 66+ providers, enabling scalable evolution and reliable error-migration within the LiteLLM-RS gateway architecture.

Related Skills

Explore More Software Engineering Skills→
merge-apimerge-api
1

Migrate LiteLLM to Merge Gateway

Detect LiteLLM usage and guide migration to Merge Gateway SDK.

Official
Advanced
blinqasblinqas
9

terraform-test

Run unit and integration tests against Terraform modules.

Official
Advanced
BagelHoleBagelHole
46

llm-gateway

Deploy a unified API gateway for LLM traffic with load balancing and rate limiting.

Community
Advanced
majiayu000majiayu000
104

provider-architecture

Implement the LLMProvider trait to integrate 66+ LLM providers in Rust gateways.

Community
Advanced