Comet
Comet workflow entry. Use when the user invokes /comet or asks to use Comet without choosing Native or Classic; load Native or Classic from project configuration.
Install
npx skills add rpamis/comet --skill cometgit clone --depth 1 https://github.com/rpamis/comet.git /tmp/comet
mkdir -p ~/.claude/skills
cp -r /tmp/comet/assets/skills/comet ~/.claude/skills/cometPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Comet Entry `/comet` selects Native or Classic from project configuration, then passes the request to that workflow's Skill. Once this Skill is loaded, immediately follow the steps below. The user has already chosen Comet: continue their request without reconsidering whether to use it or merely explaining why you would not proceed. 1. Run the Comet CLI installed on PATH in the current project: ```text comet workflow resolve . --activate --json ``` If the project has no `.comet/config.yaml`, this command saves the global defaults in the project and creates the configured artifact directories. Later changes to global defaults do not overwrite this project's saved configuration. On `command not found`, `executable not found`, or `ENOENT`, stop and report an incomplete Comet CLI installation. Do not search for Skill files, scan platform configuration directories, or invoke an internal bundle directly. If the CLI starts but exits nonzero, cannot parse the configuration, or returns invalid JSON or fields, preserve the original error and stop. Do not choose another entry yourself. 2. Parse the JSON. Only accept `schema: comet.workflow-resolution.v1` and one of the two `skill` values below. 3. Immediately use the Skill tool to load the entry named by `skill`. Load exactly one entry: - `/comet-native` → **Execute immediately:** Use the Skill tool to load the `comet-native` skill. Do not skip this step.
Details
- Skill name
comet- Repository
- rpamis/comet
- Path
assets/skills/comet/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Comet skill do?
Comet workflow entry. Use when the user invokes /comet or asks to use Comet without choosing Native or Classic; load Native or Classic from project configuration.
How do I install the Comet skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add rpamis/comet --skill comet. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Comet popular?
It lives in rpamis/comet, which has 3,306 GitHub stars and 317 forks.
Related skills
Brainstorming
3.3krpamis/comet
Transforms rough ideas into fully-formed designs. Structure your brainstorming sessions and develop ideas systematically.
Dispatching Parallel Agents
3.3krpamis/comet
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Finishing a Development Branch
3.3krpamis/comet
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Comet
3.3krpamis/comet
Comet — OpenSpec + Superpowers dual-star development workflow. Start with /comet for automatic phase detection and dispatch to subcommands. Five phases: open → design → build → verify → archive.
Zeigarnik Effect
3.4kOwl-Listener/designer-skills
Apply the Zeigarnik Effect — incomplete tasks stay mentally active. Use when designing progress indicators, saved drafts, and return hooks. For the emotional shape of the ending, use `peak-end-rule`.
Comet Build
3.3krpamis/comet
Plan, implement, and accept Classic tasks. Use when the user invokes /comet-build or Classic Runtime enters Build or returns to Build for repairs.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.