Error Handling Patterns
CheckedImplements robust error handling patterns based on Herdiansah's techniques for resilient backend systems.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add herdiansah/antigravity-skills-master --skill error-handling-patterns -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
herdiansah
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned herdiansah/antigravity-skills-master at f642a05f9c.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- f642a05f9c
- Scanned
- 1 file, 622 lines
About this skill
What it does
This skill provides patterns and best practices for robust error handling in backend systems. It helps developers anticipate, gracefully manage, and log errors to improve application stability and maintainability. The skill focuses on practical implementation strategies rather than theoretical concepts.
When to use it
- When building a new API endpoint where you need to handle potential failures (e.g., database connection issues).
- During refactoring of existing code to improve error handling and logging practices.
- To standardize error responses across different microservices within an application.
- When debugging production errors and needing guidance on how to implement better error recovery mechanisms.
Key capabilities
- Provides patterns for structured error responses (e.g., consistent JSON format).
- Offers strategies for logging detailed error information without exposing sensitive data.
- Suggests techniques for implementing circuit breakers to prevent cascading failures.
- Includes guidance on handling specific error types, such as authentication failures or resource not found errors.
Example prompts
- "Show me a pattern for returning a 404 error in my API."
- "How can I implement retry logic with exponential backoff?"
- "What's the best way to log an error without including sensitive user data?"
Tips & gotchas
This skill assumes some familiarity with backend development concepts and common programming languages. While it provides patterns, adapting them to your specific technology stack will require careful consideration and potentially code modifications.