Skip to content
Skills Library
Management & product · Planning

map

/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.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Arguments

/map [what are you trying to do]
Original author 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.

How it works

  1. The delivery loop
  2. On-ramps (off the main loop)
  3. Utilities
  4. Rules
Original SKILL.md headings · 55 lines, 511 words
SKILL.md preview
---
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` |
| 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` |
| 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` |

## 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.

Versions

RepositoryScoreLicence
This page · yeachan-heo/oh-my-claudecode90MIT
milansolutionsai-ops/claude-code-map-skill100MIT
acaprino/alfio-claude-plugins100MIT
shenxingy/clade100MIT
DaBaoAgent/Auto-Video100MIT
bgmacris/quimera-ai100MIT
fabiozagaria/spring-security-advisor100MIT
htlin222/dotfiles100MIT
roma8ok/getmapstack100MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 9ad12aa58056 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100yard
    Keep the branch's Yard Log while planning, building, fixing and reviewing a change on a git branch: its stages and tasks, the person's questions and approvals, and what each step produced and decided. Use for any work on a git branch, even where the person does not name Yard:…
  • 100yard
    Keep the branch's Yard Log while planning, building, fixing and reviewing a change on a git branch: its stages and tasks, the person's questions and approvals, and what each step produced and decided. Use for any work on a git branch, even where the person does not name Yard:…
  • 100yt-guide
    Skill router and usage guide for all YouTube Skillbox skills. Use when the user asks "which skill should I use", "how do I use this", "what skills are available", or any general request that needs the right skill(s) selected. Read this first when unsure which skill to run.
  • 100using-the-enso-method
    Where to start and what comes next in the Enso Method — which skill runs at each stage, in what order, and where the user's review is recommended. Use when the user asks to use the Enso Method, asks "where do I start" or "what's next", or hands over requirements, an idea or a…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.