epsilon

Detect CDD gaps from receipt streams and generate cdd-iteration.md artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ε's CDD-specific instantiation observes receipt streams across cycles, surfaces cdd-*-gap findings, applies MCA discipline, and writes cdd-iteration.md when protocol_gap_count > 0.

Core Features & Use Cases

  • Detects cdd-gap patterns (e.g., cdd-skill-gap, cdd-protocol-gap, cdd-tooling-gap, cdd-metric-gap) from receipt streams and triggers appropriate patching workflows.
  • Applies MCA discipline to determine patch urgency (ship now / next-MCA / no-patch) and generates the per-cycle iteration artifact when required.
  • Produces cross-repo traces and centralized iteration records to support long-term coherence across hubs.

Quick Start

Initialize the cycle by reading the receipt stream, apply the ε rules to surface gaps, and generate a cdd-iteration.md when protocol gaps exist.

Frequently Asked Questions about epsilon

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

FAQPage Schema
How do I detect protocol gaps from receipt streams to guide iteration improvements?

You detect protocol gaps by observing receipt streams across cycles to surface cdd-skill-gap, cdd-protocol-gap, cdd-tooling-gap, and cdd-metric-gap findings. This applies MCA discipline to determine patch urgency and generates a cdd-iteration.md artifact when protocol gaps exist.

What is the ε=δ collapse rule for protocol gap detection?

The ε=δ collapse rule is a CDD-specific discipline applied during gap detection to ensure coherence across cycles. It governs how detected gaps are classified and routed to .cdd revisions for protocol improvements.

How do I classify gap urgency and decide between shipping a patch now or waiting for the next MCA?

Apply MCA discipline to classify gap urgency by evaluating cdd-gap patterns from receipt streams. This determines whether to ship now, defer to the next MCA cycle, or apply no patch, ensuring durable protocol fixes.

When do I need to generate a cdd-iteration.md file for my development cycle?

Generate a cdd-iteration.md file when the protocol_gap_count is greater than zero. It serves as a durable iteration artifact that records cross-repo traces and centralized iteration records to support long-term coherence.

Can I integrate gap detection with existing operator workflows across multiple hubs?

Yes, the gap detection process integrates with operator workflows by routing artifacts to .cdd revisions. It produces cross-repo traces and centralized iteration records that support long-term coherence across distributed hubs.

What types of CDD gaps can be surfaced from receipt stream analysis?

Receipt stream analysis surfaces cdd-skill-gap, cdd-protocol-gap, cdd-tooling-gap, and cdd-metric-gap patterns. Each gap type triggers appropriate patching workflows to drive durable protocol improvements.