Hurl is a command-line tool for running and testing HTTP requests defined in plain text files. Built on libcurl, it supports chaining multiple requests, capturing values, asserting responses with JSONPath and XPath, and integrating into CI/CD pipelines — making it ideal for API testing, integration testing, and endpoint validation.
Scanned 6/8/2026
Install via CLI
openskills install agentskillexchange/skills---
name: "Hurl Declarative HTTP Request Runner and Tester"
slug: "hurl-declarative-http-request-runner-tester"
description: "Hurl is a command-line tool for running and testing HTTP requests defined in plain text files. Built on libcurl, it supports chaining multiple requests, capturing values, asserting responses with JSONPath and XPath, and integrating into CI/CD pipelines — making it ideal for API testing, integration testing, and endpoint validation."
github_stars: 18696
verification: "security_reviewed"
source: "https://github.com/Orange-OpenSource/hurl"
category: "Developer Tools"
framework: "Custom Agents"
tool_ecosystem:
github_repo: "Orange-OpenSource/hurl"
github_stars: 18696
---
# Hurl Declarative HTTP Request Runner and Tester
Hurl is a command-line tool for running and testing HTTP requests defined in plain text files. Built on libcurl, it supports chaining multiple requests, capturing values, asserting responses with JSONPath and XPath, and integrating into CI/CD pipelines — making it ideal for API testing, integration testing, and endpoint validation.
## Installation
Use the upstream install or setup path that matches your environment:
- $ brew install hurl
- $ cargo install --locked hurl
- $ conda install -c conda-forge hurl
- $ docker pull ghcr.io/orange-opensource/hurl:latest
Requirements and caveats from upstream:
- [Docker](#docker)
- Asserting JSON body response (node values, collection count etc...) with [JSONPath]:
- By default, Hurl doesn't follow redirection so each step of a redirect must be run manually and can be analysed:
Basic usage or getting-started notes:
- GET https://example.org
- POST https://example.org/login
- GET https://example.org/api/health
- Source: https://github.com/Orange-OpenSource/hurl
- Extracted from upstream docs: https://raw.githubusercontent.com/Orange-OpenSource/hurl/HEAD/README.md
## Source
- [Agent Skill Exchange](https://agentskillexchange.com/skills/hurl-declarative-http-request-runner-tester/)
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.