Individual skill

error-handling-security

Decide what an error tells the client and what stays server-side: no stack traces, SQL, or paths in responses, no silent suppression, and no distinction between outcomes that would reveal protected state. Use when generating HTTP, GraphQL, or RPC error handlers, exception, panic, or rescue blocks, or configuring production error pages.

skills/error-handling-security/SKILL.md

Read pinned source

Source commit eaba88102d91df65a9aa6397e8507c315c018f5e

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings): 23
Repository last updated: Aug 14, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-skills Repository topic
llm Repository topic
security Repository topic
skills Repository topic
data Derived category
data-databases Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 6,403 bytes
references/framework-error-pages.mddoc · 3,863 bytes
references/verifying-findings.mddoc · 3,206 bytes
rules/error_response_template.jsonasset · 1,330 bytes
tests/corpus.jsonasset · 4,094 bytes

Read excerpt


# Error-Handling Security

## Rules (for AI agents)

### ALWAYS
- Catch exceptions at the boundary — HTTP handler, RPC method, message consumer —
  and decide *there* what crosses to the client and what stays server-side. Record
  the failure with a correlation ID under `logging-security`'s policy; do not bypass
  its redaction rules to attach "full context", which is how request bodies, cookies
  and tokens end up in logs.
- Put only client-actionable information in an external error: a stable error code, a
  short human-readable message, and the correlation ID. Anything the caller cannot
  act on belongs in the log entry that shares that ID.
- Keep responses **consistent within an error class**, and make security-equivalent