create-agent-kimi-code

Generates and validates Kimi Code agent projections from canonical PoP role definitions.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/gabesan21/project-of-projects --skill create-agent-kimi-code-gabesan21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-agent-kimi-code
Source: https://github.com/gabesan21/project-of-projects/tree/main/.agents/skills/create-agent-kimi-code
Command: npx skills add https://github.com/gabesan21/project-of-projects --skill create-agent-kimi-code-gabesan21

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Projecting PoP's six canonical specialist roles into Kimi Code agent Markdown and configuration is error-prone when done by hand: tool allowlists, model routing, and the canonical body can drift or lose guarantees. This Skill generates deterministic agent files and candidate configs, then validates them locally without ever invoking Kimi Code, a model, or the network. ## Core Features & Use Cases - Deterministic agent generation: Builds Kimi Code agent Markdown from .agents/agents/<role>.md, preserving the complete canonical body with a SHA-256 source marker and fail-closed tool/subagent policies per role. - Symbolic model routing: Assigns primary routing to Planner and Judge roles and secondary routing to recon, orchestrator, executor, and verifier roles, resolving secondary through a [secondary_model] candidate config fixed to kimi-for-coding (K2.7). - Fail-closed local validation: Parses candidate TOML with tomllib, rejects unknown frontmatter fields, undemonstrated guarantees (effective effort, max nesting, aggregate validation), and K2.7 medium-effort claims, exiting BLOCKED on any violation. - Use Case: After editing the canonical pop-executor role, run the build command to regenerate its Kimi Code agent with secondary routing and a candidate config, then run validate to confirm the projection matches the source byte-for-byte before committing. ## Quick Start Ask the agent to project the pop-executor role into a Kimi Code agent with secondary routing and validate the result against the canonical source.

Frequently Asked Questions about create-agent-kimi-code

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

FAQPage Schema
How do I create a Kimi Code agent from a canonical role definition?▼

Run the build command of scripts/build_agent.py with --source pointing to the canonical role file, --agent-out for the output, and --routing set to primary or secondary. The script preserves the complete canonical body and applies the role's fixed tool and subagent allowlists.

How do I validate a generated Kimi Code agent without running Kimi Code?▼

Use the validate subcommand with the source role, generated agent, routing, and optional candidate config. It re-renders the deterministic projection, compares it byte-for-byte, checks the SHA-256 source marker, and parses the TOML config with tomllib, all locally.

Which roles use primary versus secondary model routing?▼

The Planner and Judge roles use primary routing, which resolves to the current main model. Recon, execution orchestrator, executor, and phase verifier use secondary routing, resolved through a [secondary_model] config section fixed to kimi-for-coding (K2.7).

Can I set medium effort for the K2.7 secondary model?▼

No. The build script rejects medium effort for K2.7 because its boolean Thinking flag does not demonstrate that effort level. Attempting it causes a BLOCKED failure during config generation or validation.

What guarantees can this projection not provide?▼

It cannot guarantee effective model-plus-effort per spawn, maximum agent nesting depth, or aggregate runtime validation across agents. Requesting any of these via --require-guarantee causes an immediate BLOCKED exit.

Why does validation fail with a BLOCKED error on my agent file?▼

Validation fails when the agent differs from the deterministic projection, contains unknown frontmatter fields, has a modified canonical body, or when the candidate config lacks [secondary_model]. The error message names the specific violation.