comet

Resolves the /comet entry point to load the configured Native or Classic workflow skill.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill comet-shrek-abaper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet
Source: https://github.com/shrek-abaper/sap-nexus-agent/tree/main/.comet/skills/skills/comet
Command: npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill comet-shrek-abaper

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? When a user invokes /comet without specifying Native or Classic, this Skill removes ambiguity by reading the project's permanent configuration and loading exactly one workflow entry, preventing manual guessing or accidental workflow mixing. ## Core Features & Use Cases - Deterministic Entry Resolution: Runs the public Comet CLI (comet workflow resolve . --json) and validates the output against the comet.workflow-resolution.v1 schema before acting. - Single-Entry Loading: Loads exactly one of the comet-native or comet-classic skills based on the resolved configuration, then forwards the user's original request unchanged. - Fail-Closed Error Handling: Stops with a clear explanation when the CLI is missing, exits nonzero, or returns invalid output, without falling back to scanning directories or guessing. - Use Case: A developer types /comet in a project configured for the Classic workflow; the Skill resolves the configuration and immediately loads comet-classic to continue the task. ## Quick Start Invoke /comet in a project with the Comet CLI installed and let it resolve and load the configured workflow entry automatically.

Frequently Asked Questions about comet

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

FAQPage Schema
How do I use /comet without choosing Native or Classic?▼

Invoke /comet directly and the Skill runs `comet workflow resolve . --json` to read the project's permanent configuration. It then loads exactly one entry, either comet-native or comet-classic, and passes your original request to it unchanged.

What is the difference between comet-native and comet-classic workflows?▼

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

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

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

What happens when comet workflow resolve returns invalid output?▼

The Skill stops and reports the original error without guessing. It only accepts output matching the comet.workflow-resolution.v1 schema with a recognized skill value; nonzero exits, parse failures, or invalid fields all halt execution.

Can /comet switch workflows based on task size or active changes?▼

No. The Skill explicitly forbids switching workflows based on task size, file count, active changes, or model judgment. Entry selection comes solely from the resolved project configuration.