comet creator

comet creator is the CLI companion for /comet-any. It is focused on three jobs: recovering flows, reading publishing readiness, and giving one recommended next command. For day-to-day work, start from /comet-any. Run comet creator directly when a flow is interrupted, when you need diagnostics, or when a specific step is automated.

Difference from publish

Command	What it owns	When to use it
`comet creator`	Creation, recovery, candidate resolution, proposal confirmation, generation, and authoring lanes	The `/comet-any` flow has not reached publishing, or you want to know the next step
`comet publish`	Review, approve, publish, distribute	The eval evidence is ready and you are preparing to publish and distribute
`comet bundle`	Advanced backend	Audit, troubleshooting, platform compile debugging

The recommended main line is:

/comet-any creates -> comet eval verifies -> comet creator status/next -> comet publish (review/approve/publish/distribute)

For command details in the publishing phase, see comet publish; the authoritative description of the state machine, readiness conclusions, and blocker codes is in Publishing and distributing Skills.

Subcommands

Command	Purpose	Required arguments
`comet creator list`	List recoverable Skill Creator candidates	-
`comet creator status <name>`	Read readiness, blockers, warnings, and evidence	`<name>`
`comet creator next <name>`	Print the single recommended next step	`<name>`
`comet creator guide`	Read the first-run wizard, preferences, and recoverable flow summary	-
`comet creator candidates`	Discover Skill candidates available for composition	-
`comet creator propose <name>`	Preview the Skill Creator plan without writing state	`<name>`, `--file`
`comet creator init <name>`	Initialize or update state with a confirmed plan	`<name>`, `--file`
`comet creator resolve <name>`	Resolve missing or ambiguous candidates	`<name>`, `--candidate`
`comet creator authoring-plan <name>`	Read the authoring lane plan of the generated Skill	`<name>`
`comet creator authoring-record <name>`	Record the output of an authoring lane	`<name>`, `--lane`, `--file`
`comet creator generate <name>`	Generate the Skill package from confirmed metadata	`<name>`

Every subcommand supports --project <dir> and --json.

Common recovery commands

# List recoverable flows
comet creator list --project . --json

# Read full status, readiness, and evidence
comet creator status review-helper --project . --json

# Read only what to do next
comet creator next review-helper --project . --json

The text output of comet creator next includes the current status, the current stage, the recommended action, the recommended command, the reason, and whether the step needs user confirmation.

Next step for review-helper
Status: draft
Current step: needs-eval
Action: Run repository eval for the generated Skill
Command: comet eval ./generated-skill/comet/eval.yaml --quick --html
Reason: Current draft hash is missing passing eval evidence
Requires confirmation: yes

Plan and generation commands

/comet-any normally invokes these commands for you. Manual invocation is mainly for automation pipelines or troubleshooting candidate and generation state.

# First-run wizard
comet creator guide --project . --json

# Discover candidate Skills
comet creator candidates --project . --json

# Preview a composition plan without writing state
comet creator propose review-helper --file ./plan.json --json

# Write state after the user confirms the plan
comet creator init review-helper --file ./plan.json --confirmed-proposal --json

# Resolve an ambiguous candidate
comet creator resolve review-helper --candidate review-flow --source ./skills/review-flow --json

# Ignore a missing candidate; a reason is required
comet creator resolve review-helper --candidate optional-helper --ignore-missing --reason "not needed for this workflow" --json

# Generate the Skill package
comet creator generate review-helper --json

Do not bypass the proposal confirmation page and generate directly. /comet-any must show the Skill Creator proposal confirmation page first and wait for your confirmation before it writes a draft.

Authoring lane commands

A generated Skill is not a thin template. /comet-any uses authoring lanes to write entry content, node guidance, script contracts, reference files, and review evidence.

# Read the quick or full authoring plan
comet creator authoring-plan review-helper --depth quick --json
comet creator authoring-plan review-helper --depth full --json

# Record the output of a lane
comet creator authoring-record review-helper --lane skill-core --file ./lane-output.json --json

If generated content still keeps AUTHORING PENDING markers, the publishing readiness check reports an [authoring] blocker. You need to finish the corresponding lane and record its output before continuing to eval and publishing. For the full meaning of the blocker codes and their recovery suggestions, see Publishing and distributing Skills: Blocker codes.

Next steps

Getting started: combine any Skill — run the full main line from /comet-any
Full Skill creation workflow — understand every stage
comet publish — review, approve, publish, and distribute after eval
Publishing and distributing Skills — the authoritative state machine, readiness, and blocker codes
comet bundle — the advanced backend reference

Install and health checks

Skills, evals, and publishing

Core scripts

Difference from publish

Subcommands

Common recovery commands

Plan and generation commands

Authoring lane commands

Next steps

​Difference from publish

​Subcommands

​Common recovery commands

​Plan and generation commands

​Authoring lane commands

​Next steps

Difference from publish

Subcommands

Common recovery commands

Plan and generation commands

Authoring lane commands

Next steps