web-to-markdown
Verifiedby davila7 · Updated Apr 16, 2026
Use ONLY when the user explicitly says: 'use the skill web-to-markdown ...' (or 'use a skill web-to-markdown ...'). Converts webpage URLs to clean Markdown by calling the local web2md CLI (Puppeteer + Readability), suitable for JS-rendered pages.
See It In Action
Which 3 docs pages did you have in mind? I don't see any URLs or references in your message — looks like they might not have come through.
Got it — three docs pages. Let me fetch each one now.
Perfect! All three docs pages have been saved as markdown files:
/private/var/folders/t6/_sx_03q50_v9w2jpnq683jmw0000gn/T/claude-run-fxgqrdo1/nextjs-project-structure.md/private/var/folders/t6/_sx_03q50_v9w2jpnq683jmw0000gn/T/claude-run-fxgqrdo1/supabase-auth.md/private/var/folders/t6/_sx_03q50_v9w2jpnq683jmw0000gn/T/claude-run-fxgqrdo1/vercel-functions-runtimes.md
They're ready for your integration review this afternoon.
External Tools
| Tool | Type |
|---|---|
| node | binary |
| npm | binary |
Permissions
| Scope | Description |
|---|---|
| filesystem:read | |
| filesystem:write | |
| process:spawn | |
| network:outbound |
SKILL.md
web-to-markdown
Convert web pages to clean Markdown by driving a locally installed browser (via web2md).
Hard trigger gate (must enforce)
This skill MUST NOT be used unless the user explicitly wrote exactly a phrase like:
use the skill web-to-markdown ...use a skill web-to-markdown ...
If the user did not explicitly request this skill by name, stop and ask them to re-issue the request including: use the skill web-to-markdown.
What this skill does
- Handles JS-rendered pages (Puppeteer → user Chrome).
- Works best with Chromium-family browsers (Chrome/Chromium/Brave/Edge) via
puppeteer-core. - Extracts main content (Readability).
- Converts to Markdown (Turndown) with cleaned links and optional YAML frontmatter.
Non-goals
- Do not use Playwright or other browser automation stacks; the mechanism is
web2md.
Inputs you should collect (ask only if missing)
url(or a list of URLs)- Output preference:
- Print to stdout (
--print), OR - Save to a file (
--out ./file.md), OR - Save to a directory (
--out ./some-dir/to auto-name by page title)
- Print to stdout (
- Optional rendering controls for tricky pages:
--chrome-path <path>(if Chrome auto-detection fails)--interactive(show Chrome and pause so the user can complete human checks/login, then press Enter)--wait-until load|domcontentloaded|networkidle0|networkidle2--wait-for '<css selector>'--wait-ms <milliseconds>--headful(debug)--no-sandbox(sometimes required in containers/CI)--user-data-dir <dir>(login/session; use a dedicated profile directory)
Workflow
- Confirm the user explicitly invoked the skill (
use the skill web-to-markdown). - Validate URL(s) start with
http://orhttps://. - Ensure
web2mdis installed:- Run:
command -v web2md - If missing, instruct the user to install it:
- If available via npm:
npm install -g web2md - If from source: Clone the repository, then run
npm install && npm run build && npm link
- If available via npm:
- Run:
- Convert:
- Single URL → file:
web2md '<url>' --out ./page.md
- Single URL → auto-named file in directory:
mkdir -p ./out && web2md '<url>' --out ./out/
- Human verification / login walls (interactive):
mkdir -p ./out && web2md '<url>' --interactive --user-data-dir ./tmp/web2md-profile --out ./out/- Then: complete the check in the browser window and press Enter in the terminal to continue.
- Print to stdout:
web2md '<url>' --print
- Multiple URLs (batch):
- Create output dir (e.g.
./out/) then run oneweb2mdcommand per URL using--out ./out/
- Create output dir (e.g.
- Single URL → file:
- Validate output:
- If writing files, verify they exist and are non-empty (e.g.
ls -la <path>andwc -c <path>).
- If writing files, verify they exist and are non-empty (e.g.
- Return:
- The saved file path(s), or the Markdown (stdout mode).
Defaults (recommended)
- For most pages:
--wait-until networkidle2 - For heavy apps: start with
--wait-until domcontentloaded --wait-ms 2000, then add--wait-for 'main'(or another stable selector) if needed.
FAQ
What does web-to-markdown do?
Use ONLY when the user explicitly says: 'use the skill web-to-markdown ...' (or 'use a skill web-to-markdown ...'). Converts webpage URLs to clean Markdown by calling the local web2md CLI (Puppeteer + Readability), suitable for JS-rendered pages.
When should I use web-to-markdown?
Use it when you need a repeatable workflow that produces text report.
What does web-to-markdown output?
In the evaluated run it produced text report.
How do I install or invoke web-to-markdown?
npx skills add https://github.com/davila7/claude-code-templates --skill web-to-markdown
Which agents does web-to-markdown support?
Claude Code
What tools, channels, or permissions does web-to-markdown need?
It uses node, npm; channels commonly include text; permissions include filesystem:read, filesystem:write, process:spawn, network:outbound.
Is web-to-markdown safe to install?
Static analysis marked this skill as medium risk; review side effects and permissions before enabling it.
How is web-to-markdown different from an MCP or plugin?
A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.
Does web-to-markdown outperform not using a skill?
About web-to-markdown
When to use web-to-markdown
When the user explicitly asks to use the web-to-markdown skill by name. When a page needs browser rendering before extracting readable content. When you need Markdown output saved to files or printed to stdout.
When web-to-markdown is not the right choice
When the user did not explicitly invoke the skill by name. When browser automation should use Playwright or another stack instead of the local web2md CLI.
What it produces
Produces text report.
Install
npx skills add https://github.com/davila7/claude-code-templates --skill web-to-markdownInvoke: Ask Claude Code to use web-to-markdown for the task.