activation

Bootstrap an existing repository with CDD governance structures and configuration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstrap an existing repository to operate under CDD governance by scaffolding required structures, pinning the CDD version, and establishing labels, identity, CI, notifications, secrets, and operator registry.

Core Features & Use Cases

  • One-time bootstrap to enable CDD governance across a repo.
  • Generates a .cdd/ directory with CDD-VERSION, DISPATCH, CADENCE, OPERATORS, MCAs/INDEX.md, and a vendored skills bundle declaration.
  • Provides a repeatable activation path that creates durable governance artifacts for audits and cycle management.

Quick Start

Run the activation skill on a repository with a designated primary branch and sufficient admin privileges to configure labels, secrets, and CI.

Frequently Asked Questions about activation

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

FAQPage Schema
How do I bootstrap an existing repository to operate under CDD governance?

To bootstrap CDD governance, run the activation skill on a repository with a designated primary branch to scaffold a .cdd/ directory with CDD-VERSION, DISPATCH, CADENCE, OPERATORS, and MCAs.

What do I need to set up CDD governance structures and CI workflows in my repo?

You need an existing repository with a designated primary branch and an admin-empowered operator who can configure host integrations such as GitHub labels, secrets, and CI workflows.

What files and artifacts are generated when scaffolding CDD repository governance?

Scaffolding CDD repository governance generates a .cdd/ directory containing CDD-VERSION, DISPATCH, CADENCE, OPERATORS, MCAs/INDEX.md, and a vendored skills bundle declaration.

When should I use a one-time bootstrap to enable CDD governance across my repository?

Use a one-time bootstrap when you need durable governance artifacts for audits and cycle management, establishing identity, notifications, secrets, and an operator registry in a single repeatable activation path.

Can I apply CDD activation to a repository without admin privileges for host integrations?

No, CDD activation applies to repositories with an admin-empowered operator who can configure host integrations such as GitHub labels, secrets, and CI workflows to fully establish governance.

What is the best way to pin the CDD version and establish an operator registry?

The best way to pin the CDD version and establish an operator registry is running the activation skill, which scaffolds the required .cdd/ directory structures and pins the CDD version automatically.