HTTP API Tester for Openclaw

Openclaw Skills turns endpoint descriptions into reusable curl smoke tests with timing, status assertions, and CI-ready shell output.

kingaiwork
v1.0.0
Jul 16, 2026
0
0
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install http-api-tester

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install http-api-tester using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is HTTP API Tester?

Openclaw Skills powers HTTP API Tester, a workflow that converts endpoint descriptions - method, route, auth, and sample parameters - into reusable curl smoke tests. It is built to validate health checks, expected success responses, error codes, and authentication failures without hand-crafting one-off scripts for every endpoint.

The generated output adds -s -w status and timing reporting, can emit JSON batch assertion variants for jq, and is exportable as CI-runnable shell. The free local edition covers the core generator, while the enterprise option unlocks batch scale, advanced tuning, API automation integration, and priority support.

HTTP API Tester Use Cases

  • Generate a reusable curl smoke-test suite from a raw API endpoint list.
  • Verify health checks, successful responses, error paths, and authentication failures.
  • Add status-code assertions and latency reporting to existing API checks.
  • Produce JSON-oriented batch validation that pairs with jq.
  • Package the same checks for local execution and CI pipelines such as GitHub Actions.
  • Standardize regression testing when APIs change frequently or are shared across teams.

How HTTP API Tester Works

  1. Provide the API inventory: HTTP method, path, auth requirements, headers, and sample parameters.
  2. The skill classifies each endpoint into test scenarios such as health, success, error, and auth-failure coverage.
  3. It generates curl commands with -s -w output so each request prints HTTP status and timing details.
  4. It layers in assertions, including optional JSON batch checks that can be validated with jq.
  5. The result is exported as a Bash script that can run locally or drop directly into CI for repeatable API smoke testing.

HTTP API Tester Setup

Openclaw Skills is an AI skill, so there is no package to install for the skill itself. Set up the runtime tools that will execute the generated tests, then feed the skill your endpoint descriptions.

  1. Install the command-line dependencies used by the generated scripts:
# macOS
brew install curl jq

# Ubuntu or Debian
sudo apt-get update
sudo apt-get install -y curl jq
  1. Prepare a compact API brief for each endpoint: method, path, auth, headers, sample parameters, and the expected success or failure status.

  2. Ask the skill to generate the smoke-test shell. Save the result to a file such as api_smoke_tests.sh.

  3. Make the script executable and run it locally:

chmod +x api_smoke_tests.sh
./api_smoke_tests.sh
  1. For CI, commit the script to your repository and call it from a workflow step so the same checks run on every build.

HTTP API Tester Data Schema & Taxonomy

The skill works from a simple endpoint-to-test mapping and emits a shell-based verification artifact.

Layer Typical fields Purpose
Input API spec method, path, auth, headers, query/body parameters, example values, expected status Describes what to test
Scenario taxonomy health, success, error, auth-failure Expands each endpoint into coverage buckets
Command template curl flags, payload, headers, -s -w reporter Builds runnable HTTP checks
Assertion layer HTTP status, body pattern, timing, jq checks, exit code Validates the response
Runtime metadata http_status, duration_ms, exit_code, response_excerpt Supports CI and regression tracking
Output artifact Bash script, optional JSON batch assertion blocks Usually one runnable .sh file plus optional machine-readable checks

Metadata is usually organized by endpoint identifier, HTTP method, route, auth mode, scenario name, expected status code, and any body or timing checks. The generated content is intentionally flat and shell-friendly so it can be copied into GitHub Actions, cron jobs, or other automation runners without extra packaging.

HTTP API Tester Advanced Features

  • Automatically includes -s -w reporting so every request prints status and timing data.
  • Generates multiple verification modes from the same endpoint brief: health, success, error, and authentication failure.
  • Supports JSON batch assertions and jq-based validation for machine-readable checks.
  • Exports clean Bash output that can be reused unchanged in CI pipelines.
  • Scales from a single endpoint to a multi-endpoint smoke-test suite for regression coverage.
  • The enterprise tier adds batch or unlimited usage, advanced tuning, API and automation access, and priority support with SLA.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*