Skip to main content
skaro config manages your LLM provider settings and API keys. You can also view the current configuration.

​
Usage

If no options are passed, --show is implied.

​
Examples

Set up Groq with an API key:
Switch to Ollama (no key needed):
Change only the model (keep current provider):
View current settings:
Output:

​
Provider Defaults

When you set a provider without specifying a model, Skaro uses the provider’s default:

​
Where Settings Are Stored

Configuration is saved to .skaro/config.yaml:
API keys are saved to .skaro/secrets.yaml, which is automatically added to .gitignore by skaro init. Never commit this file.

​
API Key Resolution

Skaro resolves API keys in this order:
  1. Environment variable — the variable named in api_key_env (e.g., GROQ_API_KEY)
  2. secrets.yaml — .skaro/secrets.yaml
  3. Provider preset — the default env var for the provider (e.g., ANTHROPIC_API_KEY for Anthropic)
If you prefer environment variables over secrets.yaml, just export the variable and Skaro will find it:

​
Advanced Configuration

For role-based routing, verify commands, import settings, and other advanced options, use the web dashboard or edit .skaro/config.yaml directly. See Role-Based Routing, Dashboard Configuration, and Skills for details.