comet-any

Create or upgrade Comet Classic workflow Skills through a confirmed authoring pipeline.

2.9k|284|Updated May 14, 2026
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-any
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-any
Source: https://github.com/rpamis/comet/tree/main/assets/skills/comet-any
Command: npx skills add https://github.com/rpamis/comet --skill comet-any

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Turning a workflow idea into a working Comet Skill requires resolving real Skills, designing workflow nodes, writing scripts, and passing eval and publish readiness checks. This Skill guides that entire creation and upgrade process so the result is a verifiable Comet-native Skill Bundle rather than an ad-hoc prompt.

Core Features & Use Cases

  • Three starting points: customize the /comet-classic five-phase Skills, create a new workflow-kernel Skill from a goal, or upgrade an existing Skill with new nodes, bindings, schemas, and guardrails.
  • Confirmed proposal before generation: resolves real local Skills via the comet creator CLI, shows each node, binding, output schema, and enforcement level, and waits for explicit user confirmation before writing anything.
  • Subagent authoring pipeline: dispatches six role-specific authoring lanes (script, reference, pause-points, workflow-entry, skill-core, skill-review) by DAG, then generates, evaluates, reviews, and previews the Bundle before publish.
  • Use Case: A team wants every code change to use their component library and pass a whitebox review. Describe that goal, confirm the proposed overlay plan, and receive a generated workflow Skill that requires elementui at execute nodes and whitebox-code-standard at review, with eval evidence and install preview.

Quick Start

Ask the assistant to customize the /comet-classic workflow so that execute nodes require your component library Skill and the review node requires your whitebox review Skill, then confirm the proposed plan.

Frequently Asked Questions about comet-any

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Comet workflow Skill?

Describe the workflow goal you want, and the Skill resolves real local Skills, proposes a plan of nodes, bindings, and output schemas, then waits for your confirmation. After confirmation it runs the authoring pipeline and generates a verifiable Skill Bundle.

How do I customize the /comet-classic five-phase workflow?

Use a comet-five-phase-overlay plan that patches nodes such as execute, subagent-execute, or review with required skill calls. Control nodes like open, execute, verify, and archive cannot be overridden in ordinary mode, and .comet.yaml remains the primary state.

Can I replace a control node like open or verify?

Not in ordinary overlay mode; control nodes open, execute, verify, and archive are protected. If you insist on replacing one, the flow switches to an advanced workflow-kernel that requires a new state model, output schemas, and guardrails.

What happens before a generated Skill is published?

The Bundle must pass quick or full eval with current draft hash evidence, a skill-review barrier, and human approval of the readiness report. Installation always starts with a preview showing planned files and that no files were written.

Why does generation pause and ask for confirmation?

The Skill never writes a Bundle draft before you confirm the proposal. The confirmation page lists every node, bound Skill, required skill call, output schema, and its enforcement level so you can verify the plan first.

When should I not use this Skill?

Do not use it for general Skill authoring, cleanup, or review tasks unrelated to Comet workflows. It is specifically the Comet Creator path for building or upgrading Comet Classic workflow Skills.