rust-errors

Rust to TypeScript error handling for Tauri apps. Use when mentioning Rust errors, Tauri command errors, invoke errors, or defining Rust error types for TS consumption.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%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.

A code-heavy, highly actionable skill body that teaches the Rust-to-TypeScript error union pattern and the tracing/logger mapping with executable examples and a useful binding-diff checkpoint. The main improvement opportunity is progressive disclosure: the body is long and fully inline with no reference files to offload the secondary tracing material.

Suggestions

Move the 'tracing <-> wellcrafted/logger' section into a separate reference file (e.g., LOGGING.md) and link to it from SKILL.md to shorten the main body and improve progressive disclosure.

Trim the miette aside and the 'In practice this shape is rare in epicenter' paragraph to tighten conciseness without losing the core guidance.

Dimension	Reasoning	Score
Conciseness	The body is dense and dominated by executable code and a tight level-mapping table, with only minor asides (the miette exception note, the 'rare in epicenter' paragraph) that could be trimmed; it avoids explaining basic concepts Claude already knows.	4 / 5
Actionability	It provides complete, copy-paste-ready Rust enum definitions with thiserror/serde tags, TypeScript arktype validators, a switch-based handler, and a tapErr example, covering the common cases concretely.	5 / 5
Workflow Clarity	The define-enum -> serialize -> define-TS-type -> switch-handle flow is clear, and the Tauri command surface rules include an explicit checkpoint (review the generated binding diff; stop if it is large but the IPC shape did not change), but it is pattern reference material without a full validate-fix-retry feedback loop.	4 / 5
Progressive Disclosure	Section headers (Discriminated Union Pattern, Tauri Command Surface Rules, tracing <-> logger) give good in-file structure, but all content is inline in a ~230-line file with no bundle references, and the tracing/logger topic could plausibly live in its own reference file.	4 / 5
	Total	17 / 20 Passed

Description

82%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 tight, well-targeted description with explicit 'what' and 'when' guidance and natural Tauri-specific trigger terms. The only soft spot is specificity, which states the domain and one main action rather than enumerating several concrete capabilities.

Suggestions

Expand the 'what' to list a couple more concrete actions (e.g., 'serialize Rust error enums as tagged discriminated unions, validate error shapes on the TypeScript side, map tracing levels to a frontend logger') to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('Rust to TypeScript error handling for Tauri apps') and one concrete action ('defining Rust error types for TS consumption'), but does not list several specific actions, so it sits at the 1-2 concrete actions anchor rather than comprehensive coverage.	3 / 5
Completeness	It explicitly states what the skill does and follows with a concrete 'Use when...' clause listing specific trigger phrases, matching the anchor that requires both what and when with concrete triggers.	5 / 5
Trigger Term Quality	The 'Use when mentioning Rust errors, Tauri command errors, invoke errors...' clause covers multiple natural terms a Tauri developer would say, with synonyms, but lacks the full breadth (e.g., serialization, serde tag) that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The Rust+TypeScript+Tauri error-handling niche is highly specific with distinct triggers, making conflict with unrelated skills unlikely.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: EpicenterHQ/epicenter
Path: .agents/skills/rust-errors/SKILL.md
Commit: abe10f3

Reviewed: 5 days 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.