collaborating-with-kimi

Bridges Kimi CLI into Claude Code with session persistence and agent/context injection.

4|1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/rongarede/skill-snapshots --skill collaborating-with-kimi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: collaborating-with-kimi
Source: https://github.com/rongarede/skill-snapshots/tree/main/ai-collaboration/collaborating-with-kimi
Command: npx skills add https://github.com/rongarede/skill-snapshots --skill collaborating-with-kimi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

This Skill enables non-interactive Kimi CLI collaboration inside Claude Code, preserving sessions and injecting contextual agents for guided automation.

Core Features & Use Cases

  • Session persistence: Save and resume Kimi conversations across work sessions.
  • Context and agent injection: Load project context and assign a dedicated agent role for guided interactions.
  • Non-interactive bridging: Provide a CLI bridge to Kimi for automated workflows inside Claude Code.

Quick Start

Use the skill to bridge Kimi CLI with your project by invoking the included script: ~/.claude/skills/collaborating-with-kimi/scripts/kimi-agent.sh "Your task" --cd "/path/to/project"

Frequently Asked Questions about collaborating-with-kimi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Kimi CLI non-interactively inside Claude Code?

You run Kimi CLI non-interactively inside Claude Code by invoking the included kimi-agent.sh script, which bridges the two CLIs and passes your task string directly to Kimi for automated execution.

Can I maintain Kimi session persistence across multiple work sessions?

Yes, session persistence allows you to save and resume Kimi conversations across work sessions, managing session continuity so your multi-turn collaboration context is preserved.

How do I inject project context and an agent role into Kimi CLI?

You inject project context and an agent role into Kimi CLI using the bridging script, which loads your specific project environment and assigns a dedicated agent role for guided interactions.

Does the Kimi CLI bridge for Claude Code require any specific dependencies?

Yes, the Kimi CLI bridge requires jq to be installed in your environment to parse JSON and manage the context injection and session data for the automation workflows.

What is the best way to automate multi-turn Kimi collaboration in a project?

The best way to automate multi-turn Kimi collaboration is using a CLI bridge that maintains session persistence and injects contextual agents, enabling guided non-interactive workflows.