Lintel on GitHub Copilot. Generated from skills/orientator/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/orientator/ 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/orientator/ 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.
Orientator
Retained /li-orientator <prompt> front door for entry-time guidance. For a supplied
intent, follow catalog's intent narrowing, not a
second keyword table or selection method. Return the recommended method, rationale,
alternatives and observed limitations without running it.
Skip this discovery turn when the operator already selected a workflow or supplied
--mode / --from. Mid-cycle work keeps its selected map and phase; do not infer a
new task from a state-file tail.
SENSE owns navigation control
SENSE Step 0d
calls lib/orientator-routing.sh directly, not this public skill. That existing
method verifies the profile, reads the pack's navigation, obtains a mechanical
recommendation and records its actual decision through audit_log. The library and
its navigation reference remain compatible.
Keep these boundaries when proceeding from guidance to an authorized workflow:
- SENSE's high-risk workflow always requires explicit confirmation, including when
auto-mode is eligible. Low confidence needs judgment or an unresolved-decision
question; it is not evidence of another model call.
- Configured defaults and extension namespaces remain pack-owned. A missing or drifted
required profile blocks dependent navigation; never substitute neutral success.
- Explicit operator choices override a recommendation, not host permissions or
mandatory controls. Verify the selected native entrypoint before execution.
- The compatibility escalation hook performs no model request. Do not report it as
executed escalation, token consumption or measured routing success.
This wrapper writes no audit or state. SENSE remains the decision producer when it
actually runs; discovery alone must not fabricate an orientation event or execution.
1---2name: li-orientator3description: Use for entry-time method guidance through catalog, preserving SENSE's existing pack navigation and high-risk confirmation.4metadata:5 source: https://skillmd.com/skills/jokerman89/li-orientator6---78> **Lintel on GitHub Copilot.** Generated from `skills/orientator/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/orientator/` 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/orientator/` 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# Orientator2930Retained `/li-orientator <prompt>` front door for entry-time guidance. For a supplied31intent, follow catalog's [intent narrowing](../../../skills/catalog/references/intent.md), not a32second keyword table or selection method. Return the recommended method, rationale,33alternatives and observed limitations without running it.3435Skip this discovery turn when the operator already selected a workflow or supplied36`--mode` / `--from`. Mid-cycle work keeps its selected map and phase; do not infer a37new task from a state-file tail.3839## SENSE owns navigation control4041[SENSE Step 0d](../../../skills/sense/SKILL.md#step-0d--orientator-invocation-v40-phase-3)42calls `lib/orientator-routing.sh` directly, **not this public skill**. That existing43method verifies the profile, reads the pack's navigation, obtains a mechanical44recommendation and records its actual decision through `audit_log`. The library and45its [navigation reference](../../../docs/concepts/orientator.md) remain compatible.4647Keep these boundaries when proceeding from guidance to an authorized workflow:4849- SENSE's high-risk workflow always requires explicit confirmation, including when50 auto-mode is eligible. Low confidence needs judgment or an unresolved-decision51 question; it is not evidence of another model call.52- Configured defaults and extension namespaces remain pack-owned. A missing or drifted53 required profile blocks dependent navigation; never substitute neutral success.54- Explicit operator choices override a recommendation, not host permissions or55 mandatory controls. Verify the selected native entrypoint before execution.56- The compatibility escalation hook performs no model request. Do not report it as57 executed escalation, token consumption or measured routing success.5859This wrapper writes no audit or state. SENSE remains the decision producer when it60actually runs; discovery alone must not fabricate an orientation event or execution.