handling-rust-errors

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.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured content with lean, executable Rust snippets and clean progressive disclosure to three real reference files. Minor conciseness and actionability gaps (some Quick Start sections describe rather than show) keep it just below top marks.

Suggestions

Tighten the HashQL exception explanation by removing the 'This is because compiler errors require rich formatting capabilities' rationale — the bulleted capability list already makes the case.

Add one short executable snippet per Quick Start section (Defining/Propagating/Documenting) instead of capability-only bullets, so the body is self-sufficient before deferring to references.

Add a brief validation hint (e.g., confirm the error type implements the Error trait and that contexts are attached where a reader may need to debug) to strengthen the feedback-loop character of the workflow.

Dimension	Reasoning	Score
Conciseness	Efficient body with minimal padding: DO/DON'T lists and copy-paste Rust snippets assume Claude's competence. Slight over-explanation of the HashQL exception rationale ('This is because compiler errors require rich formatting capabilities') keeps it just below a 5.	4 / 5
Actionability	Provides three concrete, copy-paste-ready Rust examples (creating an error, propagating with context, lazy context) plus explicit import guidance. Minor gap: the Quick Start Guide sections list capabilities as bullet hints rather than showing the executable snippet, deferring detail to references.	4 / 5
Workflow Clarity	Clear routing via the Quick Start Guide and a decision table for HashQL vs error-stack. Error handling is not a destructive/batch operation, so no validation cap applies; the decision table acts as a checkpoint, but there are no explicit validate/recover feedback loops.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview with a Quick Start Guide routing to three well-signaled one-level-deep references (defining/propagating/documenting-errors.md), all verified to exist; cross-references between bundle files stay one level deep with clear navigation.	5 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A high-quality description: concrete, comprehensive, and clearly scoped to a specific crate with explicit trigger guidance. It answers both 'what' and 'when' with natural trigger terms and minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'defining custom errors', 'propagating errors with change_context', 'adding context with attach', 'implementing Error trait', and 'documenting error conditions' — comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly states the 'what' (HASH error handling patterns using error-stack) and the 'when' via a detailed 'Use when working with Result types, Report types...' clause enumerating concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural/technical term coverage including 'Result', 'Report', 'error-stack', 'change_context', 'attach', 'ResultExt' — matching both user vocabulary and the crate's API surface.	5 / 5
Distinctiveness Conflict Risk	Narrowly scoped to a specific crate (error-stack) with HASH-specific triggers and an explicit HashQL exception, giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	20 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: hashintel/hash
Path: .claude/skills/handling-rust-errors/SKILL.md
Commit: 0144f9c

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.