kimi-integration
Step-by-step guide for integrating Moonshot AI (Kimi) and Kimi Code models into Clawdbot. Use when someone asks how to add Kimi models, configure Moonshot AI, or set up Kimi for Coding in Clawdbot.
What this skill does
# Kimi Model Integration
Complete guide for adding Moonshot AI (Kimi) and Kimi Code models to Clawdbot.
## Overview
Kimi offers two separate model families:
1. **Moonshot AI (Kimi K2)** - General-purpose models via OpenAI-compatible API
2. **Kimi Code** - Specialized coding model with dedicated endpoint
Both require API keys from different sources.
## Prerequisites
- Clawdbot installed and configured
- API keys (see Getting API Keys section)
## Getting API Keys
### Moonshot AI (Kimi K2)
1. Visit https://platform.moonshot.cn
2. Register an account
3. Navigate to API Keys section
4. Create a new API key
5. Copy the key (starts with `sk-...`)
### Kimi Code
1. Visit https://api.kimi.com/coding
2. Register an account
3. Navigate to API Keys section
4. Create a new API key
5. Copy the key (starts with `sk-...`)
**Note:** Moonshot and Kimi Code use separate keys and endpoints.
## Integration Steps
### Option 1: Moonshot AI (Kimi K2 models)
#### Step 1: Set environment variable
```bash
export MOONSHOT_API_KEY="sk-your-moonshot-key-here"
```
Or add to `.env` file:
```bash
echo 'MOONSHOT_API_KEY="sk-your-moonshot-key-here"' >> ~/.env
```
#### Step 2: Add provider configuration
Edit your `clawdbot.json` config:
```json5
{
"agents": {
"defaults": {
"model": {
"primary": "moonshot/kimi-k2.5"
}
}
},
"models": {
"mode": "merge",
"providers": {
"moonshot": {
"baseUrl": "https://api.moonshot.cn/v1",
"apiKey": "${MOONSHOT_API_KEY}",
"api": "openai-completions",
"models": [
{
"id": "moonlight-v1-32k",
"name": "Moonlight V1 32K",
"contextWindow": 32768
},
{
"id": "moonshot-v1-8k",
"name": "Moonshot V1 8K",
"contextWindow": 8192
},
{
"id": "moonshot-v1-32k",
"name": "Moonshot V1 32K",
"contextWindow": 32768
},
{
"id": "moonshot-v1-128k",
"name": "Moonshot V1 128K",
"contextWindow": 131072
},
{
"id": "kimi-k2.5",
"name": "Kimi K2.5",
"contextWindow": 200000
}
]
}
}
}
}
```
#### Step 3: Restart Clawdbot
```bash
clawdbot gateway restart
```
#### Step 4: Verify integration
```bash
clawdbot models list
```
You should see Moonshot models in the list.
#### Step 5: Use the model
Set as default:
```bash
clawdbot models set moonshot/kimi-k2.5
```
Or use model aliases in chat:
```bash
/model moonshot/kimi-k2.5
```
### Option 2: Kimi Code (specialized coding model)
#### Step 1: Set environment variable
```bash
export KIMICODE_API_KEY="sk-your-kimicode-key-here"
```
Or add to `.env`:
```bash
echo 'KIMICODE_API_KEY="sk-your-kimicode-key-here"' >> ~/.env
```
#### Step 2: Add provider configuration
Edit your `clawdbot.json` config:
```json5
{
"agents": {
"defaults": {
"model": {
"primary": "kimicode/kimi-for-coding"
},
"models": {
"kimicode/kimi-for-coding": {
"alias": "kimi"
}
}
}
},
"models": {
"mode": "merge",
"providers": {
"kimicode": {
"baseUrl": "https://api.kimi.com/coding/v1",
"apiKey": "${KIMICODE_API_KEY}",
"api": "openai-completions",
"models": [
{
"id": "kimi-for-coding",
"name": "Kimi For Coding",
"contextWindow": 200000,
"maxTokens": 8192
}
]
}
}
}
}
```
#### Step 3: Restart Clawdbot
```bash
clawdbot gateway restart
```
#### Step 4: Verify integration
```bash
clawdbot models list
```
You should see `kimicode/kimi-for-coding` in the list.
#### Step 5: Use the model
Set as default:
```bash
clawdbot models set kimicode/kimi-for-coding
```
Or use model alias in chat:
```bash
/model kimi
```
## Using Both Providers
You can configure both Moonshot and Kimi Code simultaneously:
```json5
{
"agents": {
"defaults": {
"model": {
"primary": "moonshot/kimi-k2.5"
},
"models": {
"kimicode/kimi-for-coding": {
"alias": "kimi"
},
"moonshot/kimi-k2.5": {
"alias": "k25"
}
}
}
},
"models": {
"mode": "merge",
"providers": {
"moonshot": {
"baseUrl": "https://api.moonshot.cn/v1",
"apiKey": "${MOONSHOT_API_KEY}",
"api": "openai-completions",
"models": [
{ "id": "kimi-k2.5", "name": "Kimi K2.5", "contextWindow": 200000 }
]
},
"kimicode": {
"baseUrl": "https://api.kimi.com/coding/v1",
"apiKey": "${KIMICODE_API_KEY}",
"api": "openai-completions",
"models": [
{ "id": "kimi-for-coding", "name": "Kimi For Coding", "contextWindow": 200000 }
]
}
}
}
}
```
Switch between models using aliases:
- `/model k25` - Kimi K2.5 (general)
- `/model kimi` - Kimi for Coding (specialized)
## Troubleshooting
### Model not appearing in list
Check config syntax:
```bash
clawdbot gateway config.get | grep -A 20 moonshot
```
Verify API key is set:
```bash
echo $MOONSHOT_API_KEY
echo $KIMICODE_API_KEY
```
### Authentication errors
- Verify API key starts with `sk-`
- Check key is valid on provider dashboard
- Ensure correct base URL for each provider
### Connection issues
Test API endpoint directly:
```bash
curl -X POST "https://api.moonshot.cn/v1/chat/completions" \
-H "Authorization: Bearer $MOONSHOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "kimi-k2.5", "messages": [{"role": "user", "content": "test"}]}'
```
## Model Recommendations
- **Kimi K2.5** (`moonshot/kimi-k2.5`) - Best for general tasks, 200K context
- **Kimi for Coding** (`kimicode/kimi-for-coding`) - Specialized for code generation
- **Moonshot V1 128K** (`moonshot/moonshot-v1-128k`) - Legacy model, 128K context
## References
- Moonshot AI Docs: https://platform.moonshot.cn/docs
- Kimi Code API: https://api.kimi.com/coding/docs
- Clawdbot Model Providers: /home/eyurc/clawdbot/docs/concepts/model-providers.md
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.