rest-graphql-debug

Diagnose REST and GraphQL APIs across connectivity, authentication, and schema validation.

Updated May 20, 2026
One-click install
npx skills add https://github.com/SriRamkunamsetty/SITA2.0-HermesAgent --skill rest-graphql-debug-sriramkunamsetty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rest-graphql-debug
Source: https://github.com/SriRamkunamsetty/SITA2.0-HermesAgent/tree/main/hermes-agent/optional-skills/software-development/rest-graphql-debug
Command: npx skills add https://github.com/SriRamkunamsetty/SITA2.0-HermesAgent --skill rest-graphql-debug-sriramkunamsetty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

REST and GraphQL API debugging and validation bottlenecks, slowing diagnosis of failures across endpoints, auth, and response schemas.

Core Features & Use Cases

  • Provides layered debugging guidance for REST and GraphQL APIs, including status codes, authentication, and schema validation.
  • Offers practical workflows to isolate connectivity, TLS, auth, request formatting, and response parsing issues using Hermes tools.
  • Suitable for API integration testing, outage triage, and reliability improvements across microservices.

Quick Start

Run an API health check and validate REST/GraphQL responses end-to-end.

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 REST API failures by isolating connectivity and authentication layers?

To debug REST API failures, isolate connectivity, TLS, authentication, and request formatting layers using guided checks. Leverage terminal for curl commands and execute_code for Python requests to validate HTTP status codes and response schemas end-to-end.

What is the best way to validate GraphQL API responses and schema during integration testing?

The best way to validate GraphQL API responses is by applying layered debugging checks to schema validation and end-to-end repros. Extract API docs using web_extract to verify response structures against expected schemas during integration testing.

Why does my REST API return unexpected HTTP status codes and how can I diagnose them?

Unexpected HTTP status codes are diagnosed by running API health checks that isolate the failing layer. Apply guided checks to status codes, authentication, and request formatting using terminal curl commands to reproduce and trace the exact failure point.

Can I use Python requests and curl to triage microservice API outages?

Yes, you can triage microservice API outages using terminal for quick curl commands and execute_code for Python requests. These Hermes tools help isolate connectivity, TLS, and authentication issues across REST and GraphQL endpoints during outage triage.

What should I do when my GraphQL API authentication fails during end-to-end testing?

When GraphQL API authentication fails, isolate the authentication layer by validating credentials and request headers. Use web_extract to pull API documentation and verify authentication schemes, then run guided checks to reproduce the failure across endpoints.

Do I need to pull API documentation manually before debugging REST and GraphQL endpoints?

No, you do not need to pull API documentation manually before debugging REST and GraphQL endpoints. The web_extract tool fetches API docs automatically, enabling guided checks for schema validation, authentication, and status codes during diagnosis.