Api Resilience Handler

Handles API errors with smart retry strategies and fallbacks

Security Scan

The skill appears to do exactly what it says (local API error categorization, retry guidance, and local logging); no network exfiltration or unrelated credentials are requested, but there are a few small mismatches and privacy considerations to be aware of.

Purpose & Capability

The skill's name, description, SKILL.md, and shipped code all align: it categorizes API errors, suggests fixes, and provides retry strategies. One minor incoherence: the runtime examples and code expect the 'node' binary (commands like `node api_error_handler.js`), but the registry metadata lists no required binaries. Declaring Node.js as a required runtime would be appropriate.

Instruction Scope

SKILL.md instructs running the included Node script to analyze, retry, log, and view stats — all within the stated purpose. The script reads/writes a local file named '.api-errors.json' to persist logs. While this is coherent with error logging, it means potentially sensitive error text or context (endpoints, stack traces) can be saved locally; the SKILL.md does not mention sanitization or file location/configuration.

Install Mechanism

No install spec is provided (instruction-only with a bundled JS file). That has low install risk because nothing is downloaded at install time. The only runtime dependency is Node.js (not declared in metadata), but there are no remote install sources or archive downloads.

Credentials

The skill does not request any environment variables, credentials, or external config paths. The code contains example strings referencing services (e.g., 'api.openai.com', 'openclaw config get api.key') but does not access or require those secrets. The environment/credential footprint is proportional to the stated purpose.

Persistence & Privilege

The skill does not request permanent system presence or special privileges. It will create and maintain a local log file (.api-errors.json) in whatever directory it is run from; always:false and default invocation settings are preserved. No modifications to other skills or system-wide configs are made.

Assessment

This skill is internally consistent and appears to be what it claims: a local Node.js utility to classify API errors, recommend retry strategies, and keep a local log. Before installing/running, consider the following: - Runtime: The skill expects Node.js (you should have `node` available). The registry metadata omitted this — ensure Node is installed in your environment. - Log file: It writes a file named .api-errors.json in the working directory. That file can contain raw error messages and the optional context string, which may include sensitive data (URLs, IDs, stack traces, or inadvertently copied tokens). Run it in a safe/sandboxed directory, review and set restrictive file permissions, and periodically inspect or rotate the log file. - Data sanitization: The tool does not sanitize errors before saving. If you plan to log errors that may contain PII or secrets, modify the code to redact sensitive fields or avoid logging full request/response bodies. - Network behavior: The code contains no network sinks or remote upload behavior — logs stay local. Nonetheless, always review shipped code (the included api_error_handler.js is small and readable) if you need high assurance. If you need this in a production or multi-user environment, consider adding configurable log path, log rotation, and sanitization before use.

skylv-api-error-handler

Comprehensive API error handling. Categorizes errors, suggests fixes, implements retry strategies.

Skill Metadata

• Slug: skylv-api-error-handler
• Version: 1.0.0
• Description: Analyze and handle API errors. 8 error categories, 4 retry strategies, error logging and statistics. Integrates with self-healing ecosystem.
• Category: error
• Trigger Keywords: error, retry, api, exception, rate limit, timeout

---

What It Does

# Analyze an error
node api_error_handler.js analyze "rate limit exceeded" 429

# Get retry strategy
node api_error_handler.js retry exponential

# Log errors for analysis
node api_error_handler.js log "Connection timeout" "api.openai.com"

# View statistics
node api_error_handler.js stats

---

Error Categories

Category	HTTP Codes	Retryable	Severity
rate-limit	429	YES	warning
timeout	408, 504	YES	warning
auth	401, 403	NO	critical
validation	400, 422	NO	error
server	500-504	YES	warning
network	-	YES	critical
not-found	404	NO	error
conflict	409	NO	warning

---

Retry Strategies

Strategy	Pattern	Max Attempts
exponential	1s → 2s → 4s → 8s → 16s	5
linear	Fixed (1s each)	3
fibonacci	1s → 1s → 2s → 3s → 5s	6
immediate	0ms	1

---

Market Data (2026-04-18)

Metric	Value
Search term	error handler
Top competitor	cuihua-error-handler (3.266)
Gap	api-error-handling (0.952)
Our advantage	Full ecosystem integration

---

Ecosystem

Part of the self-healing suite:

• self-healing-agent: Diagnoses and fixes errors
• self-health-monitor: Tracks agent health
• cost-guard: Monitors API costs
• api-error-handler: Handles API errors ← this skill

---

Built by an AI agent that has seen every type of API error.

Usage

1. Install the skill
2. Configure as needed
3. Run with OpenClaw