How do I install the Rust Expert skill?

Run npx skillmds@latest add tomevault-io/rust-expert-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rust Expert safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rust Expert?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rust Expert free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rust Expert?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rust Expert by tomevault-io — Agent Skill

Name: Rust Expert
Author: tomevault-io

Rust Expert

Rust domain expertise for Cargo builds, borrow checker errors, lifetimes, ownership, traits, generics, Result/error handling, async/concurrency, message passing, testing, mocks through traits, and idiomatic review. Use for Rust implementation, debugging, testing, build resolution, performance-sensitive refactoring, and ownership design tasks. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Rust Expert Skill

You have invoked the Rust Expert Skill. This skill contains actionable checklists and constraints for Rust software engineering tasks.

Quick Actions & Checklists

Build & Borrow Checker Resolution

Rule 1: DO NOT use .clone() as a first resort to fix borrow checker errors.
Rule 2: Analyze lifetime bounds. If &'a is missing, trace the struct instantiation.
Rule 3: If the compiler suggests a trait bound (e.g., T: Default), evaluate if the bound makes architectural sense before blindly applying it.
Rule 4: Use cargo check incrementally to verify fixes without paying the full cargo build cost.

Coding Patterns

Error Handling: Use the ? operator and Result universally. Prefer libraries like anyhow for applications or thiserror for libraries.
Enums over Booleans: Use enum for state machines instead of multiple boolean flags.
Concurrency: Prefer message passing (mpsc) or RwLock over Mutex where applicable.

Need Deep Knowledge? Read $SKILL_DIR/references/rust-patterns.md.

Testing & Verification

Unit Tests: Keep them in the same file inside a #[cfg(test)] module.
Integration Tests: Place them in the tests/ directory at the project root.
Mocks: Use traits for dependency injection to allow mocking in tests.

Need Deep Knowledge? Read $SKILL_DIR/references/rust-testing.md.

Instructions for the Agent

Based on the arguments provided (e.g., "build", "testing", "review"), apply the relevant checklist above.
For deeper Rust patterns or testing guidance, use the Read tool to fetch the relevant reference document from $SKILL_DIR/references/.

Source: Rianico/harness-zkx — distributed by TomeVault.

---name: rust-expert-3description: Rust domain expertise for Cargo builds, borrow checker errors, lifetimes, ownership, traits, generics, Result/error handling, async/concurrency, message passing, testing, mocks through traits, and idiomatic review. Use for Rust implementation, debugging, testing, build resolution, performance-sensitive refactoring, and ownership design tasks. Use when this capability is needed.---# Rust Expert SkillYou have invoked the Rust Expert Skill. This skill contains actionable checklists and constraints for Rust software engineering tasks.## Quick Actions & Checklists### Build & Borrow Checker Resolution- **Rule 1:** DO NOT use `.clone()` as a first resort to fix borrow checker errors.- **Rule 2:** Analyze lifetime bounds. If `&'a` is missing, trace the struct instantiation.- **Rule 3:** If the compiler suggests a trait bound (e.g., `T: Default`), evaluate if the bound makes architectural sense before blindly applying it.- **Rule 4:** Use `cargo check` incrementally to verify fixes without paying the full `cargo build` cost.### Coding Patterns- **Error Handling:** Use the `?` operator and `Result` universally. Prefer libraries like `anyhow` for applications or `thiserror` for libraries.- **Enums over Booleans:** Use `enum` for state machines instead of multiple boolean flags.- **Concurrency:** Prefer message passing (`mpsc`) or `RwLock` over `Mutex` where applicable.> **Need Deep Knowledge?** Read `$SKILL_DIR/references/rust-patterns.md`.### Testing & Verification- **Unit Tests:** Keep them in the same file inside a `#[cfg(test)]` module.- **Integration Tests:** Place them in the `tests/` directory at the project root.- **Mocks:** Use traits for dependency injection to allow mocking in tests.> **Need Deep Knowledge?** Read `$SKILL_DIR/references/rust-testing.md`.## Instructions for the Agent1. Based on the arguments provided (e.g., "build", "testing", "review"), apply the relevant checklist above.2. For deeper Rust patterns or testing guidance, use the `Read` tool to fetch the relevant reference document from `$SKILL_DIR/references/`.---> Source: [Rianico/harness-zkx](https://github.com/Rianico/harness-zkx) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions