Explicit personal-status surface for /dashboard or a direct request for the whole personal overview. Do not use it to find or resume one specific prior handoff, project, or work thread; that is semantic organizational recall through Runtime/QMD.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Use this bounded status card only when the user explicitly asks for Dashboard
or the whole personal overview. A request to return to one earlier piece of
work must use attached EGREGORE_ORG_CONTEXT_V1 evidence or exactly one Search
workflow query when that evidence is absent. Never use Dashboard as discovery
fallback.
Render the personal view immediately. The renderer's stdout IS the product card: it is fully visible the moment rendering finishes, and it must appear exactly once in the conversation. Never copy, regenerate, summarize, or repeat the card — or any of its rows — in your reply; add nothing beyond an answer to something the user separately asked.
Map the requested range to P1D, P7D, P30D, or P365D as {time-range},
then fetch and render exactly one authorized Runtime snapshot:
bash bin/dashboard-data.sh '{time-range}' 2>/dev/null \
| bash bin/node-run.sh bin/codex-skill-render.mjs dashboard-card -
Do not sync repositories, query memory again, or call implementation infrastructure directly. The snapshot owns actor resolution, authorization, bounds, canonical lifecycle state, and presentation data.
Connected enrichment is separate and explicit. Set
EGREGORE_STATUS_CONNECTED_ENRICH=1 only when the user requests projected
Connected status. It is capability/permission gated and cannot replace
canonical handoffs, questions, quests, todos, sessions, or lifecycle metadata.
Never print raw JSON or narrate routine commands. Preserve the shared
72-column card, omit graph/setup messaging in Local mode, end with What's next?, and act on the reply in the next turn.
Explicit personal-status surface for /dashboard or a direct request for the whole personal overview. Do not use it to find or resume one specific prior handoff, project, or work thread; that is semantic organizational recall through Runtime/QMD.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Explicit Activity card only. Use when the user names /activity or directly asks to show, open, or render the Activity dashboard/card. Never use it to answer or synthesize what the team is focused on, busy with, prioritizing, or doing; analytical organizational questions use Search/Runtime QMD.
中文简介正在准备中。当前显示原文说明。
Draft, preview, and explicitly send an Egregore group announcement. Use for /announce, telling the team something, or notifying everyone—not a direct message or structured handoff.
中文简介正在准备中。当前显示原文说明。
Capture an effective prompting or steering technique as a reusable canonical pattern. Use when a prompt chain worked especially well; use /reflect for insight about the work and /note for a private thought.
中文简介正在准备中。当前显示原文说明。
Create a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes.
中文简介正在准备中。当前显示原文说明。
Run diagnostics on an Egregore environment and render a health report, repairing safe local Runtime problems when possible. Use for /checkup, a health check, or when something is broken and the root cause is unclear.
中文简介正在准备中。当前显示原文说明。
Stage changes and create a commit with a properly formatted message. Use for /commit, or saving work locally — not sharing it (/push) or opening a pull request (/pr).
中文简介正在准备中。当前显示原文说明。