ai-orchestration

Manage and rotate LLM API keys across multiple providers.

1|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/layeddie/ai-rules --skill ai-orchestration-layeddie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-orchestration
Source: https://github.com/layeddie/ai-rules/tree/main/skills/ai-orchestration
Command: npx skills add https://github.com/layeddie/ai-rules --skill ai-orchestration-layeddie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and secures LLM API keys across multiple providers, enabling seamless multi-provider access and governance for AI workflows.

Core Features & Use Cases

  • Keyring storage and retrieval for providers such as OpenAI, Claude, Groq, and OpenRouter.
  • A multi-provider client that routes requests to the selected provider and supports automatic provider selection.
  • A director → implementor pattern to coordinate complex AI orchestration across agents and tasks.
  • Real-world use case: manage credentials, orchestrate a multi-LLM chat, and switch providers without code changes.

Quick Start

Start by initializing the keyring and registering a provider, then query a key for a given provider.

Frequently Asked Questions about ai-orchestration

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

FAQPage Schema
How do I manage and rotate LLM API keys across multiple providers?

Manage and rotate LLM API keys across multiple providers by centralizing them in a keyring storage system. This secures credentials for OpenAI, Anthropic, Groq, and OpenRouter while enabling seamless multi-provider access and governance for AI workflows.

Can I switch LLM providers during a chat without changing my application code?

Yes, you can switch LLM providers during a chat without changing code. A multi-provider client routes requests to the selected provider and supports automatic provider selection, allowing seamless switching across OpenAI, Anthropic, Groq, OpenRouter, and local runtimes.

What is the director implementor pattern for AI agent orchestration?

The director implementor pattern is an AI agent orchestration architecture that coordinates complex AI workflows across agents and tasks. It uses a director to delegate execution to implementors, enabling scalable and structured multi-LLM conversations.

How do I initialize a keyring and register an LLM provider in Elixir?

Initialize a keyring and register an LLM provider in Elixir by starting with keyring initialization, adding your provider credentials, and then querying the key for that specific provider to authenticate your multi-provider client requests.

Does this multi-provider LLM client support local LLM runtimes?

Yes, the multi-provider LLM client supports local LLM runtimes. It applies across OpenAI, Anthropic, Groq, OpenRouter, and local environments to orchestrate conversations and provider selection in various task scenarios.

Why centralize LLM API keys instead of hardcoding them in my AI workflows?

Centralize LLM API keys to improve security and apply governance across AI workflows. Hardcoding credentials risks exposure, whereas a keyring enables secure storage, retrieval, and rotation across multiple providers without code changes.