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, ...
Scanned 9/12/2026
Install to Claude Code
Skills Directorynpx -y skills add odylith/odylith --skill odylith-start --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Odylith Start?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/odylith-odylith-start-07104a2f)More formats (shields.io, HTML) on the badges page.
# Odylith Start
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, or path, follow with
`./.odylith/bin/odylith context --repo-root . <ref>`.
3. Keep the next repo reads bounded to the resolved slice instead of widening
into broad repo search immediately.
4. Summarize only the active slice and the next concrete move; do not narrate
control-plane internals.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
