Menu
Use Rhea when a task benefits from sovereign model routing, a Socratic debate, persistent Rhea sessions, remote server pairing, or Rhea image generation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | rhea |
| description | Use Rhea when a task benefits from sovereign model routing, a Socratic debate, persistent Rhea sessions, remote server pairing, or Rhea image generation. |
Rhea is a local MCP-powered sovereign model orchestration suite. It can route prompts through configured local or remote provider CLIs, pair with remote Rhea servers, generate images, and run Dreamer/Doubter/Decider debates.
Use Rhea when the user asks to:
Prefer the matching MCP tool when available:
rhea_debate for full multi-round analysisask_rhea for routed model prompts with optional session persistencerhea_quick for a fast sanity checkrhea_status to check local configurationrhea_pair to pair with a remote Rhea serverrhea_draw to generate or edit imagesThis plugin currently launches Rhea from the local checkout at:
~/repos-eidos-agi/rhea
For a public release, replace the local MCP command with the final package-based launcher for @rhea/mcp or the published Rhea command.