Lintel on GitHub Copilot. Generated from skills/skill-router/SKILL.md; edit the canonical file, then run
li-copilot init.
- Resource root:
../../.. from this skill's base directory (the Lintel source with bin/,
lib/, skills/). Write plans, state and evidence into the working repository's .claude/
tree, never into the resource root.
- Skill-relative paths: this skill's own
scripts/, references/ and data/ folders (and a
<base> that the workflow defines as its own directory) mean
../../../skills/skill-router/ in the Lintel source, not this generated folder.
${LINTEL_SKILLS_DIR:-skills} means the skills root, ../../../skills. A bin/li-run step
runs in the working repository, so use $LINTEL_SKILLS_DIR/skill-router/ there.
- Shell steps: run Bash snippets with Bash (Git for Windows'
bash.exe on Windows, never
System32\bash.exe). Save a snippet to a temporary .sh file and run
bash "<resource root>/bin/li-run" <file>; it prepares LINTEL_SOURCE_ROOT, LINTEL_REPO_ROOT
and the profile context.
- Tools: Read=
view, Write=create, Edit=edit, Bash=bash/powershell, Grep=grep,
Glob=glob, AskUserQuestion=ask_user, TodoWrite=the plan checklist, Task or a named role=task
with that custom agent, WebFetch=web_fetch.
- Other Lintel workflows are native skills: invoke
/li-<name> rather than reading their
files. Named roles such as CodeReviewer are custom agents.
Skill router
Retained front door for an operator who does not know the method's name. Follow
catalog's intent narrowing in full, including
literal queries, at most three selected-body reads, source/parser failures,
privacy, aliases and the actual host's discovery and permission boundaries.
Catalog owns selection; this entry adds no routing algorithm or model call.
If the request already names a method, use that method rather than adding a routing
turn. For agents, use the same catalog metadata and an actual authorized delegation
binding, not a role file as proof of availability or independent review.
Return fit, alternatives and limitations. A recommendation does not execute work,
change installation, or waive SENSE's pack-configured high-risk confirmation.
1---2name: li-skill-router3description: Use to find a relevant Lintel method from free-text intent through catalog's metadata-first shortlist.4metadata:5 source: https://skillmd.com/skills/jokerman89/li-skill-router6---78> **Lintel on GitHub Copilot.** Generated from `skills/skill-router/SKILL.md`; edit the canonical file, then run9> `li-copilot init`.10> - **Resource root:** `../../..` from this skill's base directory (the Lintel source with `bin/`,11> `lib/`, `skills/`). Write plans, state and evidence into the working repository's `.claude/`12> tree, never into the resource root.13> - **Skill-relative paths:** this skill's own `scripts/`, `references/` and `data/` folders (and a14> `<base>` that the workflow defines as its own directory) mean15> `../../../skills/skill-router/` in the Lintel source, not this generated folder.16> `${LINTEL_SKILLS_DIR:-skills}` means the skills root, `../../../skills`. A `bin/li-run` step17> runs in the working repository, so use `$LINTEL_SKILLS_DIR/skill-router/` there.18> - **Shell steps:** run Bash snippets with Bash (Git for Windows' `bash.exe` on Windows, never19> `System32\bash.exe`). Save a snippet to a temporary `.sh` file and run20> `bash "<resource root>/bin/li-run" <file>`; it prepares `LINTEL_SOURCE_ROOT`, `LINTEL_REPO_ROOT`21> and the profile context.22> - **Tools:** Read=`view`, Write=`create`, Edit=`edit`, Bash=`bash`/`powershell`, Grep=`grep`,23> Glob=`glob`, AskUserQuestion=`ask_user`, TodoWrite=the plan checklist, Task or a named role=`task`24> with that custom agent, WebFetch=`web_fetch`.25> - **Other Lintel workflows** are native skills: invoke `/li-<name>` rather than reading their26> files. Named roles such as `CodeReviewer` are custom agents.2728# Skill router2930Retained front door for an operator who does not know the method's name. Follow31catalog's [intent narrowing](../../../skills/catalog/references/intent.md) in full, including32literal queries, at most three selected-body reads, source/parser failures,33privacy, aliases and the actual host's discovery and permission boundaries.34Catalog owns selection; this entry adds no routing algorithm or model call.3536If the request already names a method, use that method rather than adding a routing37turn. For agents, use the same catalog metadata and an actual authorized delegation38binding, not a role file as proof of availability or independent review.3940Return fit, alternatives and limitations. A recommendation does not execute work,41change installation, or waive SENSE's pack-configured high-risk confirmation.