Convert To Markdown
- 33 installs
- 269 repo stars
- Updated June 11, 2026
- gupsammy/claudest
Convert-to-markdown is an agent skill that extracts clean markdown from URLs via the ezycopy CLI.
About
Convert-to-markdown is an agent skill that wraps the ezycopy CLI so solo builders can turn noisy web pages into clean markdown without ads and clutter. Use it when someone hands you a link and wants an article, doc, or competitor page saved for research, validation notes, or documentation drafts. The skill forces a deliberate mode choice: default HTTP is fast for static HTML, while --browser spins headless Chrome when rendering or auth depends on JavaScript. Execution is a single Bash invocation with optional save or clipboard targets, plus a failure path that escalates to browser mode when output is empty or suspiciously short. It pairs naturally with later writing and planning skills because it produces portable text you can cite, summarize, or drop into repos—without building a custom scraper per site.
- Three-phase flow: choose extraction mode, run ezycopy, retry with --browser on empty or short output
- Default fast HTTP fetch; --browser for JS SPAs, Twitter/X, paywalls, and cookie-auth pages
- Flags: clipboard (-c), output path (-o), --no-images, timeout (-t), default 30s
- In browser mode run foreground without stderr redirected into stdout (2>&1 breaks capture)
- Triggered by convert/extract/scrape URL phrasing and argument-hint URL
Convert To Markdown by the numbers
- 33 all-time installs (skills.sh)
- Ranked #917 of 1,879 Documentation skills by installs in the Skillselion catalog
- Security screen: CRITICAL risk (skills.sh audit)
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/gupsammy/claudest --skill convert-to-markdownAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 33 |
|---|---|
| repo stars | ★ 269 |
| Security audit | 0 / 3 scanners passed |
| Last updated | June 11, 2026 |
| Repository | gupsammy/claudest ↗ |
What it does
Pull clean markdown from any URL with ezycopy—fast HTTP by default or headless Chrome when the page is JS-rendered or authenticated.
Who is it for?
Best when you're capturing competitor pages, articles, or JS-heavy sites into markdown for specs, notes, or content repurposing.
Skip if: Bulk crawling entire domains, bypassing paywalls without legitimate access, or pages where you already have an official API export.
When should I use this skill?
User asks to convert this page to markdown, extract/scrape a webpage, save an article from a URL, or provides a link for clean content.
What you get
You get clipboard or file-ready markdown from the chosen URL, with a clear fallback to headless Chrome when HTTP-only extraction fails.
- Markdown on clipboard (-c) or saved file/directory (-o)
- Clean text with optional images stripped (--no-images)
By the numbers
- Default timeout: 30s (-t)
- Phases: mode selection → execute ezycopy → handle failure with --browser
Files
Web-to-Markdown via EzyCopy
Extract clean markdown from any URL using the ezycopy CLI.
Phase 1: Determine Extraction Mode
Default mode uses fast HTTP fetch. Add --browser when the page relies on client-side JavaScript to render its content or when authentication cookies are required — the default fetcher only sees the raw HTML response, not the JS-rendered DOM.
Common --browser cases: Twitter/X, single-page applications, paywalled content.
Flags
-c— copy output to clipboard-o <path>— save to file or directory--browser— use headless Chrome for JS-rendered or authenticated pages--no-images— strip image links-t <duration>— timeout (default: 30s)
Phase 2: Execute
Run ezycopy <URL> [flags] with the chosen mode.
In --browser mode: run as a foreground process and do not redirect stderr with 2>&1. Chrome outputs diagnostic messages to stderr that should flow naturally rather than polluting stdout capture.
Phase 3: Handle Failure
If the output is empty or suspiciously short and --browser was not used, retry with --browser — the site likely requires JS rendering.
If ezycopy is not found, ask the user before installing:
curl -sSL https://raw.githubusercontent.com/gupsammy/EzyCopy/main/install.sh | shPhase 4: Deliver
Present the extracted markdown to the user. If the user requested a file save, use -o. If they requested clipboard, use -c. When no explicit destination was given, display the content directly.
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71How it compares
Use structured ezycopy extraction instead of asking the model to hallucinate page content from memory.
FAQ
Who is convert-to-markdown for?
Developers and agents who need faithful web text as markdown for research, documentation, or content workflows.
When should I use convert-to-markdown?
In Idea research when saving competitor or reference URLs; during Validate when grounding scope in external writeups; in Build docs when archiving third-party guides—whenever the user says convert this page to markdown or provides a URL to extract.
Is convert-to-markdown safe to install?
It runs Bash (ezycopy, curl) and may launch headless Chrome with network access; review the Security Audits panel on this Prism page before granting tools on sensitive machines.