api-error-handling

12 stars

Implement comprehensive API error handling with standardized error responses, logging, monitoring, and user-friendly messages. Use when building resilient APIs, debugging issues, or improving error reporting.

Also in: monitoring

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →

Claude Code (CLI) Fast

skilz install aj-geddes/useful-ai-prompts/api-error-handling

OpenCode (CLI) Fast

skilz install aj-geddes/useful-ai-prompts/api-error-handling --agent opencode

OpenAI Codex (CLI) Native

skilz install aj-geddes/useful-ai-prompts/api-error-handling --agent codex

Gemini CLI (Project) Project

skilz install aj-geddes/useful-ai-prompts/api-error-handling --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents

For Claude Desktop Easy

Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

Manual Installation

1. Clone the repository:

git clone https://github.com/aj-geddes/useful-ai-prompts

2. Copy the agent skill directory:

cp -r useful-ai-prompts/skills/api-error-handling ~/.claude/skills/

Owner: aj-geddes (GitHub)
Repository: useful-ai-prompts
Stars: 12
Type: Technical
Meta-Domain: web api
Primary Domain: api
Market Score: 79

Agentic Skill Grades →

Agent Skill Grade

Score: 79/100 Click to see breakdown

Score Breakdown

Spec Compliance

12/15

PDA Architecture

15/30

Ease of Use

23/25

Writing Style

10/10

Utility

19/20

Areas to Improve

Lack of Layered Structure
Missing Table of Contents
No References Directory

Recommendations

Focus on improving Pda (currently 15/30)
Address 2 high-severity issues first
Add trigger phrases to description for discoverability

Graded: 2026-01-19

Developer Feedback

I took a look at your api-error-handling skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 79/100, solid C grade territory. This is based on Anthropic's skill best practices rubric. Your writing style is flawless (10/10) and utility is strong (19/20), but Progressive Disclosure Architecture is dragging things down (15/30). This is fixable with some structural changes.

What's Working Well

Writing is crisp. Your skill uses imperative voice consistently, zero marketing fluff. Every section earns its space.
Comprehensive error handling. You've thought through real API problems—timeout handling, rate limiting, validation errors. The code examples are practical and dense.
Consistent terminology. ApiError, ERROR_CODES, retry logic—everything lines up. Makes it easy to follow your logic.
Clear activation triggers. Your description nails the discoverability piece with specific trigger phrases like "API error handling" and "HTTP error codes."

The Big One: Layered Structure

Here's what's holding you back: Your 457-line SKILL.md is doing too much. It's got the overview and all the implementation details stuffed in one file. Progressive Disclosure is about scaling complexity gracefully—you're dumping it all at once.

The fix: Create a references/ directory and move your detailed code examples there. Keep SKILL.md as a concise overview (maybe 100-150 lines) that points to reference files for deep dives. Example structure:

api-error-handling/
├── SKILL.md (overview + workflow only)
├── references/
│   ├── error-codes-reference.md (ERROR_CODES constants)
│   ├── retry-strategies.md (backoff implementations)
│   ├── monitoring-patterns.md (logging...

Browse Category

More web api Agentic Skills

Report Security Issue

Found a security vulnerability in this agent skill?