メニュー
Use when an agent needs to work with KitKit through kitkit-cli: authenticate, choose spaces, understand the KitKit space/session/topology/shared-memory/insight/fork mental model, parse JSON output, or prepare for Kitty-like global conversation-tree work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use when an agent should behave like KitKit Kitty: maintain global space awareness, read shared memory early, treat it as possibly stale, inspect conversation-tree digests, push useful insights, update durable memory, or create forks through kitkit-cli.
Use when an agent needs to treat a KitKit or Stello conversation tree as a document library: inspect topology, choose relevant session nodes, read targeted digests, compare branches, or build space-level context without loading full transcripts.
Use when an agent needs to create or plan KitKit fork sessions with kitkit-cli: choose source sessions, select none/inherit/compress context, apply fork profiles, attach skills, pass prompts, or place topology nodes.
Use when an agent needs to push, update, or reason about KitKit insights: cross-session findings, contradictions, warnings, reusable context, target-session selection, overwrite safety, and concise insight content.
SOC 職業分類に基づく
| name | kitkit-cli |
| description | Use when an agent needs to work with KitKit through kitkit-cli: authenticate, choose spaces, understand the KitKit space/session/topology/shared-memory/insight/fork mental model, parse JSON output, or prepare for Kitty-like global conversation-tree work. |
Use kitkit-cli as the command-line access layer for KitKit space-level work.
topology shows the tree, including session ids, labels, status, turn counts, and children.digest reads one session's L2 view: metadata, memory summary, and current insight.insight writes one cross-session finding into one target session's insight slot.shared-memory stores durable space-level context.fork creates a child session from a source session.Do not treat the CLI as ordinary chat. It is for global awareness, cross-node coordination, durable memory, and forks.
Start with authentication and space selection:
kitkit-cli auth status
kitkit-cli spaces list
kitkit-cli spaces get <SPACE_ID>
kitkit-cli topology <SPACE_ID>
Use spaces get when the label alone is not enough and human-facing space metadata matters.
Use --json whenever output will be parsed, compared, summarized mechanically, or passed between tools:
kitkit-cli --json spaces list
kitkit-cli --json topology <SPACE_ID>
kitkit-cli --json digest <SPACE_ID> <SESSION_ID>
Use human-readable output for quick inspection.
Read shared memory early when acting with Kitty-like global context:
kitkit-cli shared-memory list <SPACE_ID>
Write shared memory only for durable facts such as user preferences, project background, long-lived goals, or stable constraints:
kitkit-cli shared-memory upsert <SPACE_ID> <SLUG> --body-file memory.md
cat memory.md | kitkit-cli shared-memory upsert <SPACE_ID> <SLUG> --stdin
Delete only when the entry is wrong or obsolete:
kitkit-cli shared-memory delete <SPACE_ID> <SLUG>
Shared memory is global to the space. Do not use it for temporary notes, one-session findings, or anything that belongs in an insight.
Treat live CLI help as the command authority:
kitkit-cli --help
kitkit-cli shared-memory --help
kitkit-cli insight put --help
kitkit-cli fork --help
Prefer fixing kitkit-cli help or behavior in the CLI repo if the tool surface is confusing. Do not paper over framework or CLI problems in a skill.