rest-graphql-debug

Isolate failures in REST and GraphQL API requests across connectivity, TLS, auth, and parsing.

Updated Apr 9, 2026

Search Tags:#authentication #integration testing #rest #graphql #curl #api debugging #http status codes

Ready to run

npx skills add https://github.com/MarbleSodas/Mavis --skill rest-graphql-debug-marblesodas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rest-graphql-debug
Source: https://github.com/MarbleSodas/Mavis/tree/main/optional-skills/software-development/rest-graphql-debug
Command: npx skills add https://github.com/MarbleSodas/Mavis --skill rest-graphql-debug-marblesodas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly identify why a REST or GraphQL request fails, especially when symptoms are misleading (like HTTP 200 hiding GraphQL errors).

Core Features & Use Cases

Layered API triage: Work systematically through connectivity, timeouts, TLS, authentication, request formatting, response parsing, and semantic validation.
REST + GraphQL specific debugging: Check HTTP status codes, and for GraphQL always inspect the errors field even when the HTTP status is 200.
Repro-ready techniques: Generate practical curl and Python requests to reproduce, isolate, and confirm fixes, including correlation-id capture for vendor escalation.

Quick Start

Tell the AI: "Debug this API call by checking connectivity, TLS, auth validity, request/response format, GraphQL errors (if applicable), and produce a minimal reproduction plus likely root cause."

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 GraphQL API request that returns HTTP 200 but contains errors?▼

To debug GraphQL API errors on HTTP 200, inspect the response body's errors field specifically, as GraphQL returns a 200 status even when semantic failures occur. Systematic isolation checks response parsing and schema semantics to find the root cause.

What is the best way to troubleshoot unexpected REST API HTTP status codes and authentication failures?▼

Troubleshooting REST API HTTP status codes and authentication failures requires a layered triage approach, checking connectivity, TLS certificates, and header or content-type verification. This isolates whether the break occurs at the network, authorization, or request formatting level.

How do I create a minimal curl reproduction for a failing webhook callback or API integration test regression?▼

Create repro-ready curl commands or Python requests to isolate the failing API integration test or webhook callback. Capturing correlation-ids during reproduction confirms fixes and provides necessary context for vendor escalation.

Why does my API request fail with rate limiting or pagination bugs during integration testing?▼

API integration testing failures from rate limiting or pagination bugs occur due to semantic validation breaks or request formatting issues. Step-by-step inspection of HTTP headers and GraphQL conventions isolates the exact request layer causing the failure.

Can I use terminal and execute_code to diagnose schema drift and TLS issues in API requests?▼

Yes, you can use terminal and execute_code tooling to diagnose schema drift and TLS connectivity issues. Reproduction-focused terminal commands verify TLS handshakes and validate API request formatting across connectivity and semantic layers.