web-to-markdown

Convert web pages to clean Markdown by driving a locally installed browser (via web2md).

softaworks/agent-toolkit|Updated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGoose

Installation Guide

Select your AI agent

How to use web-to-markdown on Cursor

AI-first code editor with Composer

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

›Cursor installed and configured on your machine
›Node.js 16+ with npm — verify with node --version
›Active project directory where you want to add web-to-markdown

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/softaworks/agent-toolkit --skill web-to-markdown

Fetches web-to-markdown from softaworks/agent-toolkit and configures it for Cursor.

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?

│

│ ── Universal (.agents/skills) ────────────────

│ · Cline · Codex · Goose · Windsurf

│ ●Cursor(selected)

│ · Cursor · Aider · Continue

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/web-to-markdown

Restart Cursor to activate web-to-markdown. Access via /web-to-markdown in your agent's command palette.

⚠

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

›View source on GitHub ›Skills CLI docs ›About Cursor ›What are agent skills?

Documentation

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

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)

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:// or https://.

Ensure web2md is installed:

Run: command -v web2md
If missing, instruct the user to install it (assume the project exists at ~/workspace/softaworks/projects/web2md):
- cd ~/workspace/softaworks/projects/web2md && npm install && npm run build && npm link
- Or: cd ~/workspace/softaworks/projects/web2md && npm install && npm run build && npm install -g .

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 one web2md command per URL using --out ./out/

Validate output:

If writing files, verify they exist and are non-empty (e.g. ls -la <path> and wc -c <path>).

Return:

The saved file path(s), or the Markdown (stdout mode).

web-to-markdown

Installation Guide

How to use web-to-markdown on Cursor

Prerequisites

Run the install command

Select Cursor when prompted

Verify installation

Security Notice

Documentation

List & Monetize Your Skill

Use Cases

User Story & Requirements Generation

Competitive Analysis

Roadmap Prioritization

Install Skill

web-to-markdown

Hard trigger gate (must enforce)

What this skill does

Non-goals

Inputs you should collect (ask only if missing)

Workflow

Defaults (recommended)

Stakeholder Communication

Implementation Guide

Best Practices

When to Use This

Learning Path

Related Skills

web-accessibility

grill-me

premortem

deslop

framer-motion

write-a-prd

Reviews

Discussion