error-handling-debugging

error-handling-debugging is a skill for Claude Code, Codex from cacr92/WeReply. It costs 83 tokens per session (3,191 once invoked), scanned A, original, MIT.

A guide for handling errors and debugging Rust or TypeScript applications built with Tauri, a framework for desktop apps with a Rust backend and web-based interface. It covers error chains, validation, and converting failures into API responses.

In plain words
What is it for?
Use it to add error handling, debug failed Tauri commands, report database problems, and implement recovery patterns in Rust and TypeScript.
Why use it?
It helps developers preserve useful error context and return consistent failures when commands, databases, or services go wrong.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/cacr92/wereply/error-handling-debugging
Any agent
npx skills add cacr92/WeReply --skill error-handling-debugging
Clone the repo
git clone --depth 1 https://github.com/cacr92/WeReply

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for error-handling-debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/cacr92/wereply/error-handling-debugging.svg)](https://agentmods.dev/skills/cacr92/wereply/error-handling-debugging)
Your own site
<a href="https://agentmods.dev/skills/cacr92/wereply/error-handling-debugging"><img src="https://agentmods.dev/badge/skills/cacr92/wereply/error-handling-debugging.svg" alt="Measured on agentmods" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,191 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00083 $0.03191
Opus 5 $0.00042 $0.01596
Sonnet 5 $0.00017 $0.00638
Haiku 4.5 $0.00008 $0.00319

Measured 3d ago against content hash 3f791c6c8a7b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

error-handling-debugging scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/error-handling-debugging/SKILL.md · 585 lines

How it starts

The opening of the file, as written. The whole thing — 585 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Error Handling & Debugging Skill

Comprehensive error handling and debugging strategies for Tauri + Rust + React applications.

Rust Error Handling

Error Chain with anyhow

use anyhow::{Context, Result, anyhow, bail};

pub async fn complex_operation(&self) -> Result<Output> {
    let data = self.fetch_data()
        .await
        .context("获取数据失败")?;

    if data.is_empty() {
        bail!("数据为空,无法继续处理");
    }

    let processed = self.process_data(&data)
        .context("处理数据失败")?;

    Ok(processed)
}

ApiResponse Conversion Pattern

use crate::utils::error::{api_err, api_ok, ApiResponse};

#[tauri::command]
#[specta::specta]
pub async fn handle_formula_request(
    dto: FormulaDto,
    state: State<'_, TauriAppState>,
) -> ApiResponse<Formula> {
    // Using with_service helper for automatic error conversion
    with_service(state, |ctx| async move {
        ctx.formula_service.create_formula(dto).await
    })
    .await
}

// Manual conversion
#[tauri::command]
#[specta::specta]
pub async fn manual_error_handling() -> ApiResponse<Data> {
    match perform_operation().await {
        Ok(data) => api_ok(data),
        Err(e) => {
            // Log error internally
            error!("Operation failed: {:?}", e);
            // Return user-friendly message
            api_err(format!("操作失败,请检查输入后重试"))
        }
    }
}

Custom Error Types

use thiserror::Error;

#[derive(Error, Debug)]
pub enum FormulaError {
    #[error("配方不存在: {id}")]
    FormulaNotFound { id: i64 },

    #[error("营养约束冲突: {nutrient}")]
    NutritionConflict { nutrient: String },

    #[error("优化失败: {reason}")]
    OptimizationFailed { reason: String },

    #[error("数据库错误: {0}")]
    Database(#[from] sqlx::Error),

    #[error("IO错误: {0}")]
    Io(#[from] std::io::Error),
}

impl From<FormulaError> for ApiResponse<()> {
    fn from(err: FormulaError) -> Self {
        match err {
            FormulaError::FormulaNotFound { id } => {
                api_err(format!("配方 ID {} 不存在", id))
            }
            FormulaError::NutritionConflict { nutrient } => {
                api_err(format!("营养约束 {nutrient} 冲突,请调整约束范围"))
            }
            FormulaError::OptimizationFailed { reason } => {
                api_err(format!("配方优化失败: {}", reason))
            }
            _ => api_err(format!("操作失败: {}", err)),
        }
    }
}

Read the full file on GitHub · 585 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 585 lines · 83 tokens per session scan A 3f791c6c8a7b

Subscribe to this mod's changes

error-handling-debugging is a skill published in the GitHub repository cacr92/WeReply (6 stars, last pushed 7mo ago), licensed MIT. It adds 83 tokens to every session and 3,191 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens