Index of every page on this site: llms.txt
All skills
Run it yourself

Use when testing HTTP endpoints, probing URLs for status and headers, or running declarative API test suites from plain text files

  • 1 file
  • 4 KB
  • MIT
  • Updated 6 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/api-testing

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈36 tokens for metadata: the name and description. ≈960 when used: this file.

Description uses 1.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈144 characters, or 1.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

API Testing

When to Use

  • Testing REST API endpoints for correct responses
  • Writing declarative, repeatable HTTP test suites
  • Chaining HTTP requests (authenticate → create → verify)
  • Probing multiple URLs for availability, status codes, or headers
  • Validating response bodies, headers, and status codes with assertions

Tools

Tool Purpose Structured output
Hurl Declarative HTTP testing from plain text .hurl files --json for JSON report
httpx Fast HTTP probing toolkit (ProjectDiscovery) -json for JSON output

Patterns

Hurl: Simple GET with status assertion

Create a .hurl file:

GET http://localhost:3000/api/health
HTTP 200
[Asserts]
jsonpath "$.status" == "ok"

Run it:

hurl health.hurl

Hurl: POST with JSON body and response validation

POST http://localhost:3000/api/users
Content-Type: application/json
{
  "name": "Alice",
  "email": "alice@example.com"
}
HTTP 201
[Asserts]
jsonpath "$.id" isInteger
jsonpath "$.name" == "Alice"

Hurl: Chained requests (auth → create → verify)

# Step 1: Login
POST http://localhost:3000/api/auth/login
Content-Type: application/json
{
  "email": "admin@example.com",
  "password": "secret"
}
HTTP 200
[Captures]
token: jsonpath "$.token"

# Step 2: Create resource with token
POST http://localhost:3000/api/items
Authorization: Bearer {{token}}
Content-Type: application/json
{
  "title": "New Item"
}
HTTP 201
[Captures]
item_id: jsonpath "$.id"

# Step 3: Verify resource exists
GET http://localhost:3000/api/items/{{item_id}}
Authorization: Bearer {{token}}
HTTP 200
[Asserts]
jsonpath "$.title" == "New Item"

Hurl: Run test suite with JSON report

hurl --test --report-json report/ tests/*.hurl

Hurl: Use variables from command line

hurl --variable host=https://staging.example.com --variable token=abc123 tests/api.hurl

httpx: Probe a list of URLs for status codes

echo -e "https://example.com\nhttps://httpbin.org\nhttps://nonexistent.invalid" | httpx -silent -status-code

httpx: Probe with full JSON output (status, title, tech)

echo "https://example.com" | httpx -json -title -tech-detect -status-code

httpx: Check specific ports across hosts

echo -e "192.168.1.1\n192.168.1.2" | httpx -ports 80,443,8080 -status-code

httpx: Follow redirects and show final URL

echo "http://github.com" | httpx -follow-redirects -location -status-code

Pipelines

Hurl test suite → summarize failures

hurl --test --report-json report/ tests/*.hurl 2>&1; jq '[.[] | select(.success == false) | {file: .filename, errors: [.entries[] | select(.errors | length > 0) | .errors]}]' report/*.json

Each stage: Hurl runs all tests and writes JSON reports, jq filters to failures and extracts error details.

Discover endpoints with Katana → probe with httpx

katana -u https://example.com -silent -d 2 | httpx -silent -status-code -json

Each stage: Katana crawls and discovers URLs, httpx probes each for status and metadata.

Prefer Over

  • Prefer Hurl over curl scripts for multi-step API testing — declarative syntax with built-in assertions, no bash scripting needed
  • Prefer Hurl over Postman/Bruno for CI-friendly test suites — plain text files, no GUI dependency
  • Prefer httpx over curl loops for probing many URLs — concurrent, structured output, built for scale

Do NOT Use When

  • Need full browser rendering or JavaScript execution — use web-crawling skill (Playwright)
  • Building a long-running API client or SDK — write code instead
  • Testing WebSocket or gRPC endpoints — use specialized tools (wscat, grpcurl)
  • Single ad-hoc curl request — just use curl directly

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 6 months ago
What it can do
Runs commands Reads files Edits files
version
1.0.0
author
ykotik
All 5 allowed tools
Bash(hurl*)Bash(httpx*)ReadWriteGlob

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/api-testing