playbooks

home / skills / plurigrid / asi / kimi-cli-help

kimi-cli-help skill

/skills/kimi-cli-help

This skill helps users understand and troubleshoot Kimi Code CLI usage, installation, and configuration through official docs and source insights.

npx playbooks add skill plurigrid/asi --skill kimi-cli-help

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.0 KB
---
name: kimi-cli-help
description: Answer Kimi Code CLI usage, configuration, and troubleshooting questions. Use when user asks about Kimi Code CLI installation, setup, configuration, slash commands, keyboard shortcuts, MCP integration, providers, environment variables, how something works internally, or any questions about Kimi Code CLI itself.
---

# Kimi Code CLI Help

Help users with Kimi Code CLI questions by consulting documentation and source code.

## Strategy

1. **Prefer official documentation** for most questions
2. **Read local source** when in kimi-cli project itself, or when user is developing with kimi-cli as a library (e.g., importing from `kimi_cli` in their code)
3. **Clone and explore source** for complex internals not covered in docs - **ask user for confirmation first**

## Documentation

Base URL: `https://moonshotai.github.io/kimi-cli/`

Fetch documentation index to find relevant pages:

```
https://moonshotai.github.io/kimi-cli/llms.txt
```

### Page URL Pattern

- English: `https://moonshotai.github.io/kimi-cli/en/...`
- Chinese: `https://moonshotai.github.io/kimi-cli/zh/...`

### Topic Mapping

| Topic | Page |
|-------|------|
| Installation, first run | `/en/guides/getting-started.md` |
| Config files | `/en/configuration/config-files.md` |
| Providers, models | `/en/configuration/providers.md` |
| Environment variables | `/en/configuration/env-vars.md` |
| Slash commands | `/en/reference/slash-commands.md` |
| CLI flags | `/en/reference/kimi-command.md` |
| Keyboard shortcuts | `/en/reference/keyboard.md` |
| MCP | `/en/customization/mcp.md` |
| Agents | `/en/customization/agents.md` |
| Skills | `/en/customization/skills.md` |
| FAQ | `/en/faq.md` |

## Source Code

Repository: `https://github.com/MoonshotAI/kimi-cli`

When to read source:

- In kimi-cli project directory (check `pyproject.toml` for `name = "kimi-cli"`)
- User is importing `kimi_cli` as a library in their project
- Question about internals not covered in docs (ask user before cloning)

Overview

This skill answers questions about the Kimi Code CLI: installation, setup, configuration, commands, shortcuts, MCP integration, providers, and environment variables. It prioritizes official documentation and inspects local source when the user is developing with kimi-cli or asks about internals. For deep internal questions I will ask for permission before cloning or exploring the project code.

How this skill works

I first consult the official documentation index and mapped topic pages to find authoritative guidance. If the user is working inside the kimi-cli project or imports kimi_cli as a library, I read the local source to explain behavior and APIs. For complex internals not covered in docs, I offer to clone and explore the code after obtaining user confirmation.

When to use it

  • Installing or upgrading Kimi Code CLI
  • Configuring providers, models, or environment variables
  • Understanding slash commands, CLI flags, or keyboard shortcuts
  • Troubleshooting MCP integration or agent/skill behavior
  • Explaining how a CLI feature works internally when developing with kimi-cli

Best practices

  • Start with the official docs pages for getting-started and configuration before changing files
  • Keep provider credentials and API keys in environment variables, not committed config files
  • When debugging, reproduce the issue in a minimal environment and capture CLI logs or verbose output
  • Ask for permission before sharing or requesting local code exploration; that preserves user privacy and minimizes unnecessary cloning
  • When modifying MCP, agents, or skills, test changes in a sandboxed profile to avoid affecting production state

Example use cases

  • Walk a user through installing Kimi Code CLI on macOS, Windows, or Linux
  • Explain how to set provider credentials via env vars and verify they are loaded
  • Describe available slash commands and keyboard shortcuts and how to customize them
  • Help integrate a new model provider into the CLI configuration and validate requests
  • Troubleshoot MCP behavior by checking configuration files and suggesting targeted tests

FAQ

Can you edit my local kimi-cli installation to fix a problem?

I can guide you step-by-step. If you want me to inspect local source files I will ask for permission and describe exactly what I will read or run. I do not change files without your explicit instruction.

Where do I find CLI flags and command references?

The reference page for the main command and flags is available in the official docs; I will point you to the exact page and summarize key flags if you ask.