Lintel on GitHub Copilot. Generated from skills/roles-list/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/roles-list/ 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/roles-list/ 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.
Roles list
Retained read-only front door to the role owner's
lifecycle inventory. Use its configured
roots, bounded metadata, duplicate/shadowed rows and actual-selection reporting.
--include-private requires the method's explicit private-metadata consent; it
does not authorize reading a private role body.
Listing changes no preference, profile, ledger or synchronization state. Empty
neutral-pack inventory is valid; errors are not an empty success. If a role ID
is already known, use /li-role <id> directly. Creation remains /li-role-new.
1---2name: li-roles-list3description: Use to list configured role metadata and the current selection, with explicit consent before including private roles.4metadata:5 source: https://skillmd.com/skills/jokerman89/li-roles-list6---78> **Lintel on GitHub Copilot.** Generated from `skills/roles-list/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/roles-list/` 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/roles-list/` 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# Roles list2930Retained read-only front door to the role owner's31[lifecycle inventory](../../../skills/role/references/lifecycle.md#list). Use its configured32roots, bounded metadata, duplicate/shadowed rows and actual-selection reporting.33`--include-private` requires the method's explicit private-metadata consent; it34does not authorize reading a private role body.3536Listing changes no preference, profile, ledger or synchronization state. Empty37neutral-pack inventory is valid; errors are not an empty success. If a role ID38is already known, use `/li-role <id>` directly. Creation remains `/li-role-new`.