read-routerlisted
Install: claude install-skill juliuswiener/nord-kit
# read-router — choose the read paradigm per input
"Get web data" is not one task. Picking the wrong reader is the most common and most
expensive mistake: a screenshot in context costs many times the tokens of clean markdown,
and an HTML parser can throw away 40%+ of the recoverable text. Decide per input, then call
exactly one reader. Do not pipe everything through the same tool.
This skill is a **router**: it classifies the input and hands off. It does not fetch itself.
---
## Decision tree (classify, then hand off)
```
INPUT
│
├─ No URL yet — need to FIND sources?
│ → search first: `research --web` or exa (mcp). Then re-enter with the URLs.
│
├─ Document file (PDF / Office / scanned)?
│ ├─ mostly text + tables → doc-extract (MinerU → markdown, CHEAP)
│ └─ layout carries meaning → pixel-read (charts/forms/scans, images, costly)
│
├─ Web page (URL)?
│ ├─ normal page → web-scrape (Crawl4AI local, free)
│ ├─ anti-bot / login / heavy JS → web-scrape --stealth (on-device stealth)
│ └─ layout/chart IS the content → pixel-read (render to image)
│
└─ Social platform (X / Reddit / YT / GitHub thread)?
→ native tools / WebFetch. (No bulk social-scraper wired; ToS-gray, out of scope.)
```
## Cost order — prefer the cheapest reader that captures the information
1. **Text markdown** (web-scrape, doc-extract) — cheapest. Default for prose, articles, docs, tables.
2.