Menu

Individual skill

neatcontext-create

Create a fresh NeatContext context from a user-defined behavioral profile and an existing local knowledge folder. Use only when the user explicitly invokes this skill or asks to create a new context rather than save the current conversation.

plugins/kimi-code/neatcontext/skills/create/SKILL.md

Read pinned source

Source commit 8a3f25b072487dfcbaf267e9894468fbef9d056a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Local scripts
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
13
Repository last updated
Aug 23, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Create context

The bundled CLI path and Kimi session id below are expanded by Kimi Code at skill activation.

Keep this workflow distinct from `/neatcontext:save`: create starts from user-provided purpose and existing knowledge; save distills work already in the conversation.

Collect these inputs, asking one question at a time only for information the user has not already supplied:

1. What the context covers, what Kimi Code should do and avoid, and how it should behave.
2. The path to an existing folder containing its knowledge.
3. A short context name.

Run `list` before drafting so the routing description can distinguish adjacent contexts: