Http Status Guide

Pick the HTTP status code an API should return for a given outcome, and settle the cases where two codes both look defensible — 401 vs 403, 400 vs 422, 404 vs 403 for hidden resources, 409 vs 422 for conflicts. Use when designing REST endpoints, reviewing an API's error handling, or debugging a client that mishandles a response.

5 starsSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add tomada1114/tomada-claude-plugins

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add tomada1114/tomada-claude-plugins --skill http-status-guide
Manual install
git clone --depth 1 https://github.com/tomada1114/tomada-claude-plugins.git /tmp/tomada-claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/tomada-claude-plugins/tomada-kit/skills/creating-agent-skills/examples/http-status-guide ~/.claude/skills/http-status-guide

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# HTTP Status Guide

Demonstrates progressive disclosure: the body carries the decision, `references/` carries the detail. The reference is read only when the decision needs it.

## Procedure

1. Name the outcome in one sentence — what the server did, not what the client asked for. "Created a row" and "rejected because the email is taken" pick different codes.
2. Map it with the table below.
3. If the outcome is one of the contested pairs, read [references/http-status-codes.md](references/http-status-codes.md) — it resolves each pair and gives the response body shape.

## Table

| Outcome | Code |
|---|---|
| Read succeeded, body attached | 200 |
| Resource created | 201 + `Location` |
| Accepted, work happens later | 202 |
| Succeeded, deliberately no body | 204 |
| Request is malformed — unparseable, wrong content type | 400 |
| Caller is unidentified or the credential expired | 401 + `WWW-Authenticate` |
| Caller is identified and still not permitted | 403 |
| No such resource, and admitting that is safe | 404 |
| Syntax is fine, the values violate a business rule | 422 |
| Rate limited | 429 + `Retry-After` |
| Unhandled server fault | 500 |
| Dependency down or deploy in progress | 503 + `Retry-After` |

Two rules the table cannot show: never return 200 with an error payload, and never leak existence through the status code — an unauthorized read of a resource the caller may not know about returns 404, not 403.
Read the full skill on GitHub

Details

Skill name
http-status-guide
Path
tomada-kit/skills/creating-agent-skills/examples/http-status-guide/SKILL.md
Repo updated
12 November 2026

FAQ

What does the Http Status Guide skill do?

Pick the HTTP status code an API should return for a given outcome, and settle the cases where two codes both look defensible — 401 vs 403, 400 vs 422, 404 vs 403 for hidden resources, 409 vs 422 for conflicts. Use when designing REST endpoints, reviewing an API's error handling, or debugging a client that mishandles a response.

How do I install the Http Status Guide skill?

Claude Code plugin: /plugin marketplace add tomada1114/tomada-claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Http Status Guide popular?

It lives in tomada1114/tomada-claude-plugins, which has 5 GitHub stars and 0 forks.

Related skills

Auditing Prompt Docs

5

tomada1114/tomada-claude-plugins

Audit and fix prompt-bearing documents — SKILL.md, CLAUDE.md, AGENTS.md, agent and command definitions, reference files, whole repositories — against Anthropic's published prompting guidance for current Claude models, proposing edits for approval before writing anything. Also answers how to prompt a specific model: holds the per- model guidance for Claude Fable 5.2, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 alongside the cross-model practices. Use when reviewing or slimming an instruction file, when instructions are ignored or fire too often, when migrating a prompt to a newer m

AI, LLMs & Agents

Auditing Repositories

5

tomada1114/tomada-claude-plugins

Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst

Testing & QA

Authoring Goal Prompts

5

tomada1114/tomada-claude-plugins

Author a self-contained prompt for Claude Code's /goal command, run unattended in a separate session — a lead-to-staff handoff where this session researches, designs, and decides with full context, and a fresh executor session (Opus 5.5 or Fable 5.2, with none of that context) implements. Drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules; packages design intent, code examples, research findings, checklists, and pre-answered decisions as support files in a per-goal state directory whenever the executor would otherwise re-de

AI, LLMs & Agents

Issues

5

Magnus-Gille/claude-skills

Inspect current-repository tickets in Plane (via the tickets MCP tools, else the tix CLI) or prepare a specifically requested routed ticket. Use when the user asks to list, view, filter, search, or create an issue or ticket.

Software Development

Friction Triage

5

Magnus-Gille/claude-skills

Triage accumulated Munin friction and prepare or file consolidated Plane tickets routed to their owning repos. Use when the user explicitly asks to review friction signals or turn them into tickets.

Software Development

Project Validator

5

tomada1114/tomada-claude-plugins

Check a Node project for the setup failures that surface later as confusing runtime errors — malformed package.json, uninstalled node_modules, missing .env, uninitialized git — and scaffold the missing pieces. Use when onboarding to an unfamiliar repo, bootstrapping a new project, or diagnosing "it works on my machine".

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.