compose

Evaluate skill proposals using axis, contract, trigger, order, and ownership decisions.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill compose-usurobor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compose
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.core/skills/compose
Command: npx skills add https://github.com/usurobor/cnos --skill compose-usurobor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Compose skill helps teams determine whether a proposed artifact should be published as a new skill or composed from existing skills, ensuring clear boundaries and governance.

Core Features & Use Cases

  • Decide if a new artifact should stand alone as a skill or integrate into an existing composition.
  • Enforce a formal decision framework (axis, contract, trigger, order, ownership) to prevent overlap and hidden dependencies.
  • Provide a concrete composition verdict and supporting documentation for isolation testing.

Quick Start

Provide a sample skill proposal and let Compose determine whether to publish or compose, with explicit axis, contracts, trigger, and order.

Frequently Asked Questions about compose

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

FAQPage Schema
How do I decide whether to publish a new skill or compose from existing ones?▼

To decide whether to publish or compose, apply a formal framework evaluating axis, contract, trigger, order, and ownership to ensure coherent, non-overlapping boundaries and explicit handoffs.

What is the axis and contract framework for skill composition?▼

The axis and contract framework is a governance model that defines explicit boundaries, triggers, execution order, and ownership to prevent overlapping skills and hidden dependencies in compositions.

How do I prevent overlapping skills and hidden dependencies in my architecture?▼

Prevent overlapping skills and hidden dependencies by enforcing formal governance decisions around axis, contracts, triggers, and ownership before finalizing whether to publish or compose artifacts.

How do I test skill composition in isolation?▼

Test skill composition in isolation by following the concrete testing path provided in the composition verdict, which validates the explicit axis, contracts, trigger, and order decisions.

When should I not use skill composition for a new artifact?▼

You should not use skill composition when the proposed artifact lacks clear axis boundaries and ownership, making it impossible to establish explicit contracts and non-overlapping handoffs.