Error
v1.0.0Error handling reference — error types, exception patterns, HTTP status codes, retry strategies, and observability. Use when designing error handling, debugg...
⭐ 0· 89·0 current·0 all-time
byBytesAgain2@ckchzh
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (error-handling reference) matches the provided assets: an instruction-only skill that calls a bundled scripts/script.sh which prints documentation for error handling, HTTP status codes, retry strategies, logging, etc. There are no unexpected credentials, binaries, or external services required.
Instruction Scope
SKILL.md directs the agent to run local commands like `scripts/script.sh intro` and other subcommands. The included script appears to only output reference text (cat << 'EOF' blocks) for each command. The instructions do not ask the agent to read unrelated system files, access external endpoints, or collect user secrets.
Install Mechanism
No install spec is provided and the skill is instruction-only with a local script. Nothing is downloaded or extracted from remote URLs, so there is no elevated install risk.
Credentials
The skill declares no required environment variables or credentials. SKILL.md documents an optional ERROR_DIR (default ~/.error/) for data, which is reasonable for a doc/reference skill; no sensitive secrets are requested.
Persistence & Privilege
always is false and the skill does not request permanent system presence. The skill will only run when invoked and does not modify other skills or global agent configuration.
Assessment
This skill appears to be a local documentation tool implemented as a bundled shell script that prints error-handling guidance. It is coherent with its description and doesn’t request credentials or network access. Before installing or running: (1) quickly review scripts/script.sh yourself to confirm it only prints text (search for network commands like curl, wget, nc, ssh or file-write operations), (2) avoid running it as an elevated user (root) if you have concerns, and (3) if you expect persistent data, check how ERROR_DIR is used and whether files are written there. If you want extra assurance, run the script in an isolated environment (container) and inspect its output and any files it creates.Like a lobster shell, security has layers — review code before you run it.
latestvk972c3xjfr925vvke35hyhp71h83bpte
License
MIT-0
Free to use, modify, and redistribute. No attribution required.