http-fetch
Fetch a URL via HTTP/HTTPS and return the response body as text. Lightweight entrypoint replacement for `sub-agent` steps whose only job is a single GET/POST. Supports GET (default), POST/PUT/DELETE with a stdin-piped body, configurable timeout, and a max-bytes cap — no LLM agent loop, no custom-header injection (request goes out with urllib defaults). Use for simple data-fetch steps in meta-skill DAGs; for crawling, JS-rendered pages, or complex auth chains use sub-agent + scrapling instead.
Profile →npx skills add opensquilla/opensquilla --skill http-fetch --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# http-fetch (sub-skill) Direct shell wrapper for a single HTTP request. Replaces ``sub-agent`` sub-Agent steps that just GET/POST a URL — order-of- magnitude faster (no LLM round-trip, no tool surface, no iteration loop). ## Inputs (``with:``) | key | required | default | notes | |-------------|----------|------------------------|----------------------------------------------------------------| | `url` | yes | — | absolute http(s) URL | | `method` | no | `GET` | `GET` / `POST` / `PUT` / `DELETE` (case-insensitive) | | `body` | no | `''` | request body, piped via stdin (for POST/PUT); empty = no body | | `timeout` | no | `30` | request timeout in seconds | | `max_bytes` | no | `2000000` | response body cap; larger payloads truncated + suffixed `…` | ## Output - Success: response body on stdout (UTF-8 decoded, truncated to ``max_bytes`` if larger; lossy decode replaces invalid bytes). - Non-2xx response: exit 1, stderr ``HTTP <code>: <reason> <body[:200]>``; stdout still carries the body for callers that want to inspect. - Network / DNS / timeout failure: exit 2, stderr cause. ## When NOT to use - Crawling multiple pages → use ``scrapling`` (via ``sub-agent``). - JS-rendered pages →
- Inputs (with:)
- Output
- When NOT to use
- Fallback
What does the http-fetch skill do?
Fetch a URL via HTTP/HTTPS and return the response body as text. Lightweight entrypoint replacement for `sub-agent` steps whose only job is a single GET/POST. Supports GET (default), POST/PUT/DELETE with a stdin-piped body, configurable timeout, and a max-bytes cap — no LLM agent loop, no custom-header injection (request goes out with urllib defaults). Use for simple data-fetch steps in meta-skill DAGs; for crawling, JS-rendered pages, or complex auth chains use sub-agent + scrapling instead.
How do I install it?
Run `npx skills add opensquilla/opensquilla --skill http-fetch --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From opensquilla/opensquilla, a repository with 6,515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.