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

​
Usage

skaro config [OPTIONS]
OptionDescription
--providerLLM provider: anthropic, openai, groq, or ollama
--model TEXTModel name or ID
--api-key TEXTAPI key (saved securely to .skaro/secrets.yaml)
--showDisplay current configuration
If no options are passed, --show is implied.

​
Examples

Set up Groq with an API key: 
skaro config --provider groq --api-key gsk_your_key_here
Switch to Ollama (no key needed): 
skaro config --provider ollama --model qwen3:32b
Change only the model (keep current provider): 
skaro config --model claude-opus-4-6
View current settings: 
skaro config --show
Output: 
┌─────────────────┬──────────────────────────┐
│ Key             │ Value                    │
├─────────────────┼──────────────────────────┤
│ LLM Provider    │ groq                     │
│ Model           │ llama-3.3-70b-versatile  │
│ API Key Env     │ GROQ_API_KEY             │
│ API Key Resolved│ ✓                        │
│ Language        │ en                       │
└─────────────────┴──────────────────────────┘

​
Provider Defaults

When you set a provider without specifying a model, Skaro uses the provider’s default:
ProviderDefault Model
anthropicclaude-sonnet-4-6
openaigpt-5.2
groqllama-3.3-70b-versatile
ollamaqwen3:32b

​
Where Settings Are Stored

Configuration is saved to .skaro/config.yaml: 
llm:
  provider: groq
  model: llama-3.3-70b-versatile
  api_key_env: GROQ_API_KEY
  max_tokens: 16384
  temperature: 0.3
lang: en
theme: dark
project_name: my-project
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: 
export GROQ_API_KEY=gsk_your_key_here

​
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 and Dashboard Configuration for details.