Oh My ClaudeCode skills

Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior

Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before reference, one meaning in one home, no restating what the environment already says. Mandatory at drydock seed generation and the launch C5 sediment pass; opt-in for any other agent-facing doc edit. The companion of minimal-code-discipline: that one disciplines code, this one disciplines papers.

Configure notification integrations (Telegram, Discord, Slack) via natural language

Parallel execution engine for high-throughput task completion

Evaluate finished work for defects, risk, and simplification before it ships

Invoke parallel document-specialist agents for external web searches and documentation lookup

Turn a repeatable workflow from the current session into a reusable OMC skill draft

CLI-team runtime for claude, codex, gemini, antigravity, grok, or cursor workers in tmux panes when you need process-based parallel execution

Deep codebase initialization with hierarchical AGENTS.md documentation

Configure popular MCP servers for enhanced agent capabilities

Writing-time discipline for the prose an agent speaks to a human (replies, reports, pointers): a protected core never rewritten (code, commands, paths, errors, negators, numbers), filler dies, no narration, auto-clarity where terse misleads

OMC agent catalog, available tools, team pipeline routing, commit protocol, and skills registry. Auto-loads when delegating to agents, using OMC tools, orchestrating teams, making commits, or invoking skills.

Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASE_RULE.md, then guides the release

The yard's skill map — which skill owns which job, in delivery-loop order. Use when something needs doing but not which of the shipped skills owns it; the map routes, it never executes.

Loft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the artifact never docks. Use when a design question stalls in words, when a navigator map carries a loft ticket, or when a spec discussion reaches "we would have to see it".

Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs

Structured visual QA verdict for screenshot-to-reference comparisons

N coordinated agents on shared task list using Claude Code implicit agent teams

Agentic memory system for writers - track characters, relationships, scenes, and themes

Claude-Codex-Gemini tri-model orchestration via /ask codex + /ask antigravity (or gemini), then Claude synthesizes results

YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away

Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode

Carry an approved task through to working, verified code

Deterministic orchestration graph runtime - declarative DAG pipelines with journal-based crash recovery