api-test

Construct terminal-based REST API tests using environment variables instead of secrets.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/fxckcode/skills-kit --skill api-test-fxckcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-test
Source: https://github.com/fxckcode/skills-kit/tree/main/skills/api-test-skill
Command: npx skills add https://github.com/fxckcode/skills-kit --skill api-test-fxckcode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Enables secure, terminal-based REST API testing across Windows, macOS, and Linux by constructing commands that reference environment variables rather than embedding secrets, reducing exposure and cross-OS friction.

Core Features & Use Cases

  • OS-aware request construction that references environment variables (never literals) and supports curl, httpie, or Invoke-RestMethod across Windows, macOS, and Linux.
  • Automated response interpretation with status classification, header/body parsing, pagination signals, and error diagnosis plus optional chaining and assertions.
  • Trigger-friendly workflow: test endpoints, run end-to-end API chains, and verify responses in production or development environments.

Quick Start

Provide a target API URL and let the skill execute a safe test against it.

Frequently Asked Questions about api-test

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

FAQPage Schema
How do I test REST APIs from the terminal without exposing API keys?

Test REST APIs from the terminal securely by constructing commands that reference environment variables rather than embedding secrets directly. This approach prevents accidental exposure of sensitive credentials across Windows, macOS, and Linux environments.

Does terminal API testing work across different operating systems and HTTP clients?

Terminal API testing works across Windows, macOS, and Linux by automatically detecting the OS and available HTTP clients. It supports curl, httpie, or Invoke-RestMethod to construct and execute requests regardless of the platform.

How do I automate response interpretation and pagination handling for API testing?

Automate response interpretation for API testing by executing requests and parsing status classifications, headers, and body content. The workflow detects pagination signals and diagnoses errors to provide comprehensive end-to-end response analysis.

Can I run end-to-end API chains and evaluate assertions in the terminal?

You can run end-to-end API chains in the terminal by linking multiple requests and evaluating all-assertions. The workflow supports request chaining and assertion evaluation to verify complex API interactions and production workflows.

What is the best way to redact secrets during automated API testing?

The best way to redact secrets during automated API testing is using a two-stage secret redaction process. This mechanism ensures sensitive data remains masked while constructing requests with environment variable references and interpreting responses.