CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An expert-level, tightly written convention document: complete code examples in both languages, concrete contract rules, and a sensible define/generate/sync structure. The consistent weakness is small completeness gaps — a missing consumer-side switch example, an unspecified regeneration command, and partial overlap with the logging skill's territory.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — it never explains what Tauri, thiserror, or tracing are, and nearly every line carries project-specific contract detail (DataError mode, non-nullable errors, binding regeneration). Minor trims are possible, e.g. the paragraph re-explaining that no Rust logging crate attaches level to error types and the miette exception, which is ecosystem knowledge Claude already has.

4 / 5

Actionability

Two complete copy-paste-ready examples (the Rust enum with serde/specta derives, the TS `tapErr` chain), a concrete five-level macro-to-method mapping table, and specific rules like "Callers branch on `error !== null`" give mostly executable guidance. Minor gaps keep it below the top anchor: no consumer-side `switch (error.name)` example, no command for regenerating bindings, and the raw-byte command is mentioned without a code sample.

4 / 5

Workflow Clarity

The sections form a coherent define → generate → sync sequence, and the sync section includes explicit checkpoints ("Regenerate the bindings... and review their diff", "Check the relevant TypeScript type assertions and consumers"). It is not a destructive or batch workflow, so no cap applies; it falls short of the top anchor only because the checkpoints are terse rather than fully elaborated feedback loops.

4 / 5

Progressive Disclosure

A single well-organized file with clear section headers, no nested references, and clearly signaled cross-references to sibling skills (`tauri`, `error-handling`, `logging`). It is not a 5: the file exceeds 50 lines, and the `tracing` ↔ `wellcrafted/logger` section duplicates level-mapping content that the body itself says the `logging` skill owns, a minor organization gap.

4 / 5

Total

16

/

20

Passed

Description

78%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 strong description with an explicit "Use when" clause and natural, niche-appropriate trigger terms. Its main weakness is that the capability statement is a single domain phrase plus one action rather than a list of concrete capabilities, leaving the breadth of what the skill covers understated.

Suggestions

Replace the bare domain phrase "Rust to TypeScript error handling for Tauri apps" with 2-3 concrete capabilities, e.g. "Define serializable Rust command error enums, generate typed TS result shapes, and map tracing levels to the frontend logger for Tauri apps."

Add one or two natural trigger variants such as "error serialization" or "IPC errors" to catch phrasings that do not mention Tauri or invoke explicitly.

DimensionReasoningScore

Specificity

The description names the domain crisply ("Rust to TypeScript error handling for Tauri apps") and includes one concrete action ("defining Rust error types for TS consumption"), but it does not list several distinct actions, matching the anchor for a domain plus 1-2 concrete actions rather than the multi-action coverage of the level above.

3 / 5

Completeness

It explicitly answers both questions: the first sentence states what the skill does, and "Use when mentioning Rust errors, Tauri command errors, invoke errors, or defining Rust error types for TS consumption" provides concrete trigger phrases, matching the top anchor's example pattern exactly.

5 / 5

Trigger Term Quality

"Rust errors, Tauri command errors, invoke errors" are natural phrases a user in this niche would actually say, giving good keyword coverage. It falls short of the top anchor because common variations like "error serialization", "IPC errors", or "Result types" are absent.

4 / 5

Distinctiveness Conflict Risk

The Tauri-specific niche and triggers ("Tauri command errors, invoke errors") make it mostly distinct with only minor overlap risk: "Rust errors" alone could fire in non-Tauri Rust contexts, and the body itself names sibling `error-handling` and `tauri` skills whose territory could overlap. This fits the anchor for mostly distinct with minor overlap rather than the clear-niche top anchor.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.