api-error-handling

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

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

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 examples)
│   └── validation-examples.md (input validation code)

Impact: +7 points easy. This single change addresses your biggest gap.

Other Things Worth Fixing

1. Add a table of contents. At the top of SKILL.md, add a quick TOC with links to main sections. For a 457-line file, this is navigation gold. (+2 points)

2. Beef up your description triggers. You've got 1-2 trigger phrases. Add more like "API retry logic," "error response handling," "HTTP timeout management." Better discoverability. (+1 point)

3. Expand feedback loops. You mention logging and monitoring, but add a section on validation patterns—how to detect bad responses before they cause problems downstream. Real-world crews need this. (+1 point)

Quick Wins

• Split SKILL.md into overview + references/ (biggest bang for your buck)
• Add table of contents to main file
• Expand trigger phrases in description metadata
• Add validation patterns section for feedback loops

You've built something useful here. These structural changes just make it discoverable and digestible at scale.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.