Global error handling
Skill bg-szy/TOP-SKILLS/skills/marketplace/global-error-handling
全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard
npx -y skills add bg-szy/TOP-SKILLS --skill global-error-handlingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Implement user-friendly error handling with specific exception types, centralized error handling, graceful degradation, and proper resource cleanup. Use this skill when implementing error handling in controllers, services, or API endpoints, when creating custom exception classes, when writing try-catch blocks, when handling external service failures, when implementing retry strategies, when displaying error messages to users, when cleaning up resources in finally blocks, or when implementing fail-fast validation and error detection.
SKILL.md
1.8 KB, as published. Nobody here has run it
Global Error Handling
This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle global error handling.
When to use this skill
- When implementing error handling in controllers, services, or API endpoints
- When creating custom exception classes for specific error scenarios
- When writing try-catch blocks for error handling
- When providing user-friendly error messages without exposing technical details
- When implementing fail-fast validation and precondition checks
- When handling errors at appropriate boundaries (controllers, API layers)
- When implementing graceful degradation for non-critical service failures
- When creating retry strategies with exponential backoff for external services
- When cleaning up resources (file handles, database connections) in finally blocks
- When centralizing error handling rather than scattering try-catch everywhere
- When handling transient vs. permanent failures differently
- When logging errors appropriately while protecting sensitive information
Instructions
For details, refer to the information provided in this file: global error handling