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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, well-structured wrapper-skill body: lean, organized into clear sections, with a concrete I/O and exit-code contract and appropriate offloading of executable code to the bundled script. The only minor gap is the absence of an inline invocation example.

Dimension	Reasoning	Score
Conciseness	Lean body with an inputs table, an output/exit-code contract, and short routing sections; no concept-padding and every line earns its place, matching the 5-anchor.	5 / 5
Actionability	Concrete input defaults and an explicit exit-code/stderr contract make invocation actionable, but there is no inline invocation example; the executable code lives only in the bundled script, leaving a minor gap versus the 5-anchor's copy-paste-ready examples.	4 / 5
Workflow Clarity	A single-action wrapper skill whose one action (invoke with url/method/etc.) is unambiguous, with the exit-code contract serving as the caller's validation checkpoint; the simple-skill exception applies and it is not a destructive/batch operation.	5 / 5
Progressive Disclosure	Under 50 lines with well-organized sections and the single bundled script kept out of the body via the entrypoint; per the rubric's simple-skill note this satisfies the 5-anchor with no nested references.	5 / 5
	Total	19 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tight, well-scoped description that concretely states capabilities, gives explicit use-when and when-NOT-to-use guidance, and carves out a distinct niche against related tools. Trigger-term coverage is strong but could add a few natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities (GET/POST/PUT/DELETE, stdin-piped body, configurable timeout, max-bytes cap) with only minor framing gaps; not quite the fully comprehensive action enumeration of the 5-anchor.	4 / 5
Completeness	Explicitly answers both 'what' (fetch URL, return body, methods/timeout/max-bytes) and 'when' ('Use for simple data-fetch steps in meta-skill DAGs' plus an explicit when-NOT-to-use clause), matching the 5-anchor.	5 / 5
Trigger Term Quality	Natural terms like 'Fetch a URL', 'GET/POST', 'HTTP/HTTPS', and 'data-fetch' appear, but common synonyms such as 'download' or 'request' are missing, short of the 5-anchor's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	Clear niche as a lightweight single-HTTP-fetch entrypoint with explicit boundaries against sub-agent/scrapling for crawling, JS rendering, and auth chains, giving minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: TokenRhythm/opensquilla
Path: src/opensquilla/skills/bundled/http-fetch/SKILL.md
Commit: 94ac35e

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.