Skip to content
Development
Skill

/provider-integration

Adds new AI providers to claude-council, configures provider API settings, troubleshoots provider connections, and documents the provider script interface. Covers creating provider shell scripts, setting API keys, and validating connectivity. Triggers on "add provider", "new AI

From plugin
claude-council
7394 skills1 agent4 commands1 hook
Install
$ npx -y skills add hex/claude-council --skill provider-integration --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/provider-integration

Context preview

The summary Claude sees to decide when to auto-load this skill.

Adds new AI providers to claude-council, configures provider API settings, troubleshoots provider connections, and documents the provider script interface. Covers creating provider shell scripts, setting API keys, and validating connectivity. Triggers on "add provider", "new AI

SKILL.md

provider-integration.SKILL.md
name: provider-integration
description: Adds new AI providers to claude-council, configures provider API settings, troubleshoots provider connections, and documents the provider script interface. Covers creating provider shell scripts, setting API keys, and validating connectivity. Triggers on "add provider", "new AI agent", "provider not working", "API configuration", or "extend council".

Adding AI Providers to Claude Council

Provider Script Interface

Each provider is a shell script in `scripts/providers/` that: 1. Accepts a prompt as the first argument 2. Outputs the AI response to stdout 3. Exits 0 on success, non-zero on failure

Quick Start

1. Create `scripts/providers/{name}.sh` (see `api-patterns.md` for templates) 2. `chmod +x scripts/providers/{name}.sh` 3. Set `{NAME}_API_KEY` environment variable 4. Test: `./scripts/providers/{name}.sh "Hello"`

Current Providers

| Provider | API Key Variable | Default Model | |----------|------------------|---------------| | Gemini | `GEMINI_API_KEY` | gemini-flash-latest | | OpenAI | `OPENAI_API_KEY` | gpt-5.6-sol | | Grok | `XAI_API_KEY` (or `GROK_API_KEY`) | grok-latest | | Perplexity | `PERPLEXITY_API_KEY` | sonar-reasoning-pro | | Kimi | `KIMI_API_KEY` | kimi-k3 | | Ollama | none (local) | first model `ollama list` shows | | OpenRouter | `OPENROUTER_API_KEY` | anthropic/claude-sonnet-5 (or one seat per `OPENROUTER_MODELS` entry) |

CLI providers (`codex`, `antigravity`, `grok-cli`, `kimi-cli`, `cursor-cli`) need no key: they are discovered when their binary is on `PATH` and use that CLI's own login. See `scripts/providers/kimi-cli.sh` and `cursor-cli.sh` for the headless-run pattern: a read-only mode, a JSON output format the answer is parsed from, `--model` only on an explicit `*_CLI_MODEL` override, and `run_with_deadline` in place of the API providers' retry.

Troubleshooting

  • **Not discovered**: Check API key is set and script is executable
  • **API errors**: Verify key, check rate limits, confirm model name
  • **Parse fails**: Add `echo "$RESPONSE"` to debug, check response format

Reference

For API patterns and code templates, see `api-patterns.md` in this directory.

Read more
Ships withclaude-council

A Claude Code plugin that consults multiple AI coding agents in parallel and shows you their answers side-by-side.

Get the whole plugin

Other skills on claude-council.