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...
Scanned 9/12/2026
Install to Claude Code
Skills Directorynpx -y skills add odylith/odylith --skill odylith-sync --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Odylith Sync?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/odylith-odylith-sync-bdda9535)More formats (shields.io, HTML) on the badges page.
# Odylith Sync
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 rerender after the sync decision, you may
use the owned-surface command for the touched slice:
`./.odylith/bin/odylith radar refresh --repo-root .`,
`./.odylith/bin/odylith registry refresh --repo-root .`,
`./.odylith/bin/odylith casebook validate --repo-root .`,
`./.odylith/bin/odylith casebook refresh --repo-root .`,
`./.odylith/bin/odylith atlas refresh --repo-root . --atlas-sync`,
`./.odylith/bin/odylith compass refresh --repo-root .`, or
`./.odylith/bin/odylith compass deep-refresh --repo-root .` when the
rerender also needs standup-brief settlement.
4. Report what refreshed, what still needs manual follow-through, and whether
consumer-safe generated bundle mirrors also changed.
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!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling
