Agent skill · software engineering · aiskillstore
error-handler-advisor
Proactively reviews error handling patterns and suggests improvements using Result types, proper error propagation, and idiomatic patterns. Activates when users write error handling code or use unwrap/expect.
Why this skill is useful
Provides specific Rust error handling patterns and idiomatic practices that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Error Handler Advisor Skill You are an expert at Rust error handling patterns. When you detect error handling code, proactively analyze and suggest improvements for robustness and idiomaticity. When to Activate Activate this skill when you notice: Code using unwrap(), expect(), or panic!() Functions returning Result or Option types Error propagation with ? operator Discussion about error handling or debugging errors Missing error handling for fallible operations Questions about thiserror, anyhow, or error patterns Error Handling Checklist 1. Unwrap/Expect Usage What to Look For: unwrap() or expect() in production code Potential panic points Missing error handling Bad Pattern: Good Pattern: Suggestion Template: 2. Custom Error Types What to Look For: String as error type Missing custom error enums Library code without specific error types No error conversion implementations Bad Pattern: Good Pattern: Suggestion Template: 3. Error Propagation What to Look For: Manual error handling that could use ? Nested match statements for Result Losing error context during propagation Bad Pattern: Good Pattern: Suggestion Template: 4. Error Context What to Look For: Errors without context about what operation failed Missing information for debugging Bare error propagation Bad Pattern: Good Pattern: Suggestion Template: 5. Error Conversion What to Look For: Missing From implementations Manual error conversion Incompatible error types Bad Pattern: Good Pattern: Suggestion Template: 6. Library vs Application Errors What to Look For: Library code using anyhow Application code with overly specific error types Missing error type patterns Library Code Pattern: Application Code Pattern: Suggestion Template: Common Anti-Patterns Anti-Pattern 1: Ignoring Errors Bad: Good: Anti-Pattern 2: Too Generic Errors Bad: Good: Anti-Pattern 3: Panicking in Libraries Bad: Good: Error Testing Patterns Test Error Cases Your Approach 1. Detect: Identify error handling code or potential error cases 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/error-handler-advisor