# CCD Skills
The shipped skills are thin wrappers around the continuity-focused CCD kernel loop. Extension-specific context remains opt-in and should stay outside the default kernel brief.
Canonical sources live under `skills/canonical/`. Generated mirrors under `.agents/skills/`, `.claude/skills/`, and `.gemini/skills/` are derived from that tree by `ccd sync --path .` or `scripts/sync-ai-docs.sh --write`.
## Core Skill Loop
### `ccd-attach`
Bootstraps CCD state for the current project workspace by running `ccd attach --path .`.
### `ccd-start`
Bootstraps CCD through the shipped runtime lifecycle path when the current runtime supports it, then renders a short continuity-only operator brief for current focus and any blocking attention. Raw CLI fallback remains `ccd start --activate --path .`. JSON output and MCP remain the full machine-facing state contract.
### `ccd-checkpoint`
Runs `ccd checkpoint` as the lightweight mid-session pulse. Use it for progress checks and context-pressure triage.
### `ccd-radar`
Runs `ccd radar-state` as the full wrap-up and continuity-evaluation path, but the default developer-facing output should stay outcome-first and continuity-only: confirm continuity is handled, ask for one missing choice if needed, and keep CCD internals in the background. If extension context is needed, request it through explicit extension surfaces instead of the default kernel brief.
### `ccd-git-workflow`
Optional Git-backed follow-through for branch/worktree/commit/push/merge work. This is intentionally separate from startup and continuity loading.
## Installation
Install the published CLI:
```bash
cargo install ccd-cli
```
Then install the shipped skills:
```bash
ccd skills install
```
This is the preferred day-1 path.
If you are contributing or testing unreleased changes, use a source checkout instead:
```bash
git clone https://github.com/dusk-network/ccd.git /tmp/ccd
cargo install --path /tmp/ccd
ccd skills install
```
CCD does not currently claim Homebrew, curl installers, or OS packages as supported distribution channels.
Manual fallback:
Run `scripts/sync-ai-docs.sh --write`, then copy the generated runtime directory for your runtime into `~/.claude/skills/`, `~/.codex/skills/`, or `~/.gemini/skills/`.
## Safety Contract
All shipped skills follow the same contract:
- inspect read-only state first
- obey preview/apply or confirm-write metadata
- keep machine-readable stdout clean
- treat external extension snapshots as explicit extension context, not default kernel truth
- keep Git follow-through separate from startup and handoff loading
## External Recall Providers
CCD can use external recall providers to supplement authored markdown memory with semantic search. The recall seam is read-only and additive — authored memory remains authoritative.
Shipped reference adapters:
- **Mem0 / OpenMemory** — `scripts/memory/mem0_openmemory_adapter.py`
- **Graphiti** — `scripts/memory/graphiti_adapter.py`
### Command-Session Mode
External providers support an optional `mode = "command-session"` transport. When enabled, CCD keeps one adapter child process alive across the sequential recall operations issued by a single top-level command (e.g. `ccd start` runs `search → describe → expand` through one child instead of spawning three). The session is command-scoped — it is not shared across CLI invocations, MCP tool calls, or daemon requests.
See [Memory Recall Providers](../docs/reference/memory-recall-providers.md) for the full contract, config shape, and failure modes. See the [Recall Provider Setup Guide](../docs/guides/recall-provider-setup.md) for end-to-end configuration.
## Advanced Notes
Platform-specific concepts such as coordination scope, pod identity, optional extensions, and runtime-builder paths still exist, but they are not the day-1 story. Start with the kernel loop first.
If your runtime does not support skills, use [bootstrap-prompt.md](../docs/reference/bootstrap-prompt.md).