skills.rest
JhonMA82
JhonMA82COMMUNITY
Explore all skills by this author →
GitHub

comet-any

Generates verifiable Comet-native workflow Skill bundles from confirmed user proposals.

Updated Aug 5, 2026
Search Tags:#workflow#subagents#guardrails#eval#comet#publish readiness#skill generator
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill comet-any-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet-any
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/comet-any
Command: npx skills add https://github.com/JhonMA82/api-starter --skill comet-any-jhonma82

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: Skills get guessed from names, state semantics break, and nothing is validated before publishing. This Skill turns a described workflow goal into a confirmed plan, then generates a verifiable Comet-native Skill Bundle with eval evidence, review, and publish readiness gating. ## Core Features & Use Cases - Three starting points: customize the /comet-classic five-phase Skills (open/design/build/verify/archive) via an overlay, create a new workflow-kernel Skill from a goal, or upgrade an existing Skill with Workflow Nodes, Skill Bindings, Output Schemas, Guardrails, and Handoffs. - Confirmation-gated generation: resolves real local Skills via the comet creator CLI, shows a proposal with enforcement levels (guarded, handoff-guarded, evidence-only, advisory), and waits for explicit confirmation before writing any Bundle draft. - DAG-dispatched authoring lanes: dispatches six subagent lanes (script, reference, pause-points, workflow-entry, skill-core, skill-review) in dependency waves, records schema-validated outputs, and blocks on BLOCKED or NEEDS_CONTEXT statuses. - Readiness and safe publishing: requires current draft-hash eval evidence, human approval, and an install preview showing "No files were written" before any real distribution. - Use Case: A team wants every execute node to require their component-library Skill and every review node to require a whitebox code standard; this Skill produces a comet-five-phase-overlay bundle enforcing those Required Skill Calls with guardrails and eval evidence. ## Quick Start Invoke /comet-any and describe the workflow you want, for example asking it to customize the /comet-classic five-phase Skills so that execute requires your component library Skill and review requires your whitebox code standard.

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 a component-library Skill at the execute node. It builds a comet-five-phase-overlay plan, shows a confirmation page with enforcement levels, and only generates the bundle after you confirm.

How do I create a new workflow Skill from scratch?▼

Describe your goal to /comet-any and choose the create-a-new-workflow path. It resolves real local Skills with comet creator candidates, compiles a workflow-kernel contract with nodes, output schemas, and guardrails, then generates the bundle after your confirmation.

Can the overlay override the open, execute, verify, or archive nodes?▼

No. Control nodes (open, execute, verify, archive) cannot be overridden in ordinary mode, and overlay state must come from .comet.yaml. Only producer nodes like design and plan may be overridden when they satisfy the matching Output Schema.

Why can't my generated Skill bundle become ready for publish?▼

Readiness blockers include missing current draft-hash eval evidence, missing human approval, required capability gaps, or unconfirmed executable disclosures. Stale eval evidence from an older draft hash also cannot advance readiness.

Does the Skill install or publish bundles automatically?▼

No. Publishing requires explicit human approval after eval and review, and installation must start with a preview showing planned files and 'No files were written'. Real distribution only runs after you confirm the preview.

Related Skills

Explore More Software Engineering Skills→
aaronjmarsaaronjmars
714

pack-submit

Packages an existing skill as a public GitHub community pack and submits a registry PR.

Community
Advanced
LAF-USLAF-US

build-mcpb

Package a local MCP server with its runtime into a .mcpb bundle.

Official
Advanced
Innorve-IncInnorve-Inc

innorve-maturity-gate

Evaluates AI skill readiness against the Innorve Maturity Ladder and returns a structured Maturity Gate Report.

Official
Advanced
manuscomanusco

resonance-ops-skill-author

Authors, validates, and evaluates Resonance skills using the Forge compiler and eval protocol.

Community
Advanced