fetch-403
仓库创建 2026年7月22日最近提交 3 天前SkillHot 收录 5 小时前
▸ 精选理由
快速定位并恢复被拦截的文档或参考链接，便于检索和研究引用。
▸ 风险提示
可能涉及绕过站点反爬或机器人检测，注意合规性。
这个 Skill 做什么
在内置抓取器返回 403/空体或人机验证时，提供恢复页面内容的流程与技巧。
当内置抓取器（WebFetch）被拒绝、返回 403、空体或跳出人机验证页时，这套流程帮你把真实页面找回来。讲清楚用 curl 做回退、如何寻找机器可读端点，以及遇到被封源时不能凭记忆答复的规则。适合需要引用外部文档但常被自动化封禁的场景。
▸ 展开 SKILL.md 英文原文
Recover a web page after the built-in fetcher (WebFetch) is refused — 403 Forbidden, empty body, or a "Just a moment…" bot-check interstitial instead of content. Use when a documentation page, blog post, or reference URL won't load through the normal fetch tool and the content is still needed. Covers the curl fallback, machine-readable endpoints, and the rule against silently answering from memory when a source stays blocked.
1
Stars
0
Forks
6
仓库内 Skill
积累中
7 日增星
安装 / 使用
给你的 Agent 一句话（通用）
帮我安装这个 skill：https://raw.githubusercontent.com/thititongumpun/skills/main/skills/fetch-403/SKILL.md或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/thititongumpun/skills/main/skills/fetch-403/SKILL.md"SKILL.MD 节选查看完整文件 ↗
# Fetching a page that returned 403
A 403 from the built-in fetcher usually means *that fetcher* is unwelcome, not
that the site blocks automation. `debezium.io` is the reference case: WebFetch
gets 403, bare `curl` gets 200. WebFetch's 403 message may suggest the page
needs authentication — try rung 1 before believing that; public docs pages
403 the fetcher's UA all the time.
Work down this list. Stop at the first rung that returns content.
## 1. curl
```bash
curl -sL -w '\n[%{http_code}]\n' URL -o /tmp/page.html
```
If that 403s, retry once with a browser User-Agent — it fixes plain UA
filtering:
```bash
curl -sL -A 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecvia SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有