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.

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

88/100

Grade

A

Excellent

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

95

Quality

86

Clarity

92

Completeness

78

Summary

This skill is a routing and discovery map for a multi-skill agent orchestration system. It provides a structured decision tree that directs users to the correct specialized skill based on their job type, organized into a delivery loop, on-ramps, and utilities. The map never executes work itself — it only routes and explains the yard's skill inventory.

Detected Capabilities

skill routingdocumentation referencedecision tree navigationorchestration guidance

Trigger Keywords

Phrases that agents use to match this skill to user intent.

route to the right skillfind which skill owns thisskill discoveryorchestration routingwhat should i do next

Use Cases

Find the right skill for a vague requirement
Route incoming work (issues, PRs, reports) to the appropriate handler
Understand the skill ecosystem and orchestration architecture
Resolve ambiguity when multiple skills could apply (using delivery-loop precedence)
Discover specialized skills for specific problem domains (debugging, testing, architecture, research)

Quality Notes

Clear hierarchical organization with three distinct sections (delivery loop, on-ramps, utilities) that maps problem types to solutions
Explicit non-execution doctrine: 'The map routes; it never executes' — eliminates ambiguity about this skill's scope
Concise tiebreaker rule provided: delivery-loop precedence handles ambiguous cases
References many other skills but does not burden the map with their documentation — each routed skill owns its own doctrine
Practical trigger phrase: 'something needs doing but not which of the shipped skills owns it'
The skill assumes familiarity with the broader agent framework (references context hygiene in launch, DAG runtime in graph, etc.) — appropriate for an internal routing skill
Markdown table format is clean and scannable
Edge case handling: explicitly addresses 'A job matching no row' case by instructing to say so plainly

Model: claude-haiku-4-5-20251001Analyzed: Oct 2, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

map

Map