Agent skill · Backend & API

api-error-taxonomy

Define consistent API error codes and responses. Use when a mid-level developer needs error standardization.

majiayu000github.com/majiayu000GitHub ↗
codexclaude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill api-error-taxonomy-proflead-codex-skills-library-2 --agent codex

Same command for any agent — swap --agent for claude-code, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 1 KB
Bundled scripts: none
Path: skills/api/api-error-taxonomy-proflead-codex-skills-library-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# API Error Taxonomy ## Purpose Define consistent API error codes and responses. ## Inputs to request - Current error responses and status usage. - Client expectations for retries and messaging. - Logging and observability requirements. ## Workflow 1. List common error categories and HTTP mappings. 2. Define error payload shape and fields. 3. Set guidelines for logging and client messaging. ## Output - Error taxonomy table and examples. ## Quality bar - Ensure errors are machine-parseable. - Align retryable vs non-retryable semantics.

What's inside
Steps it walks through
  1. Purpose
  2. Inputs to request
  3. Workflow
  4. Output
  5. Quality bar
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the api-error-taxonomy skill do?

Define consistent API error codes and responses. Use when a mid-level developer needs error standardization.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill api-error-taxonomy-proflead-codex-skills-library-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going