Claude Skills by odylith

- CLI-first is non-negotiable for both Codex and Claude Code. Remove all hand-authoring for places where Odylith CLI should be doing the heavy-lifting. When an Odylith CLI command exists for an operation, you must call the CLI command and you must not hand-edit governed files the CLI owns. Hand-authoring governed truth where a CLI exists is a hard policy violation, not a stylistic preference. The authoritative policy, CLI surface enumeration, allowed hand-edit surfaces, and failure-mode handling

Use this skill only when the user explicitly invokes `$odylith-compass-log` or asks to append a bounded execution note into Compass. 1. Identify the current workstream, entry kind, and one-sentence summary worth preserving. 2. Run `./.odylith/bin/odylith compass log --repo-root . --kind <kind> --summary "<summary>"`. 3. Add `--workstream` and `--component` when the active slice is known and the command needs those anchors explicitly. 4. Keep the log entry factual, short, and specific to the c...

Use this skill only when the user explicitly invokes `$odylith-compass-refresh` or asks to refresh Compass and wait for the current pass to settle. 1. Run `./.odylith/bin/odylith compass deep-refresh --repo-root .`. 2. Report whether the refresh completed, deferred, or surfaced a provider or runtime blocker. 3. If the refresh is blocked, summarize the blocker instead of retrying blindly.

- CLI-first is non-negotiable for both Codex and Claude Code. Remove all hand-authoring for places where Odylith CLI should be doing the heavy-lifting. When an Odylith CLI command exists for an operation, you must call the CLI command and you must not hand-edit governed files the CLI owns. Hand-authoring governed truth where a CLI exists is a hard policy violation, not a stylistic preference. The authoritative policy, CLI surface enumeration, allowed hand-edit surfaces, and failure-mode handling

- CLI-first is non-negotiable for both Codex and Claude Code. Remove all hand-authoring for places where Odylith CLI should be doing the heavy-lifting. When an Odylith CLI command exists for an operation, you must call the CLI command and you must not hand-edit governed files the CLI owns. Hand-authoring governed truth where a CLI exists is a hard policy violation, not a stylistic preference. The authoritative policy, CLI surface enumeration, allowed hand-edit surfaces, and failure-mode handling

- CLI-first is non-negotiable for both Codex and Claude Code. Remove all hand-authoring for places where Odylith CLI should be doing the heavy-lifting. When an Odylith CLI command exists for an operation, you must call the CLI command and you must not hand-edit governed files the CLI owns. Hand-authoring governed truth where a CLI exists is a hard policy violation, not a stylistic preference. The authoritative policy, CLI surface enumeration, allowed hand-edit surfaces, and failure-mode handling

Use this skill only when the user explicitly invokes `$odylith-context` or asks to resolve a known Odylith anchor into the smallest useful local context. 1. Use this only after the current turn has run `odylith start`, or after a fresh session-start packet already exists and an exact anchor is known, such as a workstream id, bug id, component, diagram id, or repo path. 2. Do not run this in parallel with `odylith start`; startup is the serial gate and context is the follow-on exact-anchor pac...

- CLI-first is non-negotiable for both Codex and Claude Code. Remove all hand-authoring for places where Odylith CLI should be doing the heavy-lifting. When an Odylith CLI command exists for an operation, you must call the CLI command and you must not hand-edit governed files the CLI owns. Hand-authoring governed truth where a CLI exists is a hard policy violation, not a stylistic preference. The authoritative policy, CLI surface enumeration, allowed hand-edit surfaces, and failure-mode handling

- CLI-first is non-negotiable for both Codex and Claude Code. Remove all hand-authoring for places where Odylith CLI should be doing the heavy-lifting. When an Odylith CLI command exists for an operation, you must call the CLI command and you must not hand-edit governed files the CLI owns. Hand-authoring governed truth where a CLI exists is a hard policy violation, not a stylistic preference. The authoritative policy, CLI surface enumeration, allowed hand-edit surfaces, and failure-mode handling

Use this skill when Odylith Discipline behavior, credit-safe hard laws, learning-spine signals, or benchmark-proved pressure behavior need validation or implementation.

Use this skill only when the user explicitly invokes `$odylith-doctor` or asks to verify or repair the current Odylith install. 1. Run `./.odylith/bin/odylith doctor --repo-root .` for inspection. 2. Add `--repair` only when the user explicitly asks for repair or when the current task is clearly repair-authorized. 3. Add `--reset-local-state` only when the user explicitly wants a stronger local-state reset. 4. Report the verified posture or blocker instead of retrying blindly.

Use this skill when the operator asks Odylith to build, govern, plan, or architect a new project before source code exists. 1. Do not refuse merely because the repo has no app source. Greenfield intent is valid proposal evidence, not source evidence. 2. Run the host-reasoning contract path: `./.odylith/bin/odylith greenfield propose --repo-root . --prompt "<operator request>"`. 3. Use the active host model's full reasoning to draft the proposal in normal chat. The CLI output is the evidence/s...

Use this skill when guidance behavior pressure cases, high-risk agent instructions, or cross-host guidance contracts need deterministic validation. Guidance Behavior is the first deterministic pressure-family proof lane under Odylith Discipline; it proves concrete hard-law families while the broader Odylith Discipline layer handles open-world stance, credit budgets, learning signals, and benchmark sovereignty.

Use this skill only when the user explicitly invokes `$odylith-query` or asks to search the local Odylith projection store after concrete anchors already exist. 1. Confirm that a concrete noun already exists, such as a workstream, component, path, bug id, or diagram id. 2. Run `./.odylith/bin/odylith query --repo-root . "<terms>"`. 3. Use the result to narrow the next file reads, tests, or edits instead of expanding into broad unguided repo search. 4. Do not use this as a substitute for the i...

- CLI-first is non-negotiable for both Codex and Claude Code. Remove all hand-authoring for places where Odylith CLI should be doing the heavy-lifting. When an Odylith CLI command exists for an operation, you must call the CLI command and you must not hand-edit governed files the CLI owns. Hand-authoring governed truth where a CLI exists is a hard policy violation, not a stylistic preference. The authoritative policy, CLI surface enumeration, allowed hand-edit surfaces, and failure-mode handling

Use this skill only when the user explicitly invokes `$odylith-registry-sync-specs` or asks to sync mapped Compass requirement evidence into component living specs. 1. Run `./.odylith/bin/odylith governance sync-component-spec-requirements --repo-root .`. 2. Report which components or forensics records updated. 3. If nothing changed, say that plainly instead of implying hidden work.

Use this skill only when the user explicitly invokes `$odylith-registry-validate` or asks to validate Registry component inventory contracts. 1. Run `./.odylith/bin/odylith validate component-registry --repo-root .`. 2. Report the contract result, component counts, and any critical policy finding. 3. Keep follow-up bounded to the surfaced Registry contract issue.

- CLI-first is non-negotiable for both Codex and Claude Code. Remove all hand-authoring for places where Odylith CLI should be doing the heavy-lifting. When an Odylith CLI command exists for an operation, you must call the CLI command and you must not hand-edit governed files the CLI owns. Hand-authoring governed truth where a CLI exists is a hard policy violation, not a stylistic preference. The authoritative policy, CLI surface enumeration, allowed hand-edit surfaces, and failure-mode handling

- CLI-first is non-negotiable for both Codex and Claude Code. Remove all hand-authoring for places where Odylith CLI should be doing the heavy-lifting. When an Odylith CLI command exists for an operation, you must call the CLI command and you must not hand-edit governed files the CLI owns. Hand-authoring governed truth where a CLI exists is a hard policy violation, not a stylistic preference. The authoritative policy, CLI surface enumeration, allowed hand-edit surfaces, and failure-mode handling

- CLI-first is non-negotiable for both Codex and Claude Code. Remove all hand-authoring for places where Odylith CLI should be doing the heavy-lifting. When an Odylith CLI command exists for an operation, you must call the CLI command and you must not hand-edit governed files the CLI owns. Hand-authoring governed truth where a CLI exists is a hard policy violation, not a stylistic preference. The authoritative policy, CLI surface enumeration, allowed hand-edit surfaces, and failure-mode handling

Use this skill only when the user explicitly invokes `$odylith-session-brief` or asks for a concise session brief grounded in current Odylith state. 1. Run `./.odylith/bin/odylith session-brief --repo-root .`. 2. Use current workstream, Compass, Casebook, and validation evidence that already exists. 3. Summarize what moved, what is blocked, and the next concrete move. 4. Prefer grounded evidence over narration flourishes.

- CLI-first is non-negotiable for both Codex and Claude Code. Remove all hand-authoring for places where Odylith CLI should be doing the heavy-lifting. When an Odylith CLI command exists for an operation, you must call the CLI command and you must not hand-edit governed files the CLI owns. Hand-authoring governed truth where a CLI exists is a hard policy violation, not a stylistic preference. The authoritative policy, CLI surface enumeration, allowed hand-edit surfaces, and failure-mode handling

Use this skill when the operator says "show me what you can do", "what can Odylith do", "what can you do for this repo", or any similar first-time exploration request. Works identically on Claude Code and Codex. Do not use this skill for `Odylith, help`. That request should route directly to the CLI help output and print stdout only. This is a first-match route lock. If you have not run a show command and captured stdout, do not answer. Never replace `odylith show` stdout with a hand-written ...

Use this skill only when the user explicitly invokes `$odylith-start` or directly asks to run the repo-local Odylith startup contract. 1. Run `./.odylith/bin/odylith start --repo-root .` for substantive work. Do not run `odylith context`, `odylith query`, `git status`, or broad repo search in parallel with this step; let startup finish first so the host transcript reflects the real grounding order. 2. If startup cannot narrow the slice but the user already named a workstream, bug, component, ...

- CLI-first is non-negotiable for both Codex and Claude Code. Remove all hand-authoring for places where Odylith CLI should be doing the heavy-lifting. When an Odylith CLI command exists for an operation, you must call the CLI command and you must not hand-edit governed files the CLI owns. Hand-authoring governed truth where a CLI exists is a hard policy violation, not a stylistic preference. The authoritative policy, CLI surface enumeration, allowed hand-edit surfaces, and failure-mode handling

- CLI-first is non-negotiable for both Codex and Claude Code. Remove all hand-authoring for places where Odylith CLI should be doing the heavy-lifting. When an Odylith CLI command exists for an operation, you must call the CLI command and you must not hand-edit governed files the CLI owns. Hand-authoring governed truth where a CLI exists is a hard policy violation, not a stylistic preference. The authoritative policy, CLI surface enumeration, allowed hand-edit surfaces, and failure-mode handling

Use this skill only when the user explicitly invokes `$odylith-sync` or asks to refresh governed Odylith surfaces for the current changed slice. 1. Identify the changed source-of-truth paths under `odylith/radar/source/`, `odylith/technical-plans/`, `odylith/casebook/bugs/`, `odylith/registry/source/`, `odylith/atlas/source/`, or other governed Odylith paths. 2. Run `./.odylith/bin/odylith sync --repo-root . --impact-mode selective <changed_paths...>`. 3. If the change only needs a narrow rer...

Use this skill only when the user explicitly invokes `$odylith-version` or asks to inspect the pinned, active, and locally available Odylith versions. 1. Run `./.odylith/bin/odylith version --repo-root .`. 2. Report the active pinned runtime posture plainly. 3. When relevant, distinguish the active target release from the latest shipped release instead of collapsing them together.

Use when concrete Odylith failure evidence needs a Casebook bug with grounded repro details.

Use when an Odylith Casebook bug create or update needs prerequisite checks.

Use when a slice shows duplicate helpers, fake modularization, oversized-file pressure, or AI-shaped code slop that needs explicit cleanup discipline.

Use when a bounded execution note needs to be appended into Compass.

Use when Compass state needs a refresh and the current pass must settle.

Use after startup, never in parallel with startup, when a known Odylith anchor needs local context.

Use when Odylith Discipline pressure behavior, zero-credit hard laws, host/lane parity, or benchmark-proved learning-spine contracts need validation.

Use when the current Odylith install needs verification or an approved repair.

Use when a consumer repo needs proposal-first backlog, Registry, and Atlas drafts from new project intent before source exists.

Use when guidance behavior pressure cases or high-risk agent guidance contracts need deterministic validation.

Use when concrete anchors already exist and the local Odylith projection store needs search.

Use when current Odylith state needs a concise session brief.

Use when the operator asks what Odylith can do for a repo, requests an advisory repo demo, or asks for the clean scenario-aware show-me output.

Use first, before context/search fan out, when a task needs repo-local Odylith startup grounding.

Use when changed files need governed Odylith surfaces refreshed.

Use when pinned, active, and locally available Odylith versions need inspection.

Refresh Atlas diagrams from change-watch metadata.

Render Atlas from the Mermaid catalog.

Create grounded Radar backlog workstreams.

Validate Radar backlog and plan linkage contracts.

Capture a new Odylith Casebook bug from concrete failure evidence and grounded repro details.

Investigate an Odylith bug record, gather evidence, and connect it to the right governed surfaces.