CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 hereSkill
External work arrived (issues, PRs, reports)harbor
A non-engineer handed you a chat log as requirementsintent
The destination is foggy — the first three decisions cannot be stated yetask-navigator
Vague idea; questions must come before anything elsedeep-interview
Requirements are clear; you need a planplan (multi-perspective consensus: ralplan)
Approved plan; decompose and ship end to end with human checkpointslaunch
One task; persistence until verified completeralph
Hands-off idea-to-codeautopilot
Work needs coordinated parallel workersteam
One approved task carried through verified codeexecute
One attempt risks locking in the wrong shapearena
Code crosses a function boundary; designs should compete firstarchitect
Finished work needs attack before it shipsinterrogate
A design question prose cannot settleloft
Finished work needs judgmentreview
Something claims to be doneverify
Work is landing as a PRpr
An open PR needs driving to merge-readybabysit
The run taught the environment somethingrefit

On-ramps (off the main loop)

JobSkill
A bug needs its root causedebug; competing-hypothesis tracing: trace
The question is why the code is this waywhy
A subsystem needs explaininghow; as a lesson: teach
A risky change needs its blast radius mappedblast-radius
The same agent mistake keeps recurringcorrect
Long autonomous work needs an audit trailshow-me-your-work
No bundled skill fits the task shapefigure-it-out (designs one, validated against anchors)
A property tests cannot reach needs formal proofcreate-formal-verification-skill; drifted spec: maintain-formal-verification-skill
A flow or protocol bug shows up as a path through statesstatechart
The repo needs its own verification commands recordedcreate-verification-skill; drifted commands: maintain-verification-skill
Roles should run on chosen modelsmodels
Tests should drive the implementationtdd
The codebase is getting harder to changearchitecture-survey
AI-generated slop needs cleanupai-slop-cleaner
A measured number needs vetting before it is reported or acted onbenchmark-checklist
A delegated brief needs cross-cutting judgment guardrailsprinciples
An open question needs grounded answersresearch; external docs: external-context
Knowledge should compound across sessionswiki; durable project memory: remember
A recurring autonomous improvement loopself-improve; durable goal ledger: ultragoal
A session needs reorientation across its pivots and outcomessession-flow — run /oh-my-claudecode:session-flow manually
Visual work needs verdicts or diagramsvisual-verdict; diagram

Utilities

JobSkill
Install, diagnose, configureomc-setup; omc-doctor; configure-notifications
Manage skills themselvesskill (local); skillify (extract from session)
Inspect orchestration statetrace (also the tracing lane); graph (DAG runtime)
Cancel a modecancel
CI is red on a PR you ownfix-ci; review threads: get-pr-comments; conflicts: fix-merge-conflicts
The user missed the sessionketchup; as a subtitled video: ketchup-video; after a break or crash: recall
A brief is vaguesharpen; playback before starting: in-your-own-words
A reply was too densebro
Shipping prose needs the standardtechnical-writing; TS type discipline: typescript-best-practices
The period's authored work needs summarizingwhat-did-i-get-done
A queue must land as one stacked PR chainstacked-delivery; watch state: babysit
A measured target needs climbing over multiple roundshillclimb
A long session's lessons should be banked as skill editsreflect; extraction: skillify
A cross-project personal behavior profile is wantedpersonal-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.
Repository

Yeachan-Heo/oh-my-claudecode

Path

skills/map/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.