agentskills.codes
HA

handling-rust-errors

by hashintelCodingSource

Standardizes Rust error handling using the error-stack crate and provides guidance on contextual error reporting.

DebuggingCode ReviewRust

Install

mkdir -p .claude/skills/handling-rust-errors && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2724" && unzip -o skill.zip -d .claude/skills/handling-rust-errors && rm skill.zip

Installs to .claude/skills/handling-rust-errors

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

HASH error handling patterns using error-stack crate. Use when working with Result types, Report types, defining custom errors, propagating errors with change_context, adding context with attach, implementing Error trait, or documenting error conditions in Rust code.
267 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • →Uses Report<MyError> for consistent error propagation
  • →Attaches contextual info to results using the attach method
  • →Standardizes error definition without using standard library error types
  • →Enforces usage of derive_more instead of thiserror

How it works

Applies a set of rigid imports and trait-method rules to wrap and propagate errors according to project coding standards.

Inputs & outputs

You give it
Result type or error definition
You get back
Error-stack compliant error implementation

When to use handling-rust-errors

  • →Implementing error propagation
  • →Attaching context to Rust Result types
  • →Defining custom error traits
  • →Refactoring error handling code

About handling-rust-errors

Standardizes error handling through the `error-stack` crate. Guides developers in using `Report<MyError>`, custom error definitions, and contextual attaching to ensure consistent observability.

HASH error handling patterns using error-stack crate. Use when working with Result types, Report types, defining custom errors, propagating errors with change_context, adding context with attach, implementing Error trait, or documenting error conditions in Rust code.

When not to use it

  • →In the HashQL compiler module where diagnostics are required
  • →When prototyping simple CLI tools where anyhow suffices

Prerequisites

Rust toolchainError-stack crate

Limitations

  • →Requires explicit import management of Error traits
  • →Not compatible with standard diagnostic-heavy compiler code

How it compares

It enforces a HASH-specific standard by banning common Rust error crates like anyhow and thiserror.

Compared to similar skills

handling-rust-errors side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
handling-rust-errors (this skill)44moNo flagsIntermediate
debug-cli110moReviewIntermediate
fix-clippy37moNo flagsBeginner
search-code26moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by hashintel

View all by hashintel →

exploring-rust-crates

hashintel

Generate Rust documentation to understand crate APIs, structure, and usage. Use when exploring Rust code, understanding crate organization, finding functions/types/traits, or needing context about a Rust package in the HASH workspace.

33

writing-hashql-jexpr

hashintel

HashQL J-Expr syntax for writing queries. Use when writing J-Expr code, using #literal/#struct/#list constructs, understanding function call syntax, or working with HashQL query files (.jsonc).

25

documenting-rust-code

hashintel

Rust documentation practices for HASH codebase. Use when writing doc comments, documenting functions/types/traits/modules, creating error sections, using intra-doc links, or following rustdoc conventions.

19

managing-cargo-dependencies

hashintel

Cargo.toml dependency management patterns for HASH workspace. Use when adding, updating, or removing dependencies, organizing Cargo.toml sections, configuring version pinning and default features, or managing public dependencies.

13

managing-git-workflow

hashintel

Git workflow for HASH including branch naming, PR creation, and PR reviews. Use when creating branches, making commits, opening pull requests, or reviewing PRs.

12

testing-hashql

hashintel

HashQL testing strategies including compiletest (UI tests), unit tests, and snapshot tests. Use when writing tests for HashQL code, using //~ annotations, running --bless, debugging test failures, or choosing the right testing approach.

11

You might also like

debug-cli

antinomyhq

Use when users need to debug, modify, or extend the code-forge application's CLI commands, argument parsing, or CLI behavior. This includes adding new commands, fixing CLI bugs, updating command options, or troubleshooting CLI-related issues.

117

fix-clippy

quickwit-oss

Fix all clippy lint warnings in the project

315

search-code

JamieMason

Search for code patterns in Syncpack. Use when finding symbols, implementations, or understanding how code is used. Covers ast-grep for Rust and grep/rg for other cases.

21

m01-ownership

actionbook

CRITICAL: Use for ownership/borrow/lifetime issues. Triggers: E0382, E0597, E0506, E0507, E0515, E0716, E0106, value moved, borrowed value does not live long enough, cannot move out of, use of moved value, ownership, borrow, lifetime, 'a, 'static, move, clone, Copy, 所有权, 借用, 生命周期

11

m03-mutability

actionbook

CRITICAL: Use for mutability issues. Triggers: E0596, E0499, E0502, cannot borrow as mutable, already borrowed as immutable, mut, &mut, interior mutability, Cell, RefCell, Mutex, RwLock, 可变性, 内部可变性, 借用冲突

11

bisect-ssa-pass

noir-lang

Workflow for debugging SSA pass semantic preservation using the noir-ssa CLI. Use when a program's behavior changes incorrectly during the SSA pipeline - bisects passes to identify which one breaks semantics. The `pass_vs_prev` fuzzer finds such issues automatically.

10

Search skills

Search the agent skills registry