Lintel on GitHub Copilot. Generated from skills/web-session/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/web-session/ 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/web-session/ 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.
/web-session
One browser entrypoint with explicit modes. Select the current host's actual
provider and permission before operating; this skill installs no browser,
daemon, MCP server or credentials. The concrete local provider and extraction
module are retained under scripts/, not replaced by instructions to find a tool.
Modes
Use --mode browse|scrape|open|cookies; omitted mode means browse.
Reject unknown, duplicate or conflicting options before page access or output.
Mode-specific options belong only to their selected mode. These are skill
arguments, not flags for an invented web-session executable.
| Mode |
Preserved inputs and outcome |
Procedure |
browse |
URL/local artifact, --actions, --viewport, --out, --headed; open/read/act/screenshot/print/close |
Browse |
scrape |
--urls, --schema, --concurrency, --rate-limit, --diff; structured extraction and comparison |
Extract pages |
open |
--url, --profile, --devtools; explicitly owned operator-visible session. --check is non-launch provider preflight |
Open a session |
cookies |
--service, --login-url, --profile, validation URL/marker; user-managed login. --check checks only that selected authorized context |
Authentication |
All modes follow browser operations and ownership:
actual discovery, current work/profile references, exact hosts and origins,
pre-navigation request/redirect admission, scoped artifacts and owned cleanup.
Authentication never grants cookie export/import or wider navigation permission.
An inaccessible user-chosen surface remains a manual task, not authorization to
transfer its session elsewhere.
Provider and consumers
scripts/chromium.mjs exposes Admission, checkProvider, BrowserSession,
artifactName and validateAction. scripts/extract.mjs exposes validateSchema,
extractPage and diffRecords. The local provider requires an explicitly selected
installed Chromium-family executable, Node.js 22+ and Python 3.9+; it installs
nothing and preserves its single-page, no-credential boundaries.
Use frontend-design-review for built UI critique, generate-web --mode mockup
for static HTML authoring, and generate-pdf for composition/print choices. Printing
does not imply PDF text, dimensions or rendered-page inspection passed.
PDF and other consumers use these canonical resources through the existing
installed dependency inventory. Temporary resource bridges were removed after
those consumers were joined; they are not a second provider or entrypoint.
Missing installed resources remain an explicit integrity failure, not permission
to load a personal browser copy or a retired path.
Evidence
Report mode, actual provider/API/version, requested versus supported operations,
work/profile references, owner/handles, admitted destinations, real observations,
artifact paths and cleanup. Record blocked, failed and unattempted work separately.
Source checks are not browser execution; preflight is not launch; a screenshot is
not an accessibility audit; a PDF file is not completed inspection. Required
missing observations remain unverified under P05.
1---2name: li-web-session3description: Use to browse, extract pages, open an owned browser or validate user-managed sign-in through an actual provider with explicit URL admission and lifecycle evidence.4metadata:5 source: https://skillmd.com/skills/jokerman89/li-web-session6---78> **Lintel on GitHub Copilot.** Generated from `skills/web-session/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/web-session/` 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/web-session/` 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# /web-session2930One browser entrypoint with explicit modes. Select the current host's actual31provider and permission before operating; this skill installs no browser,32daemon, MCP server or credentials. The concrete local provider and extraction33module are retained under `scripts/`, not replaced by instructions to find a tool.3435## Modes3637Use `--mode browse|scrape|open|cookies`; omitted mode means `browse`.38Reject unknown, duplicate or conflicting options before page access or output.39Mode-specific options belong only to their selected mode. These are skill40arguments, not flags for an invented `web-session` executable.4142| Mode | Preserved inputs and outcome | Procedure |43|---|---|---|44| `browse` | URL/local artifact, `--actions`, `--viewport`, `--out`, `--headed`; open/read/act/screenshot/print/close | [Browse](../../../skills/web-session/references/browse.md) |45| `scrape` | `--urls`, `--schema`, `--concurrency`, `--rate-limit`, `--diff`; structured extraction and comparison | [Extract pages](../../../skills/web-session/references/scrape.md) |46| `open` | `--url`, `--profile`, `--devtools`; explicitly owned operator-visible session. `--check` is non-launch provider preflight | [Open a session](../../../skills/web-session/references/open.md) |47| `cookies` | `--service`, `--login-url`, `--profile`, validation URL/marker; user-managed login. `--check` checks only that selected authorized context | [Authentication](../../../skills/web-session/references/cookies.md) |4849All modes follow [browser operations and ownership](../../../skills/web-session/references/browser-operations.md):50actual discovery, current work/profile references, exact hosts and origins,51pre-navigation request/redirect admission, scoped artifacts and owned cleanup.52Authentication never grants cookie export/import or wider navigation permission.53An inaccessible user-chosen surface remains a manual task, not authorization to54transfer its session elsewhere.5556## Provider and consumers5758`scripts/chromium.mjs` exposes `Admission`, `checkProvider`, `BrowserSession`,59`artifactName` and `validateAction`. `scripts/extract.mjs` exposes `validateSchema`,60`extractPage` and `diffRecords`. The local provider requires an explicitly selected61installed Chromium-family executable, Node.js 22+ and Python 3.9+; it installs62nothing and preserves its single-page, no-credential boundaries.6364Use `frontend-design-review` for built UI critique, `generate-web --mode mockup`65for static HTML authoring, and `generate-pdf` for composition/print choices. Printing66does not imply PDF text, dimensions or rendered-page inspection passed.6768PDF and other consumers use these canonical resources through the existing69installed dependency inventory. Temporary resource bridges were removed after70those consumers were joined; they are not a second provider or entrypoint.71Missing installed resources remain an explicit integrity failure, not permission72to load a personal browser copy or a retired path.7374## Evidence7576Report mode, actual provider/API/version, requested versus supported operations,77work/profile references, owner/handles, admitted destinations, real observations,78artifact paths and cleanup. Record blocked, failed and unattempted work separately.79Source checks are not browser execution; preflight is not launch; a screenshot is80not an accessibility audit; a PDF file is not completed inspection. Required81missing observations remain unverified under P05.