← 返回 Skills 市场
tobewin

Http Status

作者 ToBeWin · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ 安全检测通过
171
总下载
0
收藏
1
当前安装
1
版本数
在 OpenClaw 中安装
/install 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...
使用说明 (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

  1. Check references/codes.md for the exact code
  2. If not found, infer from the range (4xx = client error, 5xx = server error)
  3. Note the source category: RFC standard / WebDAV / Nginx / Cloudflare / unofficial
  4. 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
安全使用建议
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.
功能分析
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.
能力评估
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.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install http-status
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /http-status 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
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.
元数据
Slug http-status
版本 1.0.0
许可证 MIT-0
累计安装 1
当前安装数 1
历史版本数 1
常见问题

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... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 171 次。

如何安装 Http Status?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install http-status」即可一键安装,无需额外配置。

Http Status 是免费的吗?

是的,Http Status 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Http Status 支持哪些平台?

Http Status 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Http Status?

由 ToBeWin(@tobewin)开发并维护,当前版本 v1.0.0。

💬 留言讨论