ax-provider-system

Manage AI provider contracts, categories, and plugin-based implementations.

5|2|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/project-ax/ax-legacy --skill ax-provider-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ax-provider-system
Source: https://github.com/project-ax/ax-legacy/tree/main/.claude/skills/ax-provider-system
Command: npx skills add https://github.com/project-ax/ax-legacy --skill ax-provider-system

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typescript, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The ax-provider-system Skill simplifies the management of AI provider configurations, allowing for easy addition, modification, and understanding of provider categories, loading, and plugin infrastructure.

Core Features & Use Cases

  • Provider Contract Pattern: Supports TypeScript interfaces for subsystems with pluggable implementations.
  • Provider Categories: Manages 15 different provider categories, such as llm, memory, channel, and database.
  • Provider Map: Allows static and plugin-based resolution of provider implementations.
  • Provider SDK: Provides tools for third-party provider authors to develop plugins.

Quick Start

Run 'ax-provider-system help' for information on how to configure providers or use the built-in SDK for plugin development.

Frequently Asked Questions about ax-provider-system

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

FAQPage Schema
How do I manage AI provider configurations for multiple categories?

Manage AI provider configurations through a contract pattern supporting 15 categories like llm, memory, channel, and database. The system enables easy addition, modification, and static or plugin-based resolution of implementations.

What is a provider contract pattern in TypeScript plugin development?

The provider contract pattern uses TypeScript interfaces to define subsystems with pluggable implementations. It establishes a clear contract for AI providers, enabling static resolution and dynamic plugin-based loading of third-party implementations.

How do I develop third-party plugins for an AI provider system?

Develop third-party AI provider plugins using the built-in Provider SDK. Run 'ax-provider-system help' to access configuration information and utilize the SDK tools designed specifically for plugin authors.

Do I need TypeScript to use a provider management system with pluggable implementations?

Yes, TypeScript is required as a dependency to use this provider management system. The provider contract pattern relies on TypeScript interfaces to define and manage contracts for subsystems with pluggable implementations.

Can I resolve AI provider implementations dynamically using a plugin-based system?

Yes, you can resolve AI provider implementations dynamically using a plugin-based system. The provider map supports both static and plugin-based resolution, allowing flexible integration of various provider categories.

What provider categories are supported by the ax-provider-system?

The ax-provider-system supports 15 different provider categories, including llm, memory, channel, and database. These categories cover a wide range of subsystems for comprehensive AI provider management.