comet-any

Generates verifiable Comet workflow Skill bundles from confirmed workflow contracts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Creating or customizing multi-phase agent workflow Skills by hand is error-prone: Skill bindings, output schemas, guardrails, eval evidence, and publish readiness can drift apart. This Skill turns a confirmed workflow goal into a governed, auditable Comet Skill bundle with deterministic scripts and enforced readiness gates. ## Core Features & Use Cases - Workflow Contract Compilation: Expresses a goal as Workflow Nodes, Skill Bindings, Required Skill Calls, Output Schemas, Guardrails, and Handoffs, compiled into a single workflow-protocol.json source of truth. - Comet Classic Overlay: Customizes the /comet-classic five-phase workflow (open/design/build/verify/archive) without overriding protected control Nodes or .comet.yaml state semantics. - Subagent Authoring Pipeline: Dispatches six authoring lanes (script, reference, pause-points, workflow-entry, skill-core, skill-review) by DAG, records lane outputs, and blocks on missing claims. - Eval and Publish Readiness: Requires current draft-hash eval evidence, human approval, and install preview before any publish or distribution. - Use Case: A team wants every code change to require the elementui component library at execute time and whitebox-code-standard at review time; this Skill generates an overlay bundle enforcing those Required Skill Calls with guarded evidence. ## Quick Start Ask the assistant to customize the /comet-classic five-phase workflow so that execute requires the elementui Skill and review requires the whitebox-code-standard Skill, then confirm the generated proposal.

Frequently Asked Questions about comet-any

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

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

Invoke /comet-any and describe the customization, such as requiring specific Skills at execute or review nodes. It proposes an overlay plan, waits for your confirmation, then generates a bundle that preserves the open/design/build/verify/archive control flow and .comet.yaml state.

How do I create a new workflow Skill with comet-any?▼

Describe your goal and candidate Skills; the Skill resolves real local Skills via the comet creator CLI, builds a workflow-kernel contract with nodes and output schemas, and generates the bundle only after you confirm the proposal.

Can comet-any override control nodes like open or verify?▼

No. In ordinary overlay mode the control nodes open, execute, verify, and archive cannot be overridden. Only producer nodes like design and plan may be replaced, and only when the replacement satisfies the matching Output Schema.

What happens if eval evidence is missing or stale?▼

Missing, skipped, failed, or stale-hash eval evidence blocks readiness. The bundle cannot become ready or be published until eval is run against the current draft hash and a human approves the review.

Does comet-any install generated Skills automatically?▼

No. Installation always starts with a preview showing planned files and 'No files were written'. Real distribution happens only after you explicitly confirm the preview result.

When should I not use comet-any?▼

Do not use it for general Skill authoring, cleanup, or review tasks. It is intended only when explicitly invoked as /comet-any or when customizing the /comet-classic workflow or creating and upgrading Comet-managed workflow Skills.