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

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplary router skill: lean lookup tables with concrete skill names, executable routing rules covering tiebreaks, manual routes, and no-match cases, and clean section organization with nothing that belongs in a separate file. All dimensions land on the top anchors.

DimensionReasoningScore

Conciseness

The body is a two-sentence contract plus terse job-to-skill table rows with zero explanation of concepts Claude already knows; "explains nothing twice — each routed skill owns its own doctrine" is itself an anti-duplication rule, so every token earns its place.

5 / 5

Actionability

Every row yields an exact skill name, and the Rules make execution concrete: "Each ordinary row resolves to one Skill-tool call — make it", "show the user its slash command; do not try to call the Skill tool", with the manual route even giving the literal command (/oh-my-claudecode:session-flow).

5 / 5

Workflow Clarity

As a single-decision routing skill, the one action (find the job, make the Skill call) is unambiguous, and all edge cases are explicitly handled: the delivery-loop tiebreak for overlapping rows, the manual-route rule, and the no-match rule ("say so plainly rather than picking the nearest-sounding skill"). No destructive or batch operations apply, so the validation cap is not triggered.

5 / 5

Progressive Disclosure

With no bundle files, the entire body is appropriately inline: three clearly-labeled lookup tables plus Rules, with the one-level-deep references being the routed skills themselves (signaled by Skill-tool calls) — the stated rule that each routed skill owns its own doctrine confirms no detail content is mis-placed inline.

5 / 5

Total

20

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly and explicitly states both what the skill does (routes jobs to owning skills, never executes) and when to use it (needing something done but not knowing which skill owns it). Minor deductions for insider jargon ("the yard's") and lack of trigger-term variations.

DimensionReasoningScore

Specificity

"which skill owns which job, in delivery-loop order" and "the map routes, it never executes" state concrete, precisely scoped actions in third person, but the description names only the single routing action rather than several specific actions.

4 / 5

Completeness

Explicitly answers both: the what ("which skill owns which job, in delivery-loop order... the map routes, it never executes") and the when ("Use when something needs doing but not which of the shipped skills owns it") with a concrete trigger state.

5 / 5

Trigger Term Quality

Natural trigger phrases like "something needs doing" and "which of the shipped skills owns it" are present and capture the routing-uncertainty state well; a few natural variations (e.g. "which skill should I use") are missing and "the yard's" is insider jargon.

4 / 5

Distinctiveness Conflict Risk

"the map routes, it never executes" explicitly demarcates it from every executor skill, and its trigger (uncertainty about which skill owns a job) does not overlap with any task-skill trigger, minimizing conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

Yeachan-Heo/oh-my-claudecode

Path

skills/map/SKILL.md

Reviewed

Table of Contents

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.