Skip to main content
skill CX Codex

map · yeachan-heo — Claude Code skill: task routing and installation

This Claude Code skill routes a task to the matching skill in the collection. It maps work to a delivery stage or a specific workflow, but does not carry out the task itself.

MIT 160 installs ★ 40,997 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Yeachan-Heo/oh-my-claudecode --skill map -a claude-code
Open on GitHub

What map does

map matches a request to a skill: plan handles planning, verify checks finished work, and debug investigates bugs. Its routes cover the delivery loop, standalone jobs, and utilities. When several entries fit, the earlier delivery-loop stage takes priority.

For a standard route, map invokes the selected skill through the Skill tool. A manual route instead gives the slash command, since map must not call the Skill tool for it. For example, session-flow is started manually with /oh-my-claudecode:session-flow; model invocation is disabled for that route.

What it helps with

  • find the right skill when its name is unknown
  • place a task at the right point in the delivery loop
  • locate a route for debugging or code review
  • get the slash command for a manually started skill

Example prompts for the agent

  • Which skill should I use to make a work plan?
  • Route this finished code to the right review skill.
  • Find a skill for debugging a bug with an unknown cause.

How to install map

1Skills CLI (Vercel)

npx skills add Yeachan-Heo/oh-my-claudecode --skill map -a claude-code

2Manually: put the files in place

~/.claude/skills/map/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/map/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about map

How do I install map in Claude Code?

Run npx skills add Yeachan-Heo/oh-my-claudecode --skill map -a claude-code.

What does map do?

It matches a task to a skill in the collection and routes the request there. map does not perform the work itself.

Does map run the skill it selects?

For standard routes, map calls the selected skill through the Skill tool. For manual routes, it displays a slash command instead.

Source text

SKILL.md · MIT
---
name: map
description: 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.
argument-hint: "[what are you trying to do]"
disable-model-invocation: true
---

# Map

You know something needs doing; you do not know which skill owns it. Find the job below and follow its route. Most routes call the Skill tool; a route marked manual gives you the slash command to invoke yourself because model invocation is disabled. 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` |
| One attempt risks locking in the wrong shape | `arena` |
| Code crosses a function boundary; designs should compete first | `architect` |
| Finished work needs attack before it ships | `interrogate` |
| 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` |
| An open PR needs driving to merge-ready | `babysit` |
| 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` |
| The question is why the code is this way | `why` |
| A subsystem needs explaining | `how`; as a lesson: `teach` |
| A risky change needs its blast radius mapped | `blast-radius` |
| The same agent mistake keeps recurring | `correct` |
| Long autonomous work needs an audit trail | `show-me-your-work` |
| No bundled skill fits the task shape | `figure-it-out` (designs one, validated against anchors) |
| A property tests cannot reach needs formal proof | `create-formal-verification-skill`; drifted spec: `maintain-formal-verification-skill` |
| A flow or protocol bug shows up as a path through states | `statechart` |
| The repo needs its own verification commands recorded | `create-verification-skill`; drifted commands: `maintain-verification-skill` |
| Roles should run on chosen models | `models` |
| Tests should drive the implementation | `tdd` |
| The codebase is getting harder to change | `architecture-survey` |
| AI-generated slop needs cleanup | `ai-slop-cleaner` |
| A measured number needs vetting before it is reported or acted on | `benchmark-checklist` |
| A delegated brief needs cross-cutting judgment guardrails | `principles` |
| 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` |
| A session needs reorientation across its pivots and outcomes | `session-flow` — run `/oh-my-claudecode:session-flow` manually |
| 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` |
| CI is red on a PR you own | `fix-ci`; review threads: `get-pr-comments`; conflicts: `fix-merge-conflicts` |
| The user missed the session | `ketchup`; as a subtitled video: `ketchup-video`; after a break or crash: `recall` |
| A brief is vague | `sharpen`; playback before starting: `in-your-own-words` |
| A reply was too dense | `bro` |
| Shipping prose needs the standard | `technical-writing`; TS type discipline: `typescript-best-practices` |
| The period's authored work needs summarizing | `what-did-i-get-done` |
| A queue must land as one stacked PR chain | `stacked-delivery`; watch state: `babysit` |
| A measured target needs climbing over multiple rounds | `hillclimb` |
| A long session's lessons should be banked as skill edits | `reflect`; extraction: `skillify` |
| A cross-project personal behavior profile is wanted | `personal-mode`; single facts: `remember` |

## Rules

- The map routes; it never executes. Each ordinary row resolves to one Skill-tool call — make it, then follow that skill's doctrine. For a manual-only route, show the user its slash command; do not try to call the Skill tool.
- 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.

© Yeachan-Heo · MIT · Yeachan-Heo/oh-my-claudecode

Similar skills

SKILL.md skills catalog →

map by other authors comes first.

map SethGammon map generates a JSON index of a repository's files, exports, imports and dependency graph so an agent can locate relevant code without extra Glob or Grep calls. CX Codex +1 ★ 937repo stars firecrawl-map firecrawl firecrawl-map is a Claude Code skill that finds a site's URLs and filters them by search terms. It runs when a page address or site structure needs to be found. CX Codex +1 80,900installs tavily-map tavily-ai tavily-map — a skill that has the agent walk a site and hand back the list of addresses, leaving page text alone. Useful when you know the domain but not the page. CX Codex +1 17,600installs developer-journey-map Samuel Berthe developer-journey-map maps the developer journey across stages for a single audience segment and points out the main leak. Useful when developers try your product but never reach production. CX Codex +1 13,400installs context-map official github The context-map skill makes the agent map every file, test and dependency tied to a task before it touches code. Handy on a codebase you don't know yet. CX Codex +1 9,641installs security-ownership-map official openai security-ownership-map builds a people-to-file map from git history, computes bus factor, and flags sensitive code with too few active owners. CX Codex +1 4,200installs customer-journey-map phuryn Builds an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Useful for experience research and onboarding work. CX Codex +1 3,300installs

From the same set48

The whole set →
diagram This skill picks a compact visual for code structure, from a call tree to a Mermaid diagram. Use it when prose makes relationships hard to follow. CX Codex +1 194installs ask-navigator ask-navigator — a skill that turns an unclear effort into a map of decision tickets on the repo's issue tracker. It works the frontier one ticket per session until the route clears, then hands decisions over without building anything. CX Codex +1 191installs loft loft resolves deadlocked design and logic questions by building disposable runnable prototypes that never merge into main. CX Codex +1 189installs intent Turns a pasted chat or problem report into a reviewed intent.md. It gives /launch a decision brief instead of code. CX Codex +1 187installs pr pr — a Claude Code skill that drafts pull request descriptions from the session paper trail. It compiles verified test evidence, visual summaries, and rollback risks into a markdown body. CX Codex +1 161installs refit refit is a Claude Code skill that reviews OMC runtime traces to find agent workflow friction and propose targeted fixes to checks, configs, and instructions. CX Codex +1 158installs session-flow session-flow — a skill for Claude Code rebuilds the session’s goal, pivots, outcomes, current stage, and open decisions from its history. It starts after a session switch or context compaction. CX Codex +1 118installs research The research skill investigates open questions in a codebase and its docs, then ties findings to sources. Use it when an unresolved fact affects your next step. CX Codex +1 1installs

Project sponsors

Companies that keep this analytics open