菜单
Use when the user mentions Kai, @kai, kai CLI, founder ops, company-building workflows, Eidos internal operations, platform provisioning guardrails, Slack operations through Kai, deploy routing, idea capture, or Kai feedback.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user asks about Eidos, Eidos AGI, platform status, `eidos do`, closeout, cleanup before done, docket-task orchestration, evidence verification, praxis learning, gateway routing, vault/secrets, plugins, or which Eidos AGI specialist system should handle a task. This skill tells Codex to call the installed `eidos` CLI first; MCP and plugins should only point to CLIs, while CLIs provide progressive reveal of the deeper tool graph.
Investigate current context before predicting likely futures, failures, user objections, and concrete changes. Use when Zoltar needs to research an app, plugin, architecture, workflow, plan, decision, or implementation and answer what is likely to go wrong, what evidence supports it, what complaint or failure is being prevented, and what should change today.
Answer a specific foresight decision question with researched evidence, a clear judgment, likely futures, user complaint prediction, and concrete changes. Use when Daniel asks whether an idea, implementation, plugin, architecture, or workflow is likely to be regretted, whether it is the right thing in the right place with the right authority, or what decision should be made given future effects.
Compatibility entrypoint for Zoltar foresight. Use when Daniel mentions Zoltar, asks to predict the future, asks for second-order effects, asks what he will complain about, or wants future-backed product/spec changes; route the work through researched evidence, judgment, structured output, doer/checker handoff, and self-improvement notes rather than generic prediction.
Maintain and check the Eidos marketplace when plugins must work in both Claude Code and Codex. Use when adding, refactoring, auditing, or debugging marketplace plugins, dual-host packaging, .claude-plugin and .codex-plugin manifests, root marketplace entries, source/store/cache drift, install proof, or host-neutral plugin payloads.
Challenge whether a Zoltar prediction, product idea, plugin, workflow, category framing, or architecture is overfit to existing market patterns. Use when Daniel asks for a Challenger Matrix, anti-consensus review, category redefinition, frontier user needs, non-consensus futures, Doubter voice, or whether an answer is too derivative, market-shaped, competitor-shaped, or copied from current agent/product patterns.
| name | use-kai-cli |
| description | Use when the user mentions Kai, @kai, kai CLI, founder ops, company-building workflows, Eidos internal operations, platform provisioning guardrails, Slack operations through Kai, deploy routing, idea capture, or Kai feedback. |
Kai is the internal Eidos AGI founder-ops multitool. It is CLI-first and
progressive-reveal: Codex should run the local kai command before inventing
company process in chat.
Run the smallest live orientation command:
kai doctor
If the user asks for a specific Kai domain, inspect that domain next:
kai --help
kai ops --help
kai slack --help
kai deploy --help
kai ideas --help
kai feedback --help
Kai is a dispatcher, not a place to reimplement every specialist. Use Kai to find the right deterministic path, then follow the owning CLI or procedure.
Active domains:
kai doctor: pre-flight for local tools.kai ops: founder-ops guardrails and company procedures.kai slack: Slack read/write/manage/admin operations through the Kai Slack app.kai deploy: Railway deploy routing through railguey.kai ideas: pre-roadmap idea capture.kai feedback: capture misses, drifts, surprises, wins, and noise about Kai itself.kai login: bootstrap a registered platform secret into Eidos Vault.Planned domains may appear in help output but are not necessarily implemented:
plan, vision, decide, forge, session, disk, orient, llm, mcp.
If a planned domain is missing, report that plainly and use the current owning
surface instead, such as Linear, Eidos CLI, Eidos Company Formation, or the
specific platform CLI.
For vague company-building requests, start with:
kai ops guardrails
Then classify the work:
kai ops
guardrails; prefer APIs and Eidos Vault paths; stop before mutations.kai slack --help and the narrowest Kai Slack command.kai deploy --help, then kai deploy <service> or the
delegated railguey command.kai ideas add or kai ideas note.kai feedback miss "<what was missing>".Do not use Kai as permission to mutate real-world state. Ask for explicit approval before:
Kai uses Eidos Vault for platform secrets. Do not print secrets. Prefer path/status checks over secret reads.
Some Kai commands require a cockpit root. If a command reports:
cockpit-root not found
set KAI_COCKPIT_ROOT to the intended cockpit directory for that invocation or
report the missing cockpit root as the blocker.
kai doctor may show optional missing tools. Treat optional missing tools as
capability gaps, not total Kai failure.
When work reveals a stable Kai gap, leave feedback:
kai feedback miss "wanted Kai to do X, but Y was missing"
When Kai successfully routes or completes a workflow, capture a win if useful:
kai feedback win "Kai routed X to Y and produced Z evidence"