How to use the Rust Engineer agent skill (rust-engineer)

What the rust-engineer skill makes the agent do

An agent skill is a folder with a SKILL.md file that the agent reads when a task matches the skill's description. The rust-engineer skill is written for Rust work. Its stated core workflow is to analyse ownership and lifetimes, design traits, implement with minimal unsafe code, handle errors with Result, Option, the ? operator and thiserror, and then validate the code.

• Designs ownership and borrowing patterns and annotates lifetimes where inference is not enough.
• Writes trait hierarchies with generics and associated types.
• Builds async applications with tokio and async/await.
• Structures error handling with Result/Option and custom error types via thiserror.
• Follows stated rules such as avoiding unwrap() in production code, documenting every unsafe block, and running cargo clippy, cargo fmt and cargo test before finishing.

Install the rust-engineer skill from a ZIP file

Download the ZIP for the rust-engineer skill from this page and unzip it. You can install it for yourself or for one project.

For a personal install, place the unzipped skill folder inside ~/.claude/skills/. For a project-only install, place it inside the project's .claude/skills/ folder.

If you use the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.

• Personal: ~/.claude/skills/
• Project only: .claude/skills/ inside your project
• Claude apps: Settings → Capabilities → Skills, then upload

Check your Rust environment before you start

The skill itself does not install Rust. It instructs the agent to run Cargo commands in your environment, so you need a Rust toolchain with Cargo available. The validation steps use cargo clippy, cargo fmt and cargo test, so those should also be available.

Crates such as tokio, thiserror and reqwest are referenced in the examples. You only need them if your own project uses them.

• Rust toolchain with Cargo
• cargo clippy, cargo fmt and cargo test for validation
• Crates like tokio, thiserror and reqwest, only if your project uses them

Trigger the skill with natural requests

You do not need a special command. Describe the Rust task in plain language and mention Rust, Cargo or the specific topic. The skill's description lists triggers such as ownership, borrowing, lifetimes, async Rust, tokio, FFI bindings and memory safety.

Good requests name the goal and the code. For example, ask for a review of a function that returns a reference, or ask for help designing a trait-based API for a storage layer.

• "Use the rust-engineer skill to fix this borrow checker error in my parser."
• "Review this Rust module for error handling against Rust best practices."
• "Design a trait hierarchy for these three storage backends in Cargo project."
• "Help me convert this blocking file read into async code using tokio."

Example: what a typical answer contains

The skill asks the agent to return type definitions, an implementation with proper ownership, custom error types, tests including doctests, and a short explanation of design decisions. For async work, the reference notes show patterns such as #[tokio::main] and tokio::join! for running operations concurrently.

Review the output against your own compiler and test results. The skill sets the rules, but your toolchain decides whether the code builds.

Safety notes: scripts and network

According to the skill's listing, it runs no scripts and uses no network access. It is a set of instructions and reference files. The commands it asks the agent to run are Cargo commands in your own environment, so review them before approving them, as you would for any command an agent runs.

The skill does not run your project's tests by itself. It only tells the agent to run cargo commands, which means you still need to run and read the results.

• Runs scripts: no
• Uses network: no
• Generated Rust still needs compiling, testing and security review by a human

Tips for getting reliable results

Give the agent the relevant code and the compiler error message. Ask it to keep unsafe code to a minimum and to document any unsafe block. If you have a project convention, such as a particular error crate, say so. Ask for tests along with the change so that cargo test and doctests can confirm the behaviour.

• Paste the full compiler error, not a summary.
• Name the crates your project already uses.
• Ask for the validation commands to be run and the output reported.
• Review every unsafe block and every expect() message yourself.