القائمة
Use when the user asks to check, monitor, clean up, or keep a Mac healthy with apple-a-day or aad.
التثبيت باستخدام 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 | use-apple-a-day |
| description | Use when the user asks to check, monitor, clean up, or keep a Mac healthy with apple-a-day or aad. |
apple-a-day is a read-only-by-default Mac health CLI. Use it to inspect health, vitals, cleanup candidates, and launchd monitor state before doing expensive or long-running local work.
aad checkup --json --min-severity warning --fields severity,summary,fix
aad monitor --once --json
aad vitals --json --minutes 60
aad status
If aad is not on PATH, install or run it with uvx:
uvx --from apple-a-day aad checkup --json --min-severity warning --fields severity,summary,fix
fix as a recommendation unless the user explicitly asks to
execute it.aad install or aad uninstall.For a quick machine health answer:
aad checkup --json --min-severity warning --fields severity,summary,fix
For preflight before heavy local work:
aad checkup --json -c cpu_load -c thermal -c memory_pressure --min-severity warning
For an always-on Mac:
aad install
aad status
aad vitals --json --minutes 60
For cleanup planning:
aad checkup --json -c cleanup --min-severity info
Return the concrete findings, the evidence command used, and which actions remain human-approved or destructive.