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

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/rust-errors/SKILL.md

Quality

Content

65%

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

Highly actionable with complete code examples and a clear, distinct pattern set, but it leans verbose in places and is a monolithic single-file document that bundles a separate logging-level concern inline. Workflow sequencing is implied rather than framed with validation checkpoints.

Suggestions

Tighten explanatory prose that restates concepts Claude can infer (e.g., how serde tag-based enums form discriminated unions) and trim the level-not-on-variant rationale to the one-line rule.

Move the `tracing` ↔ `wellcrafted/logger` mapping into a separate reference file and link to it from a short summary, so the core Rust↔TS error pattern stays the focus.

Frame the error-handling flow as an explicit numbered workflow with a validation checkpoint (e.g., regenerate bindings → review diff → stop if IPC shape changed) rather than burying the checkpoint in prose.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and project-specific, but includes some explanation Claude could infer (e.g., how internally-tagged enums form discriminated unions, the prose around 'level is context, not identity') and could be tightened in places, matching the level-2 anchor.	2 / 3
Actionability	Provides complete, copy-paste-ready Rust enums, TypeScript handling code, serialization JSON, and anti-patterns — fully executable concrete examples rather than pseudocode or vague direction.	3 / 3
Workflow Clarity	The define→serialize→handle sequence is present and the bindings section has one checkpoint ('stop and find why before committing it'), but the skill is pattern-oriented rather than a sequenced workflow, and most guidance lacks explicit validation checkpoints.	2 / 3
Progressive Disclosure	It is a single well-sectioned file with no bundle files to reference, but at ~230 lines it keeps distinct concerns (the tracing↔logger mapping) inline that could be split out, matching the level-2 anchor.	2 / 3
	Total	9 / 12 Passed

Description

90%

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 strong, well-structured description with explicit 'what' and 'when' guidance and natural trigger terms for a clearly distinct niche. The only soft spot is that the actions ('error handling', 'defining error types') are somewhat broad rather than a rich list of concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('Rust to TypeScript error handling for Tauri apps') and a concrete action ('defining Rust error types for TS consumption'), but 'error handling' is broad and not a list of multiple specific concrete actions like the level-3 anchor requires.	2 / 3
Completeness	Explicitly answers both: what ('Rust to TypeScript error handling for Tauri apps') and when ('Use when mentioning Rust errors, Tauri command errors, invoke errors, or defining Rust error types for TS consumption'), matching the level-3 anchor.	3 / 3
Trigger Term Quality	Triggers cover natural terms a Tauri developer would say — 'Rust errors', 'Tauri command errors', 'invoke errors' — giving good coverage of common phrasings rather than jargon-only or generic terms.	3 / 3
Distinctiveness Conflict Risk	The Tauri + Rust↔TypeScript error niche is narrow with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: cb12bcc

Reviewed: 3 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.