http-qa

Verifies HTTP/JSON endpoints by driving live services with curl and asserting responses via jq/grep/awk.

33|5|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/kylesnowschwartz/ralph-ban --skill http-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: http-qa
Source: https://github.com/kylesnowschwartz/ralph-ban/tree/main/skills/http-qa
Command: npx skills add https://github.com/kylesnowschwartz/ralph-ban --skill http-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ensures an HTTP/JSON endpoint behaves according to its spec by driving a running service end-to-end and validating the full response (status, headers, body, timing) with captured evidence.

Core Features & Use Cases

  • Deterministic endpoint driving: Starts the server, polls readiness by hitting a real endpoint, and sends the actual request via curl.
  • Transcript-based verification: Captures request/response artifacts into a structured evidence directory for auditing and debugging.
  • Spec comparison via assertions: Uses a jq-based assertion grammar to validate response shape and headers, then classifies outcomes as spec violations vs environmental flake.
  • Use case: Confirm that a route change (schemas, status semantics, headers, or error handling) still matches expectations before merging.

Quick Start

Run http-qa after your latest changes and tell it which endpoint scope to verify, then review the generated verdict and transcript evidence under .agent-history/oracle/.

Frequently Asked Questions about http-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify HTTP endpoint behavior with real request and response evidence?

You can verify HTTP endpoint behavior by booting the service, polling readiness via the actual route, and driving the endpoint with curl while capturing full request and response evidence for auditing.

How do I validate JSON response shapes and headers in a CI-like environment?

Validate JSON response shapes and headers using jq, grep, and awk-based assertions over status, headers, and JSON body to check for route regressions before merging in local or CI-like environments.

What is the best way to test API routes for regressions after a schema change?

Testing API routes for regressions after a schema change involves driving the running service end-to-end, validating status semantics and error handling, and classifying unexpected outcomes using a flake-vs-defect rubric.

Can I use curl and jq to check API endpoint readiness and timing budgets?

Yes, you can use curl and jq to check API endpoint readiness and timing budgets by polling the actual endpoint route and running assertions to verify the response meets your specified timing constraints.

Why does my HTTP endpoint test fail intermittently in local environments?

HTTP endpoint test failures are classified using a flake-vs-defect rubric, distinguishing between environmental flake and actual spec violations by capturing request and response artifacts into a structured evidence directory.

Do I need a running server to validate API response schemas and error handling?

Yes, deterministic endpoint driving starts the server, polls readiness by hitting a real endpoint, and sends the actual request to validate the full response including status, headers, body, and error handling.