Individual skill

skills-map

Use at the START of any task, or whenever you are unsure which lich-skill applies. The router for this collection — it maps every lich-skill to the phase of work it belongs to (Decide → Spec → Plan → Build → Debug → Fan-out → Research → Media → Analyze) and walks a decision tree to pick the right one. Prevents the two failure modes of a skill collection: forgetting a skill exists, and reaching for the wrong skill at the wrong phase. Triggered by "/skills-map", "which skill should I use", "what skills do I have", or any moment of skill-selection doubt.

skills/skills-map/SKILL.md

Read pinned source

Source commit ebbc355b6db90b445649efba9a58022d049c9ee2

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 232
Repository last updated: Jun 9, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

gemini-cli-extension Repository topic
research Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

README.mddoc · 1,440 bytes
SKILL.mdcore · 8,777 bytes
SKILL.mdcore · 8,777 bytes

Read excerpt


# Skills Map — the router for lich-skills

> Most skills help you *do* the work. This one helps you pick *which* skill does the work.

A skill collection has a discovery problem: the skills only fire if the agent
remembers they exist and reaches for the right one at the right moment. Left to
chance, the agent forgets `go-no-go` and starts building, or hand-rolls a debug
crawl instead of running `debug-hypothesis`. `skills-map` is the index + decision
tree that closes that gap.

It does three things:

1. **Identify** the phase of work the current task is in.
2. **Route** to the matching skill via the decision tree.