| name | skill-dispatcher |
| description | Discover and route to project skills under .cursor/skills. Use when matching tasks to skills or listing available skills. |
Skill Dispatcher
Official Agent Skills entry point for this project.
Canonical layout
| Layer | Path | Role |
|---|
| Cursor discovers | .cursor/skills/<name>/SKILL.md | Required name + description; optional paths, scripts/, references/ |
| This dispatcher | .cursor/skills/skill-dispatcher/ | Match tasks to skill packages |
| Registry index | .cursor/features/skills/skills/registry.json | Metadata for Master/skills-loader; not used for Cursor auto-discovery |
Always prefer .cursor/skills/*/SKILL.md. For full workflows, read references/full-guide.md inside the matched skill folder.
When to use
- User asks what skills exist or which skill fits a task
- Multiple domains apply (e.g. API + security + tests)
- Routing
/master skill:<name> or explicit skill invocation
Discovery (official)
find .cursor/skills -name SKILL.md
scripts/list-skills.sh
Parse each SKILL.md frontmatter: name, description, optional paths.
Matching workflow
- Extract intent and tech context from the user message.
- Score skills by
description relevance and optional paths vs open files.
- Pick the best match; load that skill's
SKILL.md, then references/full-guide.md if needed.
- Run
scripts/ in that skill directory with paths relative to the skill root.
Registry index (optional)
registry.json maps registry keys to package and guide paths under .cursor/skills/. See references/operator-manual.md for matching tables.
Related
- Package root:
.cursor/skills/skill-dispatcher/
- Full guide:
references/full-guide.md
- Registry metadata:
.cursor/features/skills/skills/registry.json