npx skills add https://github.com/boshu2/agentops --skill status目的: 单屏概览当前状态。我正在做什么?最近发生了什么?接下来该做什么?
你必须执行此工作流。不要仅仅描述它。
CLI 依赖项: bd, ao, gt — 均为可选。显示可用的内容,跳过不可用的。
/status # 完整仪表板
/status --json # 机器可读的 JSON 输出
为求速度,在并行的 bash 调用中运行以下所有命令:
调用 1 — RPI + Ratchet + 任务状态:
# 当前 ratchet 阶段
if [ -f .agents/ao/chain.jsonl ]; then
tail -1 .agents/ao/chain.jsonl 2>/dev/null
else
echo "NO_CHAIN"
fi
# 通过 CLI 获取 Ratchet 状态
if command -v ao &>/dev/null; then
ao ratchet status --json 2>/dev/null || echo "RATCHET_UNAVAILABLE"
ao task-status --json 2>/dev/null || echo "TASK_STATUS_UNAVAILABLE"
fi
调用 2 — Beads / Epic 状态:
if command -v bd &>/dev/null; then
echo "=== EPIC ==="
bd list --type epic --status open 2>/dev/null | head -5
echo "=== IN_PROGRESS ==="
bd list --status in_progress 2>/dev/null | head -5
echo "=== READY ==="
bd ready 2>/dev/null | head -5
echo "=== TOTAL ==="
bd list 2>/dev/null | wc -l
else
echo "BD_UNAVAILABLE"
fi
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
调用 3 — 知识飞轮:
# 学习成果计数
echo "LEARNINGS=$(ls .agents/learnings/ 2>/dev/null | wc -l | tr -d ' ')"
echo "PATTERNS=$(ls .agents/patterns/ 2>/dev/null | wc -l | tr -d ' ')"
echo "PENDING=$(ls .agents/forge/ 2>/dev/null | wc -l | tr -d ' ')"
# 飞轮健康状态 + 徽章
if command -v ao &>/dev/null; then
ao metrics flywheel status 2>/dev/null || echo "FLYWHEEL_UNAVAILABLE"
ao badge 2>/dev/null || echo "BADGE_UNAVAILABLE"
fi
调用 4 — 近期活动 + Git:
# 近期会话
if [ -d .agents/ao/sessions ]; then
ls -t .agents/ao/sessions/*.md 2>/dev/null | head -3
else
echo "NO_SESSIONS"
fi
# 近期委员会裁决
ls -lt .agents/council/ 2>/dev/null | head -4
# Git 状态
echo "=== GIT ==="
git branch --show-current 2>/dev/null
git log --oneline -3 2>/dev/null
git status --short 2>/dev/null | head -5
调用 5 — 收件箱:
if command -v gt &>/dev/null; then
gt mail inbox 2>/dev/null | head -5
else
echo "GT_UNAVAILABLE"
fi
将收集到的数据组装成以下格式。使用 Unicode 指示符以提高视觉清晰度:
[PASS][WARN][FAIL][3/7] 带进度条 ███░░░░══════════════════════════════════════════════════
工作流仪表板
══════════════════════════════════════════════════
RPI 进度
阶段:<来自 chain.jsonl 的当前阶段:research | plan | implement | validate | idle>
关卡:<最后完成的关卡或 "none">
─────────────────────────────────
research ── plan ── implement ── validate
<用箭头或高亮标记当前位置>
进行中的 EPIC
<epic 标题和 ID,或 "No active epic">
进度:<已完成>/<总计> 个问题 <进度条>
进行中:<列出进行中的问题,最多 3 个>
待处理工作
<来自 bd ready 的前 3 个未阻塞问题>
<或 "No ready issues — create work with /plan">
近期验证
<最后 3 个带裁决的委员会报告>
<格式:date verdict target>
<或 "No recent validations">
知识飞轮
学习成果:<数量> 模式:<数量> 待处理:<数量>
健康状态:<飞轮状态或 "ao not installed">
徽章:<ao badge 输出,如果不可用则省略>
任务成熟度
<ao task-status 摘要:带有 CASS 成熟度级别的活动任务,如果不可用则省略>
近期会话
<最后 3 个带日期的会话摘要>
<或 "No session history">
GIT 状态
分支:<当前分支>
最近提交:<最后 3 次提交,单行显示>
变更:<未提交的文件数或 "clean">
收件箱
<消息数量或 "No messages" 或 "gt not installed">
──────────────────────────────────────────────────
建议的下一步操作
<基于状态的建议 — 参见步骤 3>
──────────────────────────────────────────────────
快捷命令
/research 深度代码库探索
/plan 将 epic 分解为问题
/pre-mortem 编码前验证计划
/implement 执行单个问题
/crank 自主执行 epic
/vibe 验证代码质量
/post-mortem 提取学习成果,关闭循环
══════════════════════════════════════════════════
从上到下评估状态。使用第一个匹配的条件:
| 优先级 | 条件 | 建议 |
|---|---|---|
| 1 | 不存在 ratchet 链 | "使用 /quickstart 或 /research 开始一个工作流" |
| 2 | 研究完成,无计划 | "运行 /plan 将研究分解为可操作的问题" |
| 3 | 计划完成,无预检 | "运行 /pre-mortem 在编码前验证计划" |
| 4 | 有进行中的问题 | "继续工作:/implement <issue-id> 或使用 /crank 进行自主执行" |
| 5 | 有待处理的问题可用 | "处理下一个问题:/implement <first-ready-id>" |
| 6 | 有未提交的更改 | "审查变更:/vibe recent" |
| 7 | 实现完成,未进行 vibe | "运行 /vibe 进行最终代码验证" |
| 8 | 近期有 WARN/FAIL 裁决 | "处理 <report-path> 中的发现,然后重新运行 /vibe" |
| 10 | Vibe 通过,无事后分析 | "运行 /post-mortem 提取学习成果并完成循环" |
| 11 | 有待处理的知识项 | "提升学习成果:ao pool list --status pending --json,然后 ao pool stage <id> 和 ao pool promote <id>" |
| 12 | 状态干净,无待处理项 | "一切就绪。使用 /research 或 /plan 寻找新工作" |
如果用户传递了 --json,则将所有仪表板数据输出为结构化 JSON,而不是可视化仪表板:
{
"rpi": {
"phase": "implement",
"last_gate": "plan",
"chain_entries": 3
},
"epic": {
"id": "ag-042",
"title": "Epic title",
"progress": { "completed": 3, "total": 7, "in_progress": ["ag-042.2"] }
},
"ready_issues": ["ag-042.4", "ag-042.5"],
"validations": [
{ "date": "2026-02-09", "verdict": "PASS", "target": "src/auth/" }
],
"flywheel": {
"learnings": 12,
"patterns": 5,
"pending": 2,
"health": "healthy"
},
"sessions": [
{ "date": "2026-02-09", "file": "session-abc.md" }
],
"git": {
"branch": "main",
"uncommitted_count": 3,
"recent_commits": ["abc1234 fix: thing", "def5678 feat: other"]
},
"inbox": { "count": 0 },
"suggestion": {
"priority": 5,
"message": "Continue working: /implement ag-042.2"
}
}
使用单个代码块渲染此内容。当 --json 激活时,不显示可视化仪表板。
用户说: /status
发生的情况:
/implement ag-042.2"结果: 完整的单屏仪表板显示 epic 执行进度,并带有可操作的下一步。
用户说: /status
发生的情况:
/research 或 /plan 寻找新工作"结果: 仪表板确认状态干净,引导用户到工作流入口点。
| 问题 | 原因 | 解决方案 |
|---|---|---|
| 显示 "BD_UNAVAILABLE" 或 "AO_UNAVAILABLE" | CLI 工具未安装或不在 PATH 中 | 安装缺失的工具:brew install bd 或 brew install ao。技能会优雅降级,仅显示可用状态。 |
| Ratchet 阶段显示陈旧数据 | 旧的 chain.jsonl 未清理 | 检查 .agents/ao/chain.jsonl 的时间戳。如果陈旧,删除它或运行 /post-mortem 以完成循环并重置状态。 |
| 建议的操作与意图不符 | 基于状态的规则未捕获边缘情况 | 查看步骤 3 中的优先级表。可能需要优化条件。使用 --json 检查原始状态并调试规则匹配。 |
| JSON 输出格式错误 | 并行 bash 调用返回了意外格式 | 单独检查每个 bash 调用。确保 jq 解析在实际数据上有效。在返回给用户之前,使用 jq . 验证 JSON 结构。 |
每周安装数
208
仓库
GitHub 星标数
197
首次出现
2026年2月6日
安全审计
安装于
opencode206
codex204
github-copilot203
gemini-cli203
kimi-cli201
amp201
Purpose: Single-screen overview of your current state. What am I working on? What happened recently? What should I do next?
YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.
CLI dependencies: bd, ao, gt — all optional. Shows what's available, skips what isn't.
/status # Full dashboard
/status --json # Machine-readable JSON output
Run ALL of the following in parallel bash calls for speed:
Call 1 — RPI + Ratchet + Task State:
# Current ratchet phase
if [ -f .agents/ao/chain.jsonl ]; then
tail -1 .agents/ao/chain.jsonl 2>/dev/null
else
echo "NO_CHAIN"
fi
# Ratchet status via CLI
if command -v ao &>/dev/null; then
ao ratchet status --json 2>/dev/null || echo "RATCHET_UNAVAILABLE"
ao task-status --json 2>/dev/null || echo "TASK_STATUS_UNAVAILABLE"
fi
Call 2 — Beads / Epic State:
if command -v bd &>/dev/null; then
echo "=== EPIC ==="
bd list --type epic --status open 2>/dev/null | head -5
echo "=== IN_PROGRESS ==="
bd list --status in_progress 2>/dev/null | head -5
echo "=== READY ==="
bd ready 2>/dev/null | head -5
echo "=== TOTAL ==="
bd list 2>/dev/null | wc -l
else
echo "BD_UNAVAILABLE"
fi
Call 3 — Knowledge Flywheel:
# Learnings count
echo "LEARNINGS=$(ls .agents/learnings/ 2>/dev/null | wc -l | tr -d ' ')"
echo "PATTERNS=$(ls .agents/patterns/ 2>/dev/null | wc -l | tr -d ' ')"
echo "PENDING=$(ls .agents/forge/ 2>/dev/null | wc -l | tr -d ' ')"
# Flywheel health + badge
if command -v ao &>/dev/null; then
ao metrics flywheel status 2>/dev/null || echo "FLYWHEEL_UNAVAILABLE"
ao badge 2>/dev/null || echo "BADGE_UNAVAILABLE"
fi
Call 4 — Recent Activity + Git:
# Recent sessions
if [ -d .agents/ao/sessions ]; then
ls -t .agents/ao/sessions/*.md 2>/dev/null | head -3
else
echo "NO_SESSIONS"
fi
# Recent council verdicts
ls -lt .agents/council/ 2>/dev/null | head -4
# Git state
echo "=== GIT ==="
git branch --show-current 2>/dev/null
git log --oneline -3 2>/dev/null
git status --short 2>/dev/null | head -5
Call 5 — Inbox:
if command -v gt &>/dev/null; then
gt mail inbox 2>/dev/null | head -5
else
echo "GT_UNAVAILABLE"
fi
Assemble gathered data into this format. Use Unicode indicators for visual clarity:
Pass/healthy: [PASS]
Warning/partial: [WARN]
Fail/missing: [FAIL]
Progress: [3/7] with bar ███░░░░
══════════════════════════════════════════════════ Workflow Dashboard ══════════════════════════════════════════════════
RPI PROGRESS Phase: <current phase from chain.jsonl: research | plan | implement | validate | idle> Gate: <last completed gate or "none"> ───────────────────────────────── research ── plan ── implement ── validate <mark current position with arrow or highlight>
ACTIVE EPIC <epic title and ID, or "No active epic"> Progress: <completed>/<total> issues <progress bar> In Progress: <list in-progress issues, max 3>
READY TO WORK <top 3 unblocked issues from bd ready> <or "No ready issues — create work with /plan">
RECENT VALIDATIONS <last 3 council reports with verdict> <format: date verdict target> <or "No recent validations">
KNOWLEDGE FLYWHEEL Learnings: <count> Patterns: <count> Pending: <count> Health: <flywheel status or "ao not installed"> Badge: <ao badge output or omit if unavailable>
TASK MATURITY <ao task-status summary: active tasks with CASS maturity levels, or omit if unavailable>
Evaluate state top-to-bottom. Use the FIRST matching condition:
| Priority | Condition | Suggestion |
|---|---|---|
| 1 | No ratchet chain exists | "Start with /quickstart or /research to begin a workflow" |
| 2 | Research done, no plan | "Run /plan to decompose research into actionable issues" |
| 3 | Plan done, no pre-mortem | "Run /pre-mortem to validate the plan before coding" |
| 4 | Issues in-progress | "Continue working: /implement <issue-id> or /crank for autonomous execution" |
If the user passed --json, output all dashboard data as structured JSON instead of the visual dashboard:
{
"rpi": {
"phase": "implement",
"last_gate": "plan",
"chain_entries": 3
},
"epic": {
"id": "ag-042",
"title": "Epic title",
"progress": { "completed": 3, "total": 7, "in_progress": ["ag-042.2"] }
},
"ready_issues": ["ag-042.4", "ag-042.5"],
"validations": [
{ "date": "2026-02-09", "verdict": "PASS", "target": "src/auth/" }
],
"flywheel": {
"learnings": 12,
"patterns": 5,
"pending": 2,
"health": "healthy"
},
"sessions": [
{ "date": "2026-02-09", "file": "session-abc.md" }
],
"git": {
"branch": "main",
"uncommitted_count": 3,
"recent_commits": ["abc1234 fix: thing", "def5678 feat: other"]
},
"inbox": { "count": 0 },
"suggestion": {
"priority": 5,
"message": "Continue working: /implement ag-042.2"
}
}
Render this with a single code block. No visual dashboard when --json is active.
User says: /status
What happens:
Result: Full single-screen dashboard showing mid-epic progress with actionable next step.
User says: /status
What happens:
Result: Dashboard confirms clean slate, points user to workflow entry points.
| Problem | Cause | Solution |
|---|---|---|
| Shows "BD_UNAVAILABLE" or "AO_UNAVAILABLE" | CLI tools not installed or not in PATH | Install missing tools: brew install bd or brew install ao. Skill gracefully degrades by showing available state only. |
| Ratchet phase shows stale data | Old chain.jsonl not cleaned up | Check timestamp of .agents/ao/chain.jsonl. If stale, delete it or run /post-mortem to complete cycle and reset state. |
| Suggested action doesn't match intent | State-aware rules didn't capture edge case | Review priority table in Step 3. May need to refine conditions. Use --json to inspect raw state and debug rule matching. |
| JSON output malformed |
Weekly Installs
208
Repository
GitHub Stars
197
First Seen
Feb 6, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode206
codex204
github-copilot203
gemini-cli203
kimi-cli201
amp201
AI Elements:基于shadcn/ui的AI原生应用组件库,快速构建对话界面
56,200 周安装
竞争对手研究指南:SEO、内容、反向链接与定价分析工具
231 周安装
Azure 工作负载自动升级评估工具 - 支持 Functions、App Service 计划与 SKU 迁移
231 周安装
Kaizen持续改进方法论:软件开发中的渐进式优化与防错设计实践指南
231 周安装
软件UI/UX设计指南:以用户为中心的设计原则、WCAG可访问性与平台规范
231 周安装
Apify 网络爬虫和自动化平台 - 无需编码抓取亚马逊、谷歌、领英等网站数据
231 周安装
llama.cpp 中文指南:纯 C/C++ LLM 推理,CPU/非 NVIDIA 硬件优化部署
231 周安装
RECENT SESSIONS <last 3 session summaries with dates> <or "No session history">
GIT STATE Branch: <current branch> Recent: <last 3 commits, one-line> Changes: <uncommitted file count or "clean">
INBOX <message count or "No messages" or "gt not installed">
────────────────────────────────────────────────── SUGGESTED NEXT ACTION <state-aware suggestion — see Step 3> ──────────────────────────────────────────────────
QUICK COMMANDS /research Deep codebase exploration /plan Decompose epic into issues /pre-mortem Validate plan before coding /implement Execute a single issue /crank Autonomous epic execution /vibe Validate code quality /post-mortem Extract learnings, close cycle ══════════════════════════════════════════════════
| 5 | Ready issues available | "Pick up next issue: /implement <first-ready-id>" |
| 6 | Uncommitted changes | "Review changes: /vibe recent" |
| 7 | Implementation done, no vibe | "Run /vibe for final code validation" |
| 8 | Recent WARN/FAIL verdict | "Address findings in <report-path>, then re-run /vibe" |
| 10 | Vibe passed, no post-mortem | "Run /post-mortem to extract learnings and complete the cycle" |
| 11 | Pending knowledge items | "Promote learnings: ao pool list --status pending --json, then ao pool stage <id> and ao pool promote <id>" |
| 12 | Clean state, nothing pending | "All clear. Start with /research or /plan to find new work" |
| Parallel bash calls returned unexpected format |
Check each bash call individually. Ensure jq parsing works on actual data. Validate JSON structure with jq . before returning to user. |