rest-graphql-debug

Diagnose REST and GraphQL API failures by isolating layers from connectivity to data semantics.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/AnandaAnugrahHandyanto/savarez_agent --skill rest-graphql-debug-anandaanugrahhandyanto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rest-graphql-debug
Source: https://github.com/AnandaAnugrahHandyanto/savarez_agent/tree/main/optional-skills/software-development/rest-graphql-debug
Command: npx skills add https://github.com/AnandaAnugrahHandyanto/savarez_agent --skill rest-graphql-debug-anandaanugrahhandyanto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging REST and GraphQL API issues by systematically isolating layers from network connectivity to data interpretation, reducing guesswork and speeding recovery.

Core Features & Use Cases

  • Layered debugging workflow for connectivity, TLS/SSL, authentication, request formatting, response parsing, and semantic validation.
  • Guidance and templates for common error scenarios (401, 403, 404, 5xx) and how to surface correlation IDs for rapid triage.
  • Practical use with curl, Python requests, and vendor docs (web_extract) to confirm behavior and reproduce failures.

Quick Start

Run a curl command to a failing endpoint and inspect the response to identify the earliest failure point

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 with unexpected HTTP status codes?

To debug REST API failures, isolate layers from connectivity to data semantics using curl and Python requests. This workflow diagnoses unexpected statuses, authentication errors, and response parsing issues by identifying the earliest failure point.

What is the best way to troubleshoot GraphQL schema mismatches and authentication errors?

Troubleshooting GraphQL schema mismatches involves a layered debugging workflow using execute_code and web_extract patterns. It isolates authentication failures and data interpretation issues against vendor documentation to speed recovery.

Why does my API request return a 401 or 403 error and how can I fix it?

API requests return 401 or 403 errors due to authentication failures or misconfigured request formatting. Diagnose these issues by inspecting curl responses and verifying credentials against vendor documentation to surface correlation IDs for triage.

How do I troubleshoot slow API responses and connectivity issues?

Troubleshoot slow API responses by isolating network connectivity and TLS/SSL layers before validating data semantics. Use curl commands to inspect endpoint behavior and identify latency bottlenecks across the request lifecycle.

Can I use this debugging workflow with Python requests and curl for API testing?

Yes, this debugging workflow supports API testing with Python requests and curl. It provides practical templates to reproduce failures, inspect HTTP status codes, and validate pagination behavior across terminal and execute_code environments.

How do I extract correlation IDs from API responses for rapid error triage?

Extract correlation IDs from API responses by parsing headers and body payloads during the response inspection phase. This workflow provides guidance on surfacing these identifiers to rapidly triage 5xx errors and connectivity failures.