How does this skill handle unwrap() calls?

The skill provides a 'Trace Down' approach to replace dangerous unwraps with the '?' operator, match blocks, or descriptive .expect() calls that document why a failure is considered an invariant violation.

When should I use anyhow versus thiserror?

Use 'thiserror' when building libraries where callers need to match on specific error types. Use 'anyhow' for application code where you want easy error propagation and the ability to add context without defining custom structs for every error.

Can this skill help with custom error types?

Yes, it includes patterns for designing domain-specific error variants and mapping lower-level errors (like io::Error) into high-level business logic errors.

Does it provide guidance on when to panic?

Absolutely. It follows a strict logic: use Result for expected failures (like a missing file) and panic! only for unrecoverable bugs or broken internal invariants.

Rust Error Handling Expert

Name: Rust Error Handling Expert
Author: lywa1998

bylywa1998

0•

开发者工具

Implements idiomatic Rust error handling strategies using Result, Option, and industry-standard crates like anyhow and thiserror.

This skill equips Claude with a comprehensive framework for navigating Rust's sophisticated error handling ecosystem. It provides structured guidance on choosing between recoverable and unrecoverable errors, implementing custom error types for libraries using thiserror, and managing application-level failures with anyhow. By applying these patterns, developers can ensure their code is robust, maintainable, and provides clear context for troubleshooting, moving beyond simple unwraps to professional-grade error propagation and domain-specific error design.

主要功能

010 GitHub stars

02Decision framework for choosing between Result, Option, and panic!

03Guidelines for when to use unwrap() versus expect() with invariants

04Standardized patterns for adding diagnostic info to error call chains

05Best practices for the '?' operator and error propagation with context

06Implementation patterns for 'anyhow' in applications and 'thiserror' in libraries

使用场景

01Designing public-facing library APIs with type-safe error variants

02Adding meaningful context to application failures for better observability

03Refactoring unsafe unwraps into robust error propagation patterns

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lywa1998/self-host-claude-marketplace m06-error-handling

For use in Claude.ai and ChatGPT

Download Skill