Skills no longer come from the user's ~/.agents library - most users have none, and the CEO branch that compiled the entire catalogue into its prompt overflowed the model context (1.1MB) and failed every CEO run. - Bundle "built-in skills/" with the app (extraResources) and stage it at startup into <profile>/builtin-skills as one dir-per-skill copy - both bundle shapes (SKILL.md dirs and flat category .md files) normalize into the same importable layout - Import the staged catalogue per org at startup and inside onboarding, so the CEO's first run already carries it - Forced house style: resolveRuntimeSnapshot unions the humanizer skill into every agent's runtime (CEO included) as a resolution rule - no binding row to forget, delete, or bypass; revoke_skill refuses it - CEO staffs hires with skills: hire_agent accepts a skills array, grant_skill/revoke_skill adjust later, list_skills now shows descriptions from skill frontmatter - Kill the c_suite compile-all branch; everyone resolves bindings-only, capped at 200k chars with omissions named in the prompt - Remove the Skills settings page and its import/sync/test IPC surface; drop ~/.agents discovery and the AGENTCOMPANY_NEW_SKILLS_ROOT seam in favor of AGENTCOMPANY_NEW_BUILTIN_SKILLS_DIR - Tests: staging/import/forced-resolution/cap units, real-bundle CI check, e2e asserts the tab is gone and the catalogue self-imports
109 lines
2.0 KiB
Markdown
109 lines
2.0 KiB
Markdown
# Kimi Code CLI Integration
|
|
|
|
Converts all Agency agents into Kimi Code CLI agent specifications. Each agent
|
|
becomes a directory containing `agent.yaml` (agent spec) and `system.md` (system
|
|
prompt).
|
|
|
|
## Installation
|
|
|
|
### Prerequisites
|
|
|
|
- [Kimi Code CLI](https://github.com/MoonshotAI/kimi-cli) installed
|
|
|
|
### Install
|
|
|
|
```bash
|
|
# Generate integration files (required on fresh clone)
|
|
./scripts/convert.sh --tool kimi
|
|
|
|
# Install agents
|
|
./scripts/install.sh --tool kimi
|
|
```
|
|
|
|
This copies agents to `~/.config/kimi/agents/`.
|
|
|
|
## Usage
|
|
|
|
### Activate an Agent
|
|
|
|
Use the `--agent-file` flag to load a specific agent:
|
|
|
|
```bash
|
|
kimi --agent-file ~/.config/kimi/agents/frontend-developer/agent.yaml
|
|
```
|
|
|
|
### In a Project
|
|
|
|
```bash
|
|
cd /your/project
|
|
kimi --agent-file ~/.config/kimi/agents/frontend-developer/agent.yaml \
|
|
--work-dir /your/project \
|
|
"Review this React component for performance issues"
|
|
```
|
|
|
|
### List Installed Agents
|
|
|
|
```bash
|
|
ls ~/.config/kimi/agents/
|
|
```
|
|
|
|
## Agent Structure
|
|
|
|
Each agent directory contains:
|
|
|
|
```
|
|
~/.config/kimi/agents/frontend-developer/
|
|
├── agent.yaml # Agent specification (tools, subagents)
|
|
└── system.md # System prompt with personality and instructions
|
|
```
|
|
|
|
### agent.yaml format
|
|
|
|
```yaml
|
|
version: 1
|
|
agent:
|
|
name: frontend-developer
|
|
extend: default # Inherits from Kimi's built-in default agent
|
|
system_prompt_path: ./system.md
|
|
tools:
|
|
- "kimi_cli.tools.shell:Shell"
|
|
- "kimi_cli.tools.file:ReadFile"
|
|
# ... all default tools
|
|
```
|
|
|
|
## Regenerate
|
|
|
|
After modifying source agents:
|
|
|
|
```bash
|
|
./scripts/convert.sh --tool kimi
|
|
./scripts/install.sh --tool kimi
|
|
```
|
|
|
|
## Troubleshooting
|
|
|
|
### Agent file not found
|
|
|
|
Ensure you've run `convert.sh` before `install.sh`:
|
|
|
|
```bash
|
|
./scripts/convert.sh --tool kimi
|
|
```
|
|
|
|
### Kimi CLI not detected
|
|
|
|
Make sure `kimi` is in your PATH:
|
|
|
|
```bash
|
|
which kimi
|
|
kimi --version
|
|
```
|
|
|
|
### Invalid YAML
|
|
|
|
Validate the generated files:
|
|
|
|
```bash
|
|
python3 -c "import yaml; yaml.safe_load(open('integrations/kimi/frontend-developer/agent.yaml'))"
|
|
```
|