web-fetch
SolidFetches web content as clean markdown by preferring markdown-native responses and falling back to selector-based HTML extraction. Use for documentation, articles, and reference pages at http/https URLs.
Install
Quality Score: 79/100
Skill Content
Details
- Author
- aiskillstore
- Repository
- aiskillstore/marketplace
- Created
- 7 months ago
- Last Updated
- today
- Language
- Python
- License
- None
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
fetch-url-as-markdown
Fetch a web page (URL) and return clean Markdown via local trafilatura, with Exa MCP as a fallback for JS-rendered or anti-bot pages. Use when the user asks to read, fetch, scrape, summarize, or quote a URL — prefer this over the built-in WebFetch tool. Don't use for binary files (PDFs, images, archives) or for fetching API/JSON endpoints.
ultra-fetch
Fetch, crawl, or map web pages into clean, context-efficient markdown saved to a file — using a stealth browser that reaches sites the built-in WebFetch can't (bot-protected, Cloudflare, JS-rendered), plus BM25 filtering that keeps only the parts relevant to a query. Use this as the default for actually reading a web page's content, following a search result deeper, reading across a whole site, or discovering what URLs a site has — especially after a WebSearch, or whenever WebFetch is blocked, returns junk, or you need the result saved to disk. NOT for a trivial quick fact where WebFetch already suffices, NOT for logged-in or authenticated pages (out of scope — use the dedicated scrape-x / scrape-fb tools for X and Facebook), and NOT for developing the ultra-fetch tool itself, which is ordinary repo work.
browser-fetch
Fetch a web page with a real headless Chrome browser (undetected-chromedriver) for two cases WebFetch can't handle. (1) Anti-bot blocking — a 403, a bot-check/"Just a moment" page, or Cloudflare/PerimeterX challenges. (2) JavaScript-rendered pages where WebFetch comes back empty, truncated, or as a shell because the content is built client-side (single-page apps, Swagger/ReDoc/other API docs, dashboards). It renders the page, waits for the JS to settle, and extracts the resulting text. Maintains a persistent per-machine browser profile so bot-challenge cookies persist across fetches instead of re-triggering the challenge every time. Use as a fallback after WebFetch fails OR returns unusable/empty content — not as a first choice, since it's much slower. Fetch-only, not interactive (no clicking/form-filling). Does NOT help with geo-blocking or content behind a login.