Quick Start: Combining Any Skill

Call /comet-any in the Agent to start. The flow prompts for confirmation, evaluation, release, and distribution steps.

/comet-any (also known as Skill Creator) is Comet’s single entry for creating, optimizing, and composing reusable Skills. This page gives you the shortest onboarding path. For internals, continue to Advanced topics.

Combining any Skill remains an experimental feature. Subsequent versions may undergo significant refactoring of processes, command interfaces, product structures, and release access control, and may also remove or replace some capabilities. It is recommended to first try it out in non-critical projects and review the changelog before upgrading Comet.

Use cases

I want to condense a recurring process in the team into a reusable Skill, eliminating the need to re-describe it each time.
Want to add, replace or close certain links on the basis of the classic five stages of /comet.
I want to organize the existing but scattered skills into standard Skill packages that are assessable, releasable and distributable.

What do you need to prepare first

Comet has been installed. Run comet doctor to confirm that the CLI is normal. If not installed yet, see Installation and Update
** An Agent platform that supports Skill **, such as Claude Code, Codex, Cursor, etc. /comet-any is a Skill called on these platforms and is not an independent terminal command.
Optional project-level preferences. On first use, /comet-any scans available platforms and recommends defaults. You can skip this step or prepare preferences in advance.

/comet-any is the only entry point that users need to remember. . When you need to check the recovery status, use comet creator. After entering the release, use comet Publisher . For daily use, there is no need to directly run , COMET bundle.

Create the main line

/ Comet-any create → comet eval verify → comet creator status/next See Next → review/approve/run → distribute

Call /comet-any to start. After an interruption, run comet creator next <name> for the suggested action or comet creator status <name> for readiness, blockers, and evidence.

The little fish advances the Skill card along the /comet-any, eval evidence, creator next/status and publish/distribute routes

/comet-any is responsible for creating the Skill, comet eval provides the evidence, and comet creator next/status translates the interrupt process into the next user command

Step 1: Call /comet-any and describe the target

Enter: In the Agent platform

/comet-any

Then describe the Skill you want to create. The more specific the description, the higher the quality of the generated Skill. A good description should at least include: what to do, how many steps to take, and for whom to reuse. For example:

Please create a PR review assistant.
It needs to first clarify the review scope, then formulate the inspection plan, and finally carry out the code review.
Finally, it is required to verify the evidence before completion.
The goal is to be reused by the team, not just for the current task.

Step 2: Select the starting point

/comet-any will allow you to choose one from three starting points. This is the first layer of choice of Skill Creator, which determines the entire generation method:

Starting point	Skill Creator Intent	Meaning	Typical scenarios
”Five-stage customization based on Comet’s existing Skill.	`customize-comet`	Make incremental adjustments on the classic five stages	I want to add a review process to `/comet` and require the use of component libraries
Create a brand-new workflow Skill	`new-skill`	Create a brand-new workflow from the target description	Establish a team-specific process
Organize existing skills	`upgrade-existing`	Organize the existing skills into standard packages that can be released	Standardize the scattered skills

Whichever starting point you choose, /comet-any compiles the target into the same Workflow Contract, composed of Workflow Nodes, Skill Bindings, Required Skill Calls, Output Schemas, Guardrails, and Handoffs. See the Skill Creator overview.

When you choose five-phase customization based on an existing Comet Skill, /comet is a protected boundary. You cannot replace the implementation of control nodes (open/execute/verify/archive). You can only add Required Skill Calls, augment nodes, or disable optional nodes.

Step 3: Confirm the combination plan (Skill Creator Confirmation page)

/comet-any will read the real skills in the project, compile the target into a Workflow Contract, generate a ** combination scheme **, and then ** pause for your confirmation **. This page is called the “Skill Creator Solution Confirmation Page “and it is a key checkpoint in the entire process. It will display:

What type of Skill (Skill Creator Intent) are you working on and what are your goals
Which nodes should be retained, which Required Skill calls should be added, which node implementations should be replaced, and which optional nodes should be closed
What cannot be done (for example, replacing the control node will be rejected)
The responsibilities of each node, the implementation Skill, the skills that must be called, and the Output Schema
Workflow Contract type (comet-five-phase-overlay/workflow-kernel) and Output Schemas list
Are there any missing or ambiguous candidates that you need to handle
What executable disclosures will scripts/hooks bring
Which files will be generated

You need to make one of the three choices:

** Confirm Generation ** - Write the plan into draft and continue generating.
** Modify the plan ** - Regenerate the plan after adjusting the goals, preferences or candidates.
“Cancel” - Do not write any status.

If /comet-any prompts that there are candidate missing or there are multiple sources of from , it will definitely pause and ask you - it will never choose for you or silently ignore it. Just select the source as prompted. This is a hard and fast rule, not an optional behavior.

Step 4: Evaluation

After confirmation, /comet-any generates the Skill package. Then evaluate whether it meets the standards. This is the “mandatory evidence” before release, not an optional step:

# Low-cost discovery pre-checking (without consuming model calls)
comet eval ./generated-skill/comet/eval.yaml --collect

# 2. Conduct real evaluations and generate browsable HTML reports
comet eval ./generated-skill/comet/eval.yaml --html

Open the Report path printed from the CLI and confirm that the assessment has passed. For detailed environmental preparation and report interpretation, please refer to Evaluate Any Skill

Prerequisite: To run comet eval, install uv, Python 3.11+, and Docker, then set ANTHROPIC_API_KEY (or ANTHROPIC_AUTH_TOKEN). See Evaluation quickstart · What you need before running.

Step 5: Release and distribution

After the assessment is passed, check the release readiness and release:

# View the complete readiness and blocking items
comet creator status my-skill --project . --json

# Just want to know what to run next
comet creator next my-skill --project . --json

# Generate review summaries (see Readiness/Blockers/Evidence)
comet publish review my-skill --platform claude --json

# Manually approve the current version
comet publish approve my-skill --reviewer alice --json

# "Publish
comet publish run my-skill --platform claude --json

Before distribution to the platform, it will first force a preview run. Only after confirmation will it be truly written.

# Forced preview (no files will be written)
comet publish distribute my-skill --platform claude --scope project --preview --json

# After confirming that the preview is correct, distribute it in reality
comet publish distribute my-skill --platform claude --scope project --json

The complete publish status chain and access control can be found at Publish and Distribute Skill

/comet-any also advances these steps and asks for your confirmation at each one. The commands above are an optional manual path for troubleshooting or automation.

The complete process can be understood in one picture

Optional: Prepare preference files

The first time you use it, /comet-any will scan the platform skills and recommend default preferences. You can also directly create a preference file and tell it which skills to prioritize for reuse. Save to .comet/skill-preferences.yaml:

# .comet/skill-preferences.yaml
version: 1
mode: advisory

prefer:
  - brainstorming
  - writing-plans
  - requesting-code-review
  - verification-before-completion

require:
  - verification-before-completion

policies:
  missing: ask
  ambiguous: ask
  deviation: explain
  scripts: disclose
  hooks: disclose

For the complete field meanings, please refer to Skill Preferences and real source

Q&A

What's the difference between /comet-any and /comet

/comet is used to complete a project change. /comet-any is used to create, optimize or organize reusable skills.If you want to create features, fix bugs or modify project code, use /comet. If you want to condense a set of processes into reusable skills or add team rules on the basis of the five stages of /comet, use /comet-any.

Do I need to understand words like Workflow Node and Output Schema

It is not necessary for ordinary use. You only need to look at what is done at each step on the solution confirmation page, which skills will be called, and which capabilities will be added or disabled.When doing deep customization or reviewing the product, then refer to Overview of Skill Creator

What should I do if I stop halfway through

Tell the Agent, “Continue the previous Skill creation.” /comet-any first attempts to restore the current authoring state, showing its name, status, next step, and blocker so you can choose what to continue. See The complete Skill creation workflow · Resume the interrupted process.

Will the products be distributed automatically

No. After / Comet-any is released, it will ask you if you want to distribute it, and will first show a preview of . It will only be truly written into the platform after your confirmation. Preview is a mandatory step and cannot be skipped.

I don't want to run the eval and publish commands myself

You can call only /comet-any throughout the process. It will proactively advance the evaluation and release and ask for your confirmation at each step. The commands listed on this page are to help you understand the process, facilitate troubleshooting or perform automation integration.

Advanced content

The basic path ends here. If you need a deeper understanding of Skill Creator, look at these pages:

Advanced Topics	Suitable scenarios
Overview of Skill Creator	Understand Workflow Contract, three types of starting points, protected boundaries and built-in nodes
The complete process for creating a Skill: ](/en/skill-creator/workflow)	A detailed explanation of every step from restoring the status to generation, evaluation, review, release, and distribution
Skill preferences and real sources	`advisory`/`strict` patterns, strategies, `resolved-skills.json` evidence
Publish and distribute Skill](/en/skill-creator/publishing)	readiness status chain, access control, capability gap and executable disclosure
Skill and Engine	Skill package structure, Engine running loop, runtime check, immutable snapshot

Quickstart

Advanced

Related commands

Quick Start: Combining Any Skill

Use cases

What do you need to prepare first

Create the main line

Step 1: Call /comet-any and describe the target

Step 2: Select the starting point

Step 3: Confirm the combination plan (Skill Creator Confirmation page)

Step 4: Evaluation

Step 5: Release and distribution

The complete process can be understood in one picture

Optional: Prepare preference files

Q&A

Advanced content

​Use cases

​What do you need to prepare first

​Create the main line

​Step 1: Call /comet-any and describe the target

​Step 2: Select the starting point

​Step 3: Confirm the combination plan (Skill Creator Confirmation page)

​Step 4: Evaluation

​Step 5: Release and distribution

​The complete process can be understood in one picture

​Optional: Prepare preference files

​Q&A

​Advanced content

Use cases

What do you need to prepare first

Create the main line

Step 1: Call /comet-any and describe the target

Step 2: Select the starting point

Step 3: Confirm the combination plan (Skill Creator Confirmation page)

Step 4: Evaluation

Step 5: Release and distribution

The complete process can be understood in one picture

Optional: Prepare preference files

Q&A

Advanced content