Install
openclaw skills install @ernestyu/clawfetchThin OpenClaw and ClawHub wrapper for the published clawfetch npm CLI, used to fetch web pages, GitHub READMEs, and Reddit threads as markdown.
openclaw skills install @ernestyu/clawfetchThis skill is a thin Agent wrapper around the published clawfetch npm CLI. It is not a second scraper product and it does not contain a separate implementation of clawfetch.
Use this skill when an Agent needs to fetch web content into markdown for knowledge-base ingestion, source review, or compact reading. Typical targets include ordinary web pages, GitHub repository README pages, and Reddit threads.
This skill does not:
The runtime behavior belongs to the published clawfetch CLI installed by bootstrap_deps.sh.
Installing this skill through OpenClaw/ClawHub only installs the wrapper files in this directory. Do not treat openclaw skills install clawfetch as a complete clawfetch installation.
First-time setup is not complete until both the npm CLI and the browser runtime are installed and checked:
SKILL.md and bootstrap_deps.sh.cd <installed skill directory>
sh bootstrap_deps.sh
node node_modules/clawfetch/clawfetch.js runtime install
node node_modules/clawfetch/clawfetch.js runtime check
node node_modules/clawfetch/clawfetch.js https://example.com
The smoke test should print --- METADATA --- and --- MARKDOWN ---.
The bootstrap script installs the published clawfetch npm package into this skill directory, under node_modules/clawfetch, and verifies that node_modules/clawfetch/clawfetch.js exists before reporting success. It does not install the browser runtime, clone a repository, install unrelated packages, modify global npm state, or change system paths.
When this skill lives inside the clawfetch project repository, bootstrap reads the project root package.json and installs that same version. If the wrapper is distributed without the project root, it uses the pinned fallback version in bootstrap_deps.sh; maintainers must keep that fallback aligned with the current published CLI version.
Ready state means node_modules/clawfetch exists and node node_modules/clawfetch/clawfetch.js runtime check exits successfully. If runtime check fails, run node node_modules/clawfetch/clawfetch.js runtime diagnose --json and follow the CLI's NEXT: hints.
This skill includes a formal configuration file at:
clawfetch.toml
From this skill directory, the CLI resolves that file as the fixed host config for node_modules/clawfetch/clawfetch.js. Do not place the long-lived skill configuration inside node_modules/clawfetch; that directory is a bootstrap-generated npm package install and may be replaced during repair, upgrade, or re-bootstrap.
The default config is conservative:
[flaresolverr]
enabled = false
# url = "http://127.0.0.1:8191"
max_timeout_ms = 60000
To enable FlareSolverr, edit this skill directory's clawfetch.toml, set enabled = true, and set url to a reachable FlareSolverr-compatible service. FLARESOLVERR_URL remains supported only as a compatibility or temporary override; it is not the preferred skill configuration path.
After bootstrap and a successful runtime check, invoke the CLI through the local package installation:
node node_modules/clawfetch/clawfetch.js https://example.com/article
Runtime lifecycle commands are also provided by the CLI itself:
node node_modules/clawfetch/clawfetch.js runtime install
node node_modules/clawfetch/clawfetch.js runtime check
node node_modules/clawfetch/clawfetch.js runtime diagnose --json
Do not bypass these CLI lifecycle commands from the skill layer. Browser runtime install, check, repair, upgrade, clean, and diagnose behavior must remain owned by the clawfetch CLI. bootstrap_deps.sh installs the npm CLI; runtime install installs the browser runtime. Both are required for first use.
Use the CLI's NEXT: hints when recovering from missing dependencies, missing browser runtime, runtime mismatch, protected pages, or weak extraction results. The skill should surface those hints rather than inventing alternate recovery paths.