map
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.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 1a6fc74a1c5befe4… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Map
You know something needs doing; you do not know which skill owns it. Find the job below, call the Skill tool with the routed skill. The map routes and explains nothing twice — each routed skill owns its own doctrine.
The delivery loop
| You are here | Skill |
|---|---|
| External work arrived (issues, PRs, reports) | harbor |
| A non-engineer handed you a chat log as requirements | intent |
| The destination is foggy — the first three decisions cannot be stated yet | ask-navigator |
| Vague idea; questions must come before anything else | deep-interview |
| Requirements are clear; you need a plan | plan (multi-perspective consensus: ralplan) |
| Approved plan; decompose and ship end to end with human checkpoints | launch |
| One task; persistence until verified complete | ralph |
| Hands-off idea-to-code | autopilot |
| Work needs coordinated parallel workers | team |
| One approved task carried through verified code | execute |
| A design question prose cannot settle | loft |
| Finished work needs judgment | review |
| Something claims to be done | verify |
| Work is landing as a PR | pr |
| The run taught the environment something | refit |
On-ramps (off the main loop)
| Job | Skill |
|---|---|
| A bug needs its root cause | debug; competing-hypothesis tracing: trace |
| Tests should drive the implementation | tdd |
| The codebase is getting harder to change | architecture-survey |
| AI-generated slop needs cleanup | ai-slop-cleaner |
| An open question needs grounded answers | research; external docs: external-context |
| Knowledge should compound across sessions | wiki; durable project memory: remember |
| A recurring autonomous improvement loop | self-improve; durable goal ledger: ultragoal |
| Visual work needs verdicts or diagrams | visual-verdict; diagram |
Utilities
| Job | Skill |
|---|---|
| Install, diagnose, configure | omc-setup; omc-doctor; configure-notifications |
| Manage skills themselves | skill (local); skillify (extract from session) |
| Inspect orchestration state | trace (also the tracing lane); graph (DAG runtime) |
| Cancel a mode | cancel |
Rules
- The map routes; it never executes. Every row resolves to one Skill-tool call — make it, then follow that skill's own doctrine.
- When two rows both fit, the delivery loop above is the tiebreak: earlier legs come first.
- Phase boundaries (continue / re-enter from disk / hand off / compact) are defined in
launch's Context hygiene — the map does not restate them. - A job matching no row is itself information: say so plainly rather than picking the nearest-sounding skill.
Files
1- SKILL.md
24642eaa0a2.9 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from Yeachan-Heo/oh-my-claudecode8
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 se
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Periodic architecture survey — walks the module graph and reports ranked deepening candidates (shallow modules, hypothetical seams, logic behind the wrong seam). Survey, not rescue: it finds candidates and hands them to the captain; it never refactors on its own.
Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding,
Full autonomous execution from idea to working code
Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior
Cancel any active OMC mode (autopilot, ralph, ultragoal, swarm, ultrapilot, pipeline, team) and clean up retired legacy state
Related knowledge skillsscan passed
Clear the freeze boundary set by /freeze, allowing edits to all directories again. (gstack)
PostHog integration for SvelteKit applications
Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.