rest-api-testing

Test REST APIs with file-based requests and assertions via the api-rest CLI.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/graysurf/agent-kit --skill rest-api-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rest-api-testing
Source: https://github.com/graysurf/agent-kit/tree/main/skills/tools/testing/rest-api-testing
Command: npx skills add https://github.com/graysurf/agent-kit --skill rest-api-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires nils-cli, jq, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of testing REST APIs, making it repeatable, verifiable, and easy to integrate into CI/CD pipelines, eliminating the guesswork and manual effort of API validation.

Core Features & Use Cases

  • Repeatable Requests: Define API requests in JSON files for consistent execution.
  • CI-Friendly Assertions: Embed assertions directly in request files to automatically validate responses.
  • Report Generation: Create markdown reports of test runs for documentation and review.
  • Use Case: Automatically test your application's /users endpoint by sending a POST request with specific data, asserting that the response status is 201 and that the returned user object contains the expected fields.

Quick Start

Use the rest-api-testing skill to call the 'health.request.json' request file.

Frequently Asked Questions about rest-api-testing

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

FAQPage Schema
How do I automate REST API testing in a CI/CD pipeline?

You can automate REST API testing in CI/CD by defining repeatable requests in JSON files with embedded assertions. The skill executes these file-based requests and generates test reports, ensuring reliable validation without manual effort.

What is the best way to make repeatable REST API requests with assertions?

The best way to make repeatable REST API requests is by defining them in JSON files. You embed assertions directly within these request files to automatically validate response statuses and payload fields during execution.

Can I use Bearer token authentication and endpoint presets for API testing?

Yes, you can use Bearer token authentication and endpoint presets for API testing. The skill supports per-project configurations, allowing you to preset endpoints and tokens for consistent and authenticated request execution.

How do I generate API test reports for manual calls and validation?

You generate API test reports by running your file-based requests through the CLI. The skill automatically creates markdown reports of your test runs, providing clear documentation for review and verifying manual API calls.

Do I need jq and nils-cli installed to test REST APIs with file-based requests?

You need jq and nils-cli installed to test REST APIs with file-based requests using this skill. These dependencies provide the underlying command-line execution environment required to run the api-rest CLI and process data.

How does file-based API testing compare to other automation tools?

File-based API testing stores requests as JSON files rather than in a GUI, enabling version control and CI integration. This approach ensures request replayability and verifiable assertions without the overhead of heavier automation frameworks.