メニュー
Use when defining, enforcing, or reviewing agent operating standards after code, repo, plugin, workflow, or agent changes need proof gates, verification loops, AGENTS.md contracts, CI checks, or a durable definition of done.
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 | canon |
| description | Use when defining, enforcing, or reviewing agent operating standards after code, repo, plugin, workflow, or agent changes need proof gates, verification loops, AGENTS.md contracts, CI checks, or a durable definition of done. |
Canon is the canonical standards layer for agentic software work. Use it after substantive code, repo, plugin, workflow, or agent changes when the user wants standards enforced across Codex, Claude Code, CI, local scripts, or source-owned plugin surfaces.
Instruction files shape behavior. Executable checks enforce behavior. Prefer the repo's deterministic verification commands over model self-assessment.
AGENTS.md, README.md, and verification docs before
changing behavior.have, want, and don't want when the task is broad or
enforcement-related.Use this order:
AGENTS.md and skills for operating behaviorCanon does not create agents; use Felix for scaffolding and agent ecosystem design. Canon does not own evidence loops; use Eidos for tracked execution. Canon does not own target scoreboards; use Converge for target/probe grids, drift monitors, and repair loops.
canon doctor
canon check
canon verify
Treat command output as evidence to reconcile, not as a verdict to parrot.