菜单
Fetch a web page and return its content as clean markdown. Use whenever you need to read any web content — documentation, articles, APIs, READMEs, blog posts. Always returns content to stdout; falls back gracefully through multiple extraction methods. Use --discover to explore a site's structure before fetching specific pages.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when a task is parallelizable, would consume many tokens (large file reads, codebase exploration, summarization), or involves grunt work that doesn't need your full reasoning ability. Spawn a sub-agent instead of doing it yourself.
Use when a command takes more than ~1 minute, needs to persist (servers, watchers), or when running it in the background lets you continue making progress on other work in parallel. Examples: dev servers, long builds, background subagents. Do not use for short one-shot commands (typecheck, lint, quick tests) — just run those directly.
| name | web-fetch |
| description | Fetch a web page and return its content as clean markdown. Use whenever you need to read any web content — documentation, articles, APIs, READMEs, blog posts. Always returns content to stdout; falls back gracefully through multiple extraction methods. Use --discover to explore a site's structure before fetching specific pages. |
Fetch a URL and get markdown back:
bun run skills/web-fetch/scripts/fetch.ts https://docs.example.com/api
Get raw HTML instead (truncated to 10k chars):
bun run skills/web-fetch/scripts/fetch.ts --raw https://example.com
Explore a site's structure (use before fetching when you don't know the exact URL):
bun run skills/web-fetch/scripts/fetch.ts --discover example.com
Output goes to stdout, errors to stderr. On success (HTTP 200), always returns content — worst case is truncated raw HTML. On hard failure (network error, non-200 HTTP status), exits with code 1 and prints the error to stderr.