← Back to Skills Marketplace
171
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install http-status
Description
HTTP status code reference — instant lookup of any status code with meaning, common causes, and fix suggestions. Use when the user asks about an HTTP status...
README (SKILL.md)
HTTP Status Code Reference
Instant lookup for any HTTP status code — meaning, common causes, and how to fix it.
Full data table in references/codes.md. Zero dependencies, fully offline.
When to use
- "What does 429 mean?"
- "I'm getting a 502 from my API, what's wrong?"
- "What's the difference between 401 and 403?"
- "Which 5xx errors are retryable?"
- "What does Cloudflare 524 mean?"
Code ranges (quick orientation)
1xx Informational — request received, continue processing
2xx Success — request was received, understood, accepted
3xx Redirection — further action needed to complete the request
4xx Client Error — request contains bad syntax or cannot be fulfilled
5xx Server Error — server failed to fulfil an apparently valid request
Lookup procedure
- Check
references/codes.mdfor the exact code - If not found, infer from the range (4xx = client error, 5xx = server error)
- Note the source category: RFC standard / WebDAV / Nginx / Cloudflare / unofficial
- Return: meaning + common causes + recommended action
Output format
Single code lookup
🔢 HTTP 429 — Too Many Requests
━━━━━━━━━━━━━━━━━━━━
Category: 4xx Client Error
Standard: RFC 6585
Meaning: The user has sent too many requests in a given time (rate limiting).
Common causes:
• API rate limit exceeded
• Burst traffic hitting a throttling policy
• Forgot to handle Retry-After header
What to do:
• Check the Retry-After response header for wait time
• Implement exponential backoff in your client
• Review your request frequency and add throttling logic
• Consider caching responses to reduce request volume
Related codes: 503 (server overloaded)
Comparison query
🔢 401 vs 403
━━━━━━━━━━━━━━━━━━━━
401 Unauthorized
→ Authentication is required and has failed or not been provided
→ "You need to log in first"
→ Fix: provide valid credentials / token
403 Forbidden
→ Server understood the request but refuses to authorize it
→ "You're logged in but don't have permission"
→ Fix: check user roles/permissions, contact admin
Key difference:
401 = identity unknown (not authenticated)
403 = identity known but access denied (not authorized)
Retryable codes
✅ Generally safe to retry (with backoff):
408 Request Timeout
429 Too Many Requests ← respect Retry-After header
500 Internal Server Error ← transient server issues
502 Bad Gateway ← upstream temporarily unavailable
503 Service Unavailable ← server overloaded/maintenance
504 Gateway Timeout ← upstream timeout
❌ Do NOT retry blindly:
400 Bad Request ← fix your request first
401 Unauthorized ← re-authenticate first
403 Forbidden ← retrying won't help
404 Not Found ← resource doesn't exist
422 Unprocessable Entity ← fix validation errors first
Notes
- For Nginx-specific codes (444, 494-499) and Cloudflare codes (520-530), see
references/codes.md - 418 "I'm a teapot" is a real RFC 2324 status — implemented as an Easter egg in some servers
- Some codes (e.g. 103, 425, 451) are newer and may not be supported by all clients/proxies
Usage Guidance
This skill is a self-contained, offline reference and appears safe to install. Consider: (1) the included references/codes.md is static—if you need the very latest RFCs or provider-specific codes, verify currency; (2) MIT-0 license lets you reuse the content; (3) because it can be invoked autonomously (normal default), ensure you trust the skill owner if you allow agents to act without prompts—though this particular skill has no network or credential access. If you require automatic updates, prefer a skill with a documented, trusted source or an explicit update mechanism.
Capability Analysis
Type: OpenClaw Skill
Name: http-status
Version: 1.0.0
The 'http-status' skill is a purely informational reference tool for HTTP status codes. It contains no executable code, only markdown documentation and a comprehensive lookup table in 'references/codes.md', with no evidence of malicious intent or risky behaviors.
Capability Assessment
Purpose & Capability
The name/description match the content: a reference/lookup for HTTP status codes. The skill requires no binaries, env vars, or external services and provides a large included reference file (references/codes.md) that supports the stated purpose.
Instruction Scope
SKILL.md instructs the agent to consult the included references/codes.md and, if needed, infer from ranges. It does not request reading unrelated system files, accessing environment variables, or making network calls. Output format and examples are narrowly scoped to status-code lookups.
Install Mechanism
There is no install spec and no code files to install; this is instruction-only. That minimizes disk writes and runtime install risk.
Credentials
The skill requests no environment variables, credentials, or config paths. Nothing included appears disproportionate to an offline reference lookup.
Persistence & Privilege
always is false and the skill does not attempt to modify other skills or system configuration. Autonomous invocation is allowed (platform default) but does not add unexpected privileges for this offline reference.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install http-status - After installation, invoke the skill by name or use
/http-status - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of **http-status**: an instant, offline reference for all HTTP status codes.
- Provides lookup of meaning, common causes, and fix suggestions for any standard or unofficial code.
- Covers RFC, WebDAV, Nginx, Cloudflare, and other commonly used codes.
- Supports single-code explanations, code comparisons (e.g. 401 vs 403), and lists of retryable errors.
- No network, no dependencies — works fully offline.
Metadata
Frequently Asked Questions
What is Http Status?
HTTP status code reference — instant lookup of any status code with meaning, common causes, and fix suggestions. Use when the user asks about an HTTP status... It is an AI Agent Skill for Claude Code / OpenClaw, with 171 downloads so far.
How do I install Http Status?
Run "/install http-status" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Http Status free?
Yes, Http Status is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Http Status support?
Http Status is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Http Status?
It is built and maintained by ToBeWin (@tobewin); the current version is v1.0.0.
More Skills