http-error-triage SKILL.md skillA

http-error-triage from getedgehq/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add getedgehq/skills/http-error-triage@git:20260910.badf951

Pins git:20260910.badf951 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

getedgehq/skills

Path

http-error-triage/SKILL.md

Versions recorded

1

Latest version

git:20260910.badf951, committed Sep 10, 2026

Size

3,945 bytes

Repository stars

5

License

Apache-2.0

Run before concluding anything from an HTTP error on a third-party API. Separates a real credential/entitlement problem from a CDN or WAF block, a wrong endpoint, or a client-signature ban. Use whenever an API returns 401/403/402/429 and you are about to say "the key is dead", "credits are exhausted", "the plan lacks access", or "we are rate limited".

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# HTTP error triage

An HTTP error tells you a request failed. It usually does **not** tell you why.
Concluding "the key is dead" from a 403 is a guess wearing a number.

Born from a real incident (2026-07-30): a third-party contact-enrichment API
returned `403 error code: 1010` to every call for six days. It was read as "key
not entitled", "credits exhausted", "monthly quota reached". A 756-line browser
automation workaround was built on that belief, and a customer was nearly asked
to check a plan that was fine. The actual cause was a missing `User-Agent`, so
the CDN banned the client at the edge. One header fixed it: 200 OK, full data,
and the credit balance had been there the whole time.

## Run these three controls before you diagnose

**1. The invalid-credential control.** Send the same request with a deliberately
garbage credential, and again with none at all.

```python
for label, key in [("real", REAL_KEY), ("garbage", "0"*36), ("empty", "")]:
    ...  # same URL, same method, same headers
```

If all three return the **same** status and body, the error is not about your
credential. It carries zero information about entitlement, quota or validity.
…

Read the whole file at its exact version.

How to install

mdr add getedgehq/skills/http-error-triage@sha256:0e05ddb904fa0979

[![mdr](https://markdownregistry.com/badge/art_3hs6kbn7ebiz7qpc.svg)](https://markdownregistry.com/a/art_3hs6kbn7ebiz7qpc)

Versions

The registry has recorded 1 version of this file, committed on Sep 10, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_3hs6kbn7ebiz7qpc
GET https://markdownregistry.com/api/v1/resolve?ref=getedgehq/skills/http-error-triage
GET https://markdownregistry.com/api/v1/blob/0e05ddb904fa0979b255b7bdde3b8af1397f068ce5b84917a800e727b696cab3

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from getedgehq/skills

Every file in getedgehq/skills

Other files named http-error-triage

Browse by kind, by grade A, or by owner.