markdown-url

Original：🇺🇸 English

Translated

1 scriptsChecked / no sensitive code detected

Route any website you need to visit through markdown.new by prefixing the URL. **WHEN TO USE:** - You would normally open a website link to read content (docs, blog posts, changelogs, GitHub issues, etc.) - You need a cleaner, Markdown-friendly view for copying notes or summarizing

11.7kinstalls

Sourceam-will/codex-skills

Added on2026-02-16

NPX Install

npx skill4agent add am-will/codex-skills markdown-url

SKILL.md Content

View Translation Comparison →

markdown.new URL Prefix

Whenever you need to visit a website URL, you must:

rewrite it to go through
```
https://markdown.new/
```
, then
visit the rewritten URL, and
pull the Markdown content from that page for use in your answer/notes.

Rewrite Rule

Normalize the destination into an absolute URL with a scheme (
```
https://
```
preferred).
Prefix it with
```
https://markdown.new/
```
(do not drop the original scheme).

Examples

https://example.com

->

https://markdown.new/https://example.com

https://example.com/docs?a=1#b

->

https://markdown.new/https://example.com/docs?a=1#b

example.com

->

https://markdown.new/https://example.com

Agent Workflow (Required)

When you would normally open a website to read it:

Produce the rewritten
```
markdown.new
```
URL.
Visit the rewritten URL first (not the original), but only when it is likely to work (see Policy below).
Extract the page content from the Markdown view (the rendered Markdown and/or the raw Markdown).
Use that extracted Markdown as the source for summaries, quotes, checklists, or copy/pasteable notes.

If the

markdown.new

view fails to load or breaks critical functionality, fall back to the original URL for browsing, but still prefer

markdown.new

for any content extraction if possible.

Policy: When To Use markdown.new (Required)

Do NOT route every site through

markdown.new

. Use it primarily for "read-only" pages where you want clean, extractable text:

Documentation pages
Blog posts / announcements / changelogs
GitHub issues/PR discussions (when you just need readable text)
Articles and guides

Skip

markdown.new

and go straight to the original URL when the destination is likely to be blocked or requires the original site behavior:

Login, OAuth, checkout, payment, or any authenticated workflow
Sites that gate content behind JS apps, CAPTCHAs, bot detection, or paywalls
File uploads, forms, editors, dashboards, interactive widgets
Anything where cookies/session state must be preserved

Block/Failure Signals (Treat As Blocked)

If you try

markdown.new

and see any of the below, stop retrying and fall back to the original URL:

HTTP
```
401/403/429
```
, "Access denied", "Forbidden", "rate limited"
CAPTCHA / "verify you are human"
Empty/partial content that clearly does not match the page
Redirect loops or repeated navigation failures

Fallback Behavior

Attempt
```
markdown.new
```
once when appropriate.
On block/failure, immediately switch to the original URL for browsing.
If you still need extractable text, try to extract from the original page (reader mode / copy text) and clearly note that
```
markdown.new
```
was blocked.

Notes / Exceptions

Keep this for reading/browsing. For API endpoints, OAuth flows, file uploads, or anything that depends on cookies/login state, use the original URL if the proxy breaks functionality.
Do not rewrite local paths (
```
./README.md
```
) or non-HTTP(S) schemes.

Optional CLI Helper

Convert a URL into its markdown.new-prefixed form:

bash

node skills/markdown-url/scripts/markdown-url.js "https://example.com/docs"