status
starsforks
How to install status?
dsifry/metaswarm/status
$npx -y skills add dsifry/metaswarm --skill statusDiagnostic status report — shows metaswarm installation state, project setup, and potential issues
SKILL.md
| 1 | # Status Skill |
| 2 | |
| 3 | Generate a diagnostic report of the metaswarm installation, project configuration, and potential issues across Claude Code, Codex, and Gemini. Useful for troubleshooting and verifying setup or migration. |
| 4 | |
| 5 | --- |
| 6 | |
| 7 | ## Checks |
| 8 | |
| 9 | Run each check below and present results in a single formatted report. Detect the active platform first: |
| 10 | |
| 11 | - Codex: `PLUGIN_ROOT` or `CODEX_HOME` is present, `.codex-plugin/plugin.json` is the active manifest, or the user invoked `$status` |
| 12 | - Claude Code: `CLAUDE_PLUGIN_ROOT` is present, `.claude-plugin/plugin.json` is the active manifest, or the user invoked `$status` |
| 13 | - Gemini: `extensionPath` is present, `gemini-extension.json` is the active manifest, or the user invoked `$status` |
| 14 | |
| 15 | ### 1. Plugin Version |
| 16 | |
| 17 | - Codex: read `.codex-plugin/plugin.json` from the plugin root and report `version` |
| 18 | - Claude Code: read `.claude-plugin/plugin.json` from the plugin root and report `version` |
| 19 | - Gemini: read `gemini-extension.json` from the plugin root and report `version` |
| 20 | - Fallback: read `package.json` at plugin root for `version` |
| 21 | - If neither found: `Plugin version: UNKNOWN` |
| 22 | |
| 23 | ### 2. Project Setup State |
| 24 | |
| 25 | - Check if `.metaswarm/project-profile.json` exists in the working directory |
| 26 | - If present, report key fields: `distribution`, `metaswarm_version`, `language`, `framework`, `test_runner` |
| 27 | - If absent, report the platform-specific setup command: |
| 28 | - Codex: `Project setup: NOT CONFIGURED -- run $setup` |
| 29 | - Claude Code: `Project setup: NOT CONFIGURED -- run $setup` |
| 30 | - Gemini: `Project setup: NOT CONFIGURED -- run $setup` |
| 31 | |
| 32 | ### 3. Platform Install State |
| 33 | |
| 34 | **Codex** |
| 35 | - Check `.codex-plugin/plugin.json` exists in the plugin root |
| 36 | - Check `~/.codex/config.toml` for an enabled `metaswarm@...` plugin entry when accessible |
| 37 | - Scan `~/.codex/plugins/cache/` for `.codex-plugin/plugin.json` with `"name": "metaswarm"` |
| 38 | - If installed from a local marketplace, report cache version as `local` |
| 39 | |
| 40 | **Claude Code** |
| 41 | - Check `.claude-plugin/plugin.json` exists in the plugin root |
| 42 | - Scan `~/.claude/plugins/cache/` for `.claude-plugin/plugin.json` with `"name": "metaswarm"` |
| 43 | - Report marketplace/plugin cache status when accessible |
| 44 | |
| 45 | **Gemini** |
| 46 | - Check `gemini-extension.json` exists in the plugin root |
| 47 | - Report extension status when discoverable from the local Gemini config |
| 48 | |
| 49 | ### 4. Claude Command Shims |
| 50 | |
| 51 | When checking a Claude project, check these files in `.claude/commands/`: |
| 52 | |
| 53 | | Shim | Expected | |
| 54 | |---|---| |
| 55 | | `start-task.md` | Routes to `/metaswarm:start-task` | |
| 56 | | `prime.md` | Routes to `/metaswarm:prime` | |
| 57 | | `review-design.md` | Routes to `/metaswarm:review-design` | |
| 58 | | `self-reflect.md` | Routes to `/metaswarm:self-reflect` | |
| 59 | | `pr-shepherd.md` | Routes to `/metaswarm:pr-shepherd` | |
| 60 | | `brainstorm.md` | Routes to `/metaswarm:brainstorm` | |
| 61 | |
| 62 | For each: report Present/Missing. If the file exists but does not contain "metaswarm" routing, flag as `present (non-metaswarm content)`. |
| 63 | |
| 64 | When checking a Codex project, report `not applicable (Codex uses $skill-name invocation)` instead of treating missing `.claude/commands/` files as errors. |
| 65 | |
| 66 | ### 5. Legacy Embedded Plugin |
| 67 | |
| 68 | - Check for `.claude/plugins/metaswarm/.claude-plugin/plugin.json` |
| 69 | - If found: `DETECTED -- run $migrate` |
| 70 | - If found alongside the marketplace plugin, flag prominently as a conflict |
| 71 | |
| 72 | ### 6. BEADS Plugin |
| 73 | |
| 74 | - Scan `~/.claude/plugins/cache/` and `~/.codex/plugins/cache/` for a directory containing `.claude-plugin/plugin.json` or `.codex-plugin/plugin.json` with `"name": "beads"` |
| 75 | - If found: `installed (standalone)` -- metaswarm defers priming to BEADS |
| 76 | - If not found: `not separately installed` |
| 77 | |
| 78 | ### 7. `bd` CLI |
| 79 | |
| 80 | ```bash |
| 81 | command -v bd && bd --version 2>/dev/null |
| 82 | ``` |
| 83 | |
| 84 | - If found: report path and version |
| 85 | - If not found: `not installed -- knowledge priming and self-reflect require bd. Core orchestration works without it.` |
| 86 | |
| 87 | ### 8. `gtg` CLI |
| 88 | |
| 89 | ```bash |
| 90 | command -v gtg && gtg --help >/dev/null 2>&1 |
| 91 | ``` |
| 92 | |
| 93 | - If found: report path |
| 94 | - If not found: `not installed -- pr-shepherd will fall back to manual gh checks.` |
| 95 | |
| 96 | ### 9. External Tools |
| 97 | |
| 98 | - Read `.metaswarm/external-tools.yaml` -- if absent: `not configured (optional)` |
| 99 | - If present, check each enabled adapter's availability: |
| 100 | |
| 101 | ```bash |
| 102 | command -v codex # Codex CLI |
| 103 | command -v gemini # Gemini CLI |
| 104 | ``` |
| 105 | |
| 106 | Report per-tool: enabled (yes/no), status (available/not installed). |
| 107 | |
| 108 | ### 10. Coverage Thresholds |
| 109 | |
| 110 | - Read `.coverage-thresholds.json` -- if absent: `not configured` |
| 111 | - If present, report threshold values (lines, branches, functions, statements) and enforcement command |
| 112 | |
| 113 | ### 11. Node.js |
| 114 | |
| 115 | ```bash |
| 116 | node --version 2>/dev/null |
| 117 | ``` |
| 118 | |
| 119 | - If found: report version |
| 120 | - If not found: `not installed -- scripts/beads-*.ts require Node.js. Core orchestration works without it.` |
| 121 | |
| 122 | --- |
| 123 | |
| 124 | ## Output Format |
| 125 | |
| 126 | ```markdown |
| 127 | ## Metaswarm Status Report |
| 128 | |
| 129 | | Component | Status | |
| 130 | |---|---| |
| 131 | | Active platform | Codex | |
| 132 | | Plugin version | 0.11.0 | |
| 133 | | Projec |
People who liked this also viewed
6 picksType
- lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026
- lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026
- lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。 当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026
- lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026
- lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026
- lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026
