# Li Web Session

> 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.

- Skill: `jokerman89/li-web-session` (Agent Skill)
- Install (CLI): `npx get-skill add jokerman89/li-web-session`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jokerman89/li-web-session/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jokerman89 (https://skillmd.com/u/jokerman89)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/jokerman89/li-web-session

---


> **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](../../../skills/web-session/references/browse.md) |
| `scrape` | `--urls`, `--schema`, `--concurrency`, `--rate-limit`, `--diff`; structured extraction and comparison | [Extract pages](../../../skills/web-session/references/scrape.md) |
| `open` | `--url`, `--profile`, `--devtools`; explicitly owned operator-visible session. `--check` is non-launch provider preflight | [Open a session](../../../skills/web-session/references/open.md) |
| `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) |

All modes follow [browser operations and ownership](../../../skills/web-session/references/browser-operations.md):
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.

