comet

Resolves the configured Comet workflow entry and loads the matching Native or Classic skill.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill comet-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/comet
Command: npx skills add https://github.com/JhonMA82/api-starter --skill comet-jhonma82

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? When a user invokes /comet without choosing between the Native and Classic workflows, this Skill removes ambiguity by reading the project's permanent configuration and routing to exactly one workflow entry, preventing accidental mixing of the two workflows' states and artifacts. ## Core Features & Use Cases - Deterministic entry resolution: Runs the public Comet CLI (comet workflow resolve . --json) and accepts only the comet.workflow-resolution.v1 schema to pick the configured entry. - Strict single-entry loading: Loads exactly one of the comet-native or comet-classic skills and passes the user's original request through unchanged. - Fail-safe error handling: Stops with a clear explanation when the CLI is missing, exits nonzero, or returns invalid output, without guessing or scanning configuration directories. - Use Case: A developer types /comet in a project configured for the Classic workflow; the Skill resolves the configuration and immediately hands off to the Classic workflow skill. ## Quick Start Invoke /comet in a project with Comet configured and let it resolve and load the workflow entry defined in the project configuration.

Frequently Asked Questions about comet

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

FAQPage Schema
How do I use the /comet command in a project?▼

Invoke /comet in a project where Comet is configured. The skill runs the Comet CLI to resolve the project's permanent workflow entry, then loads either the comet-native or comet-classic skill and passes your original request to it unchanged.

What is the difference between Comet Native and Classic workflows?▼

Native and Classic are two independent Comet workflows with separate states and artifacts. The /comet entry never switches between them based on task size or judgment; it only loads the one entry defined in the project configuration.

Why does /comet report that the Comet CLI installation is incomplete?▼

This happens when the comet executable is not found on PATH, producing command not found or ENOENT errors. Install or repair the public Comet CLI; the skill intentionally does not search for skill files or invoke internal bundles as a fallback.

Can /comet choose a workflow automatically based on my task?▼

No. The skill selects the entry solely from the project configuration returned by the CLI. It never re-evaluates task suitability or switches workflows based on file count, active changes, or model judgment.

What happens when the Comet CLI returns invalid output?▼

If the CLI exits nonzero, configuration parsing fails, output is not JSON, or a required field is invalid, the skill stops and reports the original error. It does not fall back, guess, or scan platform configuration directories.