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.
72
90%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
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).
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 … |
max_bytes if larger; lossy decode replaces invalid bytes).HTTP <code>: <reason> <body[:200]>;
stdout still carries the body for callers that want to inspect.scrapling (via sub-agent).sub-agent + browser tools.sub-agent.If this skill is unavailable, callers should spawn sub-agent
with a curl/requests task — same result, ~10× the latency and a
non-deterministic tool loop.
94ac35e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.