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 agent", "provider not working", "API configuration", or "extend council".
How do I install this agent skill?
npx skills add https://github.com/hex/claude-council --skill provider-integrationIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides a framework and templates for integrating various AI providers into an agent council. It uses standard shell scripting practices, environment variables for secret management, and specialized tools like jq to ensure safe data handling when interacting with external APIs.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Adding AI Providers to Claude Council
Provider Script Interface
Each provider is a shell script in scripts/providers/ that:
- Accepts a prompt as the first argument
- Outputs the AI response to stdout
- Exits 0 on success, non-zero on failure
Quick Start
- Create
scripts/providers/{name}.sh(seeapi-patterns.mdfor templates) chmod +x scripts/providers/{name}.sh- Set
{NAME}_API_KEYenvironment variable - 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-6-astra |
| Grok | XAI_API_KEY (or GROK_API_KEY) | grok-latest |
| Perplexity | PERPLEXITY_API_KEY | low (Agent API preset) |
| Kimi | KIMI_API_KEY | kimi-k3 |
| Ollama | none (local) | first model ollama list shows |
| OpenRouter | OPENROUTER_API_KEY | anthropic/claude-fable-5.2 (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. claude-cli, copilot-cli and opencode are the exceptions: claude is on every user's PATH, each copilot question spends a premium request, and each opencode question bills whichever provider it is logged in to, so none has a discovery arm and each joins only when named in --providers or COUNCIL_PROVIDERS. 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. A CLI that times out or fails reports through cli_failure_message in scripts/lib/cli-stderr.sh: the timeout, or the last 500 bytes of the CLI's stderr with colour codes stripped.
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.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/hex/claude-council/provider-integration">View provider-integration on skillZs</a>