rest-graphql-debug

Diagnoses REST and GraphQL API integration failures through layered verification of connectivity, TLS, authentication, request formatting, and parsing.

1|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/icyzh/hermes-web --skill rest-graphql-debug-icyzh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rest-graphql-debug
Source: https://github.com/icyzh/hermes-web/tree/main/optional-skills/software-development/rest-graphql-debug
Command: npx skills add https://github.com/icyzh/hermes-web --skill rest-graphql-debug-icyzh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests.

What problem does it solve?

This skill eliminates the guesswork in API troubleshooting by providing a structured, layer-by-layer diagnostic framework for REST and GraphQL services.

Core Features & Use Cases

  • Layered Diagnosis: Systematically verify connectivity, TLS, authentication, request formatting, and response parsing.
  • Tool Integration: Seamlessly switch between terminal-based curl commands and Python-based request scripts for complex debugging.
  • Use Case: When an API returns an unexpected 401 or 422 error, use this skill to isolate whether the issue lies in the authentication header, the payload schema, or the server-side validation logic.

Quick Start

Use the rest-graphql-debug skill to perform a verbose curl request against the target endpoint to identify the root cause of the connection failure.

Frequently Asked Questions about rest-graphql-debug

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

FAQPage Schema
How do I debug a REST API returning an unexpected 401 or 422 error?

Debug unexpected REST API 401 or 422 errors by systematically verifying authentication headers, request payload schemas, and server-side validation logic layer by layer to isolate the exact failure point.

What is the best way to isolate GraphQL API connectivity and schema validation failures?

Isolate GraphQL API connectivity and schema validation failures by systematically verifying endpoint connectivity, TLS certificates, and query schemas through structured terminal network diagnostics and Python request simulation.

How do I use curl and Python requests to troubleshoot HTTP API integration issues?

Troubleshoot HTTP API integration by executing verbose curl commands for initial network diagnostics, then switching to Python requests scripts to simulate complex payloads and validate response parsing.

Do I need terminal access to diagnose REST and GraphQL API issues in production?

Diagnosing REST and GraphQL API issues in production requires terminal access for executing curl network diagnostics and Python capabilities to simulate complex requests and validate API contracts.

Why does my API request fail during response parsing after a successful connection?

API response parsing fails after successful connections when the returned payload schema mismatches the expected format, requiring systematic layer-by-layer verification of request formatting and response contract validation.