القائمة
Use when the user asks Codex to discover, choose, install, add, bootstrap, or use Eidos plugins from the Eidos AGI catalog.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
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.
استنادا إلى تصنيف SOC المهني
| name | eidos-plugin-store |
| description | Use when the user asks Codex to discover, choose, install, add, bootstrap, or use Eidos plugins from the Eidos AGI catalog. |
Use this skill when Codex needs to find or add Eidos plugins.
https://eidosagi.com/pluginshttps://eidosagi.com/.well-known/eidos/plugin-store.jsonhttps://github.com/eidos-agi/eidos-plugin-storeThe public marketplace identity is Eidos AGI. Do not create or recommend a
second user-visible Eidos store unless the user explicitly asks for a local test
marketplace.
Prefer the machine catalog. If it is unavailable, read the human catalog. If network access is unavailable, use the fallback list below and say it may be stale.
For users, keep the language plain:
Install the Eidos AGI marketplace first. Then use the catalog plugin to find and add the other Eidos plugins you need.
When Codex install support is uncertain, use this shape:
Codex direct plugin install may not be live in this environment yet. I will use the Eidos AGI catalog and the source repo instructions, then tell you exactly what is installed versus only recommended.