rest-graphql-debug
Skill2 starsChanged 57 days agoMITView on GitHub
Debug REST/GraphQL API failures — status codes, auth, TLS, schema drift, pagination — by isolating the failing layer before guessing at a fix. Use when an API returns an unexpected status or body, auth fails after a token refresh, something works in Postman but fails in code, or you're reviewing/writing API integration tests.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nobodyohm-web/Thottheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nobodyohm-web/Thot★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-auditSkill
- app-designSkill
- cloudflare-temporary-deploySkill
- code-reviewSkill
- codex-delegateSkill
- commit-documentorSkill
- constructorSkill
- datasecurerSkill
- dependabot-validatorSkill
- dogfoodSkill
- flask-testsSkill
- ideatorSkill
- lan-viewerSkill
- memorySkill
- ollama-delegateSkill
- pr-grill-meSkill
- system-oneSkill
- web-pentestSkill
- workflow-rulesSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use an available HTTP tool or shell with curl.
- Distinctive: line 12
Do not install dependencies into the user's environment implicitly.
- Distinctive: line 24
Read only the relevant lookup:
- Distinctive: line 33
Use explicit timeouts. Redact tokens, cookies, personal data, and secrets from all shared evidence.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
REST and GraphQL debugging
Diagnose the smallest reproducible failing request. Confirm target, expected
behavior, credentials source, and whether state-changing requests are authorized.
Use an available HTTP tool or shell with curl. Python examples require the
optional requests package; check before use and prefer curl if unavailable.
Do not install dependencies into the user's environment implicitly.
- Capture the failing request, status, headers, request ID, and sanitized body.
- Work outward-in: connectivity → timeouts → TLS → authentication → request format → response parsing → business semantics. Change one variable at a time.
- For GraphQL, inspect
errorseven on HTTP 200. A transport success does not establish a successful operation. - Reproduce a fix and verify failure cases, pagination, or idempotency where relevant. Do not retry state-changing requests without establishing safety.
- Report observed vs expected behavior, sanitized repro, root cause confidence, proposed fix, and tests run/not run. Never expose credentials in logs or chat.
Read only the relevant lookup:
- Quickstart: curl and optional Python examples.
- Layered diagnosis: connectivity through semantics.
- Status playbook: 401/403/404/409/422/429/5xx.
- Contracts and regression: pagination, schemas, correlation IDs, and test examples.
- Credential handling: read before handling secrets.
Use explicit timeouts. Redact tokens, cookies, personal data, and secrets from all shared evidence. Preserve TLS validation; diagnostic bypasses do not count as a production fix.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.