API Error Handler Skill for Problem Details Responses

Centralize API error mapping in Claude Code and provide clients with a consistent response shape and trace identifier.

Install in Claude Code

Use your own local API, a test client, and the project's error contract. The example uses application/problem+json.

Get the complete `plugins/api-development/api-error-handler/skills/handling-api-errors` directory from the pinned GitHub commit.
Copy it into the target project's `.claude/skills/`. Check `.claude/skills/handling-api-errors/SKILL.md`, start Claude Code at the project root, and call `/handling-api-errors`.

Example task

Request /products/7, /products/-1, and /products/999. Verify success, invalid input, and missing-resource behavior, then inspect type, title, status, and requestId on errors.

What to check

The statuses are 200, 400, and 404. Each error has a distinguishable type and a request identifier for log lookup.

Original SKILL.md on GitHub · Updated 2026-11-13

Frequently asked question

Should a client branch on the readable title?

Use a stable type or agreed business error code for logic. Use title for human-readable presentation.