Agent skill

Comet Open

A skill your agent uses when Comet 需要创建新的 OpenSpec change，或 active change 缺少 proposal/design/tasks/.comet.yaml 初始化产物。

MITAuto-check passedProduct & Project Management

Install Comet Open

skills CLI

$ npx skills add rpamis/comet --skill comet-open -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install rpamis/comet comet-open --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/rpamis/comet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/eval/local/skills/benchmarks/040-beta/comet-open .claude/skills/comet-open && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "comet-open" agent skill from https://github.com/rpamis/comet/tree/master/eval/local/skills/benchmarks/040-beta/comet-open into .claude/skills/comet-open/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "comet-open", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/rpamis/comet/tree/master/eval/local/skills/benchmarks/040-beta/comet-open

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add rpamis/comet --skill comet-open -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install rpamis/comet comet-open --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rpamis/comet.git skills-src && mkdir -p .agents/skills && cp -r skills-src/eval/local/skills/benchmarks/040-beta/comet-open .agents/skills/comet-open && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "comet-open" agent skill from https://github.com/rpamis/comet/tree/master/eval/local/skills/benchmarks/040-beta/comet-open into .agents/skills/comet-open/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "comet-open", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add rpamis/comet --skill comet-open -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install rpamis/comet comet-open --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rpamis/comet.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/eval/local/skills/benchmarks/040-beta/comet-open .cursor/skills/comet-open && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "comet-open" agent skill from https://github.com/rpamis/comet/tree/master/eval/local/skills/benchmarks/040-beta/comet-open into .cursor/skills/comet-open/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "comet-open", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/rpamis/comet.git --path eval/local/skills/benchmarks/040-beta/comet-open

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add rpamis/comet --skill comet-open -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install rpamis/comet comet-open --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rpamis/comet.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/eval/local/skills/benchmarks/040-beta/comet-open .gemini/skills/comet-open && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "comet-open" agent skill from https://github.com/rpamis/comet/tree/master/eval/local/skills/benchmarks/040-beta/comet-open into .gemini/skills/comet-open/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "comet-open", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install rpamis/comet comet-open

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add rpamis/comet --skill comet-open -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/rpamis/comet.git skills-src && mkdir -p .github/skills && cp -r skills-src/eval/local/skills/benchmarks/040-beta/comet-open .github/skills/comet-open && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "comet-open" agent skill from https://github.com/rpamis/comet/tree/master/eval/local/skills/benchmarks/040-beta/comet-open into .github/skills/comet-open/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "comet-open", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add rpamis/comet --skill comet-open -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install rpamis/comet comet-open --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rpamis/comet.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/eval/local/skills/benchmarks/040-beta/comet-open .opencode/skills/comet-open && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "comet-open" agent skill from https://github.com/rpamis/comet/tree/master/eval/local/skills/benchmarks/040-beta/comet-open into .opencode/skills/comet-open/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "comet-open", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: comet-open
GitHub stars: 3.2k
Token cost: ~1.5k tokens
SKILL.md length: 406 words
Files: 1
Skills in repo: 52
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when Comet 需要创建新的 OpenSpec change，或 active change 缺少 proposal/design/tasks/.comet.yaml 初始化产物。

Works in 6 steps: 输出语言约束 → 探索想法与需求澄清 → 创建 Change 结构 + 初始化状态 → …
Comet 需要创建新的 OpenSpec change，或 active change 缺少 proposal/design/tasks/.comet.yaml 初始化产物
SKILL.md covers 前置条件, 步骤, 退出条件 and 自动衔接下一阶段
Calls node

What it does

Comet Open is an agent skill from rpamis/comet. Use when Comet 需要创建新的 OpenSpec change，或 active change 缺少 proposal/design/tasks/.comet.yaml 初始化产物。

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing. The repository describes itself as: Comet: agent skill harness for turning ideas into evaluated workflows. The licence is MIT.

When your agent uses it

Comet 需要创建新的 OpenSpec change，或 active change 缺少 proposal/design/tasks/.comet.yaml 初始化产物
Tasks that involve PRD writing

Example prompts

“/comet-open”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

输出语言约束
探索想法与需求澄清
创建 Change 结构 + 初始化状态
入口状态验证
内容完整性检查
用户审视确认（阻塞点）

What it can do on your machine

Read from SKILL.md and the folder at commit 0fd42a0. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Comet Open loads about 1.5k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 406 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~27
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rpamis/comet at commit 0fd42a0, republished under its MIT licence (© rpamis). 406 words, ~1,496 tokens.

Download SKILL.mdSave it as .claude/skills/comet-open/SKILL.md (or your agent's skills folder).

name: comet-open
description: Use when Comet 需要创建新的 OpenSpec change，或 active change 缺少 proposal/design/tasks/.comet.yaml 初始化产物。

Comet 阶段 1：开启（Open）

前置条件

无活跃 change，或用户希望创建新 change

步骤

0. 输出语言约束

传递给 OpenSpec 的所有提问和产物要求都必须包含输出语言约束：使用触发本次工作流的用户请求语言。恢复已有 change 且产物已有明确主语言时，除非用户明确要求切换，否则保持该语言。

1. 探索想法与需求澄清

立即执行： 使用 Skill 工具加载 openspec-explore 技能。禁止跳过此步骤。

技能加载后，按其指引探索问题空间，但不得把一次问答视为足够澄清。必须围绕下列内容继续提问、对齐并形成澄清摘要：

目标：用户真正要解决的问题和期望结果
非目标：本次明确不做的内容
范围边界：涉及/不涉及的模块、用户、平台或数据
关键未知项：仍不确定的假设、风险或依赖
验收场景草案：至少覆盖核心成功场景和关键边界场景

澄清摘要必须包含：目标、非目标、范围边界、关键未知项、验收场景草案。

1a. PRD 拆分预检（阻塞点）

当用户输入是大型 PRD、路线图、完整产品方案，或澄清摘要显示包含多个独立能力、模块、用户路径或里程碑时，必须在创建 OpenSpec artifacts 前评估是否需要拆分为多个 change。

拆分预检必须基于已澄清的信息，输出候选拆分清单。每个候选拆分项必须包含：

建议 change 名称
目标与范围边界
明确非目标
依赖关系或推荐执行顺序
对应的核心验收场景

满足任一条件时，应推荐拆分：

PRD 包含多个可独立设计、构建、验证、归档的 capability
涉及多个模块或用户路径，且其中一部分可独立交付
存在明显分阶段里程碑
预计会产生多个 delta spec 或超过 3 个大任务
任一部分失败或延期不应阻塞其他部分进入后续阶段

如推荐拆分，必须按 comet/reference/decision-point.md 的协议暂停并等待用户选择。

用户选择必须包含：

「创建多个 OpenSpec changes」— 按候选拆分逐个创建独立 change
「保持为一个 change」— 继续单 change 流程，并在 proposal/design/tasks 中记录不拆分原因
「调整拆分方案后继续」— 用户说明调整方向后，重新输出候选拆分清单并再次确认

每个被接受的拆分项都必须通过 /comet-open 创建独立 change，不得直接调用 /opsx:new。/comet-open 负责同时创建 OpenSpec artifacts 和 .comet.yaml，确保每个 change 都进入 Comet 状态机。

不得在用户完成 PRD 拆分选择前创建 proposal.md、design.md 或 tasks.md。若用户选择创建多个 change，当前 /comet-open 调用只负责完成拆分确认与调度，随后按用户确认的顺序分别进入每个拆分项的 /comet-open。

批量拆分模式下，进入每个拆分项的 /comet-open 时必须明确标注「已确认拆分项」并携带该拆分项的目标、范围、非目标和验收场景。已确认拆分项默认跳过 PRD 拆分预检，除非该拆分项本身仍明显包含多个独立 capability。

批量拆分模式下，单个拆分项完成 open 阶段后不得自动流转到 /comet-design。拆分完毕后必须暂停询问用户开始哪一个 change；用户选择后，只推进该 change 进入 /comet-design，其他 change 保持 active，稍后通过 /comet 恢复。

最小断点恢复规则：不新增专用批量状态文件。若批量拆分过程中断，恢复时先检查已创建的 active changes；已存在且包含 .comet.yaml 的拆分项不得重复创建，未创建的拆分项按用户已确认的拆分清单继续通过 /comet-open 创建。若对话中已确认的拆分清单不可恢复，必须重新向用户确认拆分清单后再继续。

1b. 需求澄清完成确认（阻塞点）

创建 OpenSpec artifacts 前，必须按 comet/reference/decision-point.md 的协议暂停并等待用户确认需求澄清完成。

暂停时必须展示澄清摘要：目标、非目标、范围边界、关键未知项、验收场景草案。

不得在用户确认需求澄清完成前创建 proposal.md、design.md 或 tasks.md，也不得使用 Skill 工具加载 openspec-propose 技能一次性生成全部 artifacts。

1c. Change 名称确认（阻塞点）

创建 change 目录（openspec new change）前，必须按 comet/reference/decision-point.md 的协议暂停，让用户决定 change 名称。不得自动生成或静默推断 change 名称。

OpenSpec change 名称必须是 kebab-case 英文（小写字母、数字、连字符；如 refine-requirements-doc）。中文或其他不合规名称无效。

暂停时必须展示：

基于已确认澄清摘要派生的 2-3 个推荐 kebab-case 英文名，每个附一行说明其隐含范围
一个让用户 自行输入名称 的明确选项
提示：若用户输入中文（或任何非 kebab-case 文本），会被转换为合规的 kebab-case 英文名，转换结果必须回显给用户确认后才能使用

决策选项必须包含：

选择某个推荐名称
「自行输入名称」——接收用户输入；若已是合规 kebab-case 英文则直接使用；若为中文或其他不合规形式，则转换为合规 kebab-case 英文并回显转换后的名称，确认后再继续

不得在用户确认最终 change 名称前运行 openspec new change 或创建 .comet.yaml。若选定/转换后的名称与已有 change 冲突，必须报告冲突并请用户另选名称。

Show full SKILL.md (228 more words)Show less

2. 创建 Change 结构 + 初始化状态

立即执行： 使用 Skill 工具加载 openspec-new-change 技能。禁止跳过此步骤。

完整 /comet 流程默认不得使用 Skill 工具加载 openspec-propose 技能；只有用户明确要求一次性生成提案和 artifacts 时才允许加载。

技能加载后，按其指引创建 change 骨架，但当 Step 1b 的已确认澄清摘要已存在于对话上下文时，覆盖其"STOP and wait for user direction"行为。

如果用户已确认澄清摘要（Step 1b），直接使用该摘要填充产物内容。如果不存在澄清摘要（边缘情况），回退到技能的默认行为，询问用户。

change 骨架创建后，按以下标准产物循环逐个生成 proposal、design、tasks：

标准产物循环（对每个 artifact-id：proposal → design → tasks）：

刷新状态：openspec status --change "<name>" --json

获取产物指令：

bash

openspec instructions proposal --change "<name>" --json
openspec instructions design --change "<name>" --json
openspec instructions tasks --change "<name>" --json

对返回的 JSON 指令载荷，必须：
- 读取 dependencies 中列出的每个已完成依赖产物
- 以 template 作为产物结构
- 遵循 instruction 的指引
- 将 context 和 rules 作为约束条件应用，不得复制到 artifact 内容中
- 写入 resolvedOutputPath
- 验证输出文件存在且非空
每创建一个 artifact 后，重新运行 openspec status --change "<name>" --json 确认状态，然后继续下一个 artifact

失败处理：如果 openspec instructions 失败、返回无效 JSON、报告未满足的 dependencies、或未提供可用的 resolvedOutputPath，必须立即停止 artifact 创建并报告 OpenSpec 错误。不得回退为硬编码文档结构，因为那样会绕过项目规则。

命名与范围守卫：change name 必须使用 Step 1c 中用户确认的 kebab-case 英文名，不得自动生成、推断或使用非 kebab-case（如中文）名称。变更范围必须与用户描述一致，不得自行扩大或缩小。

确认以下产物已创建：

openspec/changes/<name>/
├── .openspec.yaml
├── .comet.yaml
├── proposal.md       # Why + What：问题、目标、范围
├── design.md         # How（高层框架）：架构决策、方案选型（深度技术设计在 design 阶段 Design Doc 细化）
└── tasks.md          # 任务清单（勾选框）

创建 .comet.yaml 状态文件：

先按 comet/reference/scripts.md 定位脚本（定位 comet-env.mjs），然后初始化状态：

bash

node "$COMET_STATE" init <name> full

3. 入口状态验证

验证状态机已正确初始化：

bash

node "$COMET_STATE" check <name> open

验证通过后继续 Step 4。验证失败时脚本会输出具体失败原因。

幂等性：open 阶段所有操作可安全重复执行。如 .comet.yaml 已处于 phase: open 且三个产物文件均已存在，跳过已完成步骤，从第一个缺失步骤继续。

4. 内容完整性检查

确认三个文档内容完整：

proposal.md：问题背景、目标、范围、非目标
design.md：高层架构决策、方案选型、数据流
tasks.md：任务列表，每个任务有明确描述

文件存在性验证：逐个确认三个文件路径存在且非空。任一文件缺失或为空时，不得进入 Step 5 或执行阶段守卫，必须回到创建步骤补充。

5. 用户审视确认（阻塞点）

三个文档创建完成且内容完整性检查通过后，必须按 comet/reference/decision-point.md 的协议暂停并等待用户确认。不得在用户确认前执行阶段守卫或自动流转。

用户确认问题必须以单选题形式呈现，包含以下摘要和选项：

摘要内容：

proposal.md：问题背景、目标、范围
design.md：高层架构决策、方案选型
tasks.md：任务数量和关键任务描述

选项：

「确认，继续下一阶段」— 产物符合预期，执行阶段守卫流转
「需要调整」— 附带调整说明，修改后重新请求确认

用户选择「确认」后继续执行退出条件。用户选择「需要调整」时，按其说明修改对应文件，然后重新请求确认。

退出条件

proposal.md、design.md、tasks.md 均已创建且内容完整
用户已确认 proposal、design、tasks 内容符合预期
阶段守卫：运行 node "$COMET_GUARD" <change-name> open --apply，全部 PASS 后由守卫推进到下一阶段（此步骤更新 phase 字段，与 auto_transition 无关）

退出前必须使用 --apply，否则 .comet.yaml 仍停留在 phase: open，下一阶段入口检查会失败。

bash

node "$COMET_GUARD" <change-name> open --apply

完整流程会自动更新为 phase: design；hotfix/tweak 预设会自动更新为 phase: build。

自动衔接下一阶段

按 comet/reference/auto-transition.md 执行。关键命令：

bash

node "$COMET_STATE" next <change-name>

NEXT: auto → 调用 SKILL 指向的 skill 进入下一阶段
NEXT: manual → 不要调用下一 skill，按 HINT 提示用户手动运行 /<SKILL>
NEXT: done → 流程已完成，无需继续

hotfix/tweak 预设由对应预设 Skill 控制后续流转（phase 直接进入 build），其 next 会返回对应预设 Skill。

Files

Just SKILL.md in eval/local/skills/benchmarks/040-beta/comet-open of rpamis/comet.

Open the folder on GitHubat commit 0fd42a0

Compare with similar skills

Comet Open next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Comet Open compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Comet Open this skillrpamis/comet	3.2k	—	~1.5k	Automated safety check: Pass	MIT	today
CCPM Project Managementautomazeio/ccpm	8.4k	—	~1.1k	Automated safety check: Pass	MIT	6 mo ago
Ralph Tui Create Beadssubsy/ralph-tui	2.5k	1 repos	~2.6k	Automated safety check: Pass	MIT	1 mo ago
Trellis Brainstormanjiemo/SunnyBeach	178	7 repos	~4k	Automated safety check: Pass	Apache-2.0	28 days ago
Ralph Tui Create Beads Rustsubsy/ralph-tui	2.5k	1 repos	~2.8k	Automated safety check: Pass	MIT	1 mo ago
Ralph Tui Create JSONsubsy/ralph-tui	2.5k	1 repos	~2.6k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
Product & Project ManagementAuto-check passed
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
2.5k GitHub starsUsed in 1 repo~2.6k tokens
Product & Project ManagementAuto-check passed
Trellis Brainstorm
anjiemo/SunnyBeach
Guides collaborative requirements discovery before implementation.
178 GitHub starsUsed in 7 repos~4k tokens
Product & Project ManagementAuto-check passed
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
2.5k GitHub starsUsed in 1 repo~2.8k tokens
Product & Project ManagementAuto-check passed
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
2.5k GitHub starsUsed in 1 repo~2.6k tokens
Product & Project ManagementAuto-check passed
Prd Generator
jamesrochabrun/skills
Generate comprehensive Product Requirements Documents (PRDs) for product managers.
216 GitHub starsUsed in 2 repos~3.8k tokens
Product & Project ManagementAuto-check passed

Questions about Comet Open

What does Comet Open do?

A skill your agent uses when Comet 需要创建新的 OpenSpec change，或 active change 缺少 proposal/design/tasks/.comet.yaml 初始化产物。. Comet Open is an agent skill from rpamis/comet.

When should I use Comet Open?

Comet Open fits situations like: comet 需要创建新的 OpenSpec change，或 active change 缺少 proposal/design/tasks/.comet.yaml 初始化产物; tasks that involve PRD writing.

How do I install Comet Open in Claude Code?

Run `npx skills add rpamis/comet --skill comet-open -a claude-code`. Or copy the skill folder (eval/local/skills/benchmarks/040-beta/comet-open in rpamis/comet) into .claude/skills/comet-open in your project. Claude Code loads it when a task matches its description.

How do I install Comet Open in Codex?

Run `npx skills add rpamis/comet --skill comet-open -a codex`. Or copy the skill folder (eval/local/skills/benchmarks/040-beta/comet-open in rpamis/comet) into .agents/skills/comet-open in your project. Codex loads it when a task matches its description.

Can I use Comet Open in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rpamis/comet --skill comet-open -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/comet-open, .gemini/skills/comet-open, .github/skills/comet-open and .opencode/skills/comet-open in your project.

What does Comet Open need to run?

Going by SKILL.md and its folder, Comet Open needs the command-line tools its instructions call (node).

Does Comet Open access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Comet Open safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Comet Open use?

Comet Open is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Comet Open use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Comet Open?

Skills that share tags, products or a category with Comet Open: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Comet Open?

rpamis (a GitHub organization) maintains it in rpamis/comet, which has 3,166 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 9, 2026.

Source: rpamis/comet on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Comet Open

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Comet 阶段 1：开启（Open）

前置条件

步骤

0. 输出语言约束

1. 探索想法与需求澄清

1a. PRD 拆分预检（阻塞点）

1b. 需求澄清完成确认（阻塞点）

1c. Change 名称确认（阻塞点）

2. 创建 Change 结构 + 初始化状态

3. 入口状态验证

4. 内容完整性检查

5. 用户审视确认（阻塞点）

退出条件

自动衔接下一阶段

Files

Compare with similar skills

Similar skills

More from rpamis/comet

Related

Questions about Comet Open