Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions.
Works with
Handles ownership patterns, lifetime annotation, borrowing design, and trait hierarchies with generics and associated types
Implements async/await applications with tokio, concurrent task spawning, and proper error propagation via Result/Option
Enforces validation through cargo clippy, rustfmt, and comprehensive testing (unit, integration, doctests)
Minimizes unsafe code with documented
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrust-engineerExecute the skills CLI command in your project's root directory to begin installation:
Fetches rust-engineer from jeffallan/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate rust-engineer. Access via /rust-engineer in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
2
total installs
2
this week
7.9K
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
7.9K
stars
Senior Rust engineer with deep expertise in Rust 2021 edition, systems programming, memory safety, and zero-cost abstractions. Specializes in building reliable, high-performance software leveraging Rust's ownership system.
unsafe block with its safety invariantsResult/Option with ? operator and custom error types via thiserrorcargo clippy --all-targets --all-features, cargo fmt --check, and cargo test; fix all warnings before finalisingLoad detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| Ownership | references/ownership.md |
Lifetimes, borrowing, smart pointers, Pin |
| Traits | references/traits.md |
Trait design, generics, associated types, derive |
| Error Handling | references/error-handling.md |
Result, Option, ?, custom errors, thiserror |
| Async | references/async.md |
async/await, tokio, futures, streams, concurrency |
| Testing | references/testing.md |
Unit/integration tests, proptest, benchmarks |
// Explicit lifetime annotation — borrow lives as long as the input slice
fn longest<'a>(x: &'a str, y: &'a str) -> &'a str {
if x.len() > y.len() { x } else { y }
}
// Prefer borrowing over cloning
fn process(data: &[u8]) -> usize { // &[u8] not Vec<u8>
data.iter().filter(|&&b| b != 0).count()
}
use std::fmt;
trait Summary {
fn summarise(&self) -> String;
fn preview(&self) -> String { // default implementation
format!("{}...", &self.summarise()[..50])
}
}
#[derive(Debug)]
struct Article { title: String, body: String }
impl Summary for Article {
fn summarise(&self) -> String {
format!("{}: {}", self.title, self.body)
}
}
thiserroruse thiserror::Error;
#[derive(Debug, Error)]
pub enum AppError {
#[error("I/O error: {0}")]
Io(#[from] std::io::Error),
#[error("parse error for value `{value}`: {reason}")]
Parse { value: String, reason: String },
}
// ? propagates errors ergonomically
fn read_config(path: &str) -> Result<String, AppError> {
let content = std::fs::read_to_string(path)?; // Io variant via #[from]
Ok(content)
}
use tokio::time::{sleep, Duration};
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
let result = fetch_data("https://example.com").await?;
println!("{result}");
Ok(())
}
async fn fetch_data(url: &str) -> Result<String, reqwest::Error> {
let body = reqwest::get(url).await?.text().await?;
Ok(body)
}
// Spawn concurrent tasks — never mix blocking calls into async context
async fn parallel_work() {
let (a, b) = tokio::join!(
sleep(Duration::from_millis(100)),
sleep(Duration::from_millis(100)),
);
}
cargo fmt --check # style check
cargo clippy --all-targets --all-features # lints
cargo test # unit + integration tests
cargo test --doc # doctests
cargo bench # criterion benchmarks (if present)
Result/Option)cargo clippy and fix all warningscargo fmt for consistent formattingunwrap() in production code (prefer expect() with messages)unsafe without documenting safety invariantsString when &str sufficesWhen implementing Rust features, provide:
Rust 2021, Cargo, ownership/borrowing, lifetimes, traits, generics, async/await, tokio, Result/Option, thiserror/anyhow, serde, clippy, rustfmt, cargo-test, criterion benchmarks, MIRI, unsafe Rust
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
jeffallan/claude-skills
jeffallan/claude-skills
jeffallan/claude-skills
jeffallan/claude-skills
jeffallan/claude-skills
jeffallan/claude-skills
Keeps context tight: rust-engineer is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: rust-engineer is focused, and the summary matches what you get after install.
Registry listing for rust-engineer matched our evaluation — installs cleanly and behaves as described in the markdown.
rust-engineer has been reliable in day-to-day use. Documentation quality is above average for community skills.
rust-engineer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
rust-engineer reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend rust-engineer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
rust-engineer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in rust-engineer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
rust-engineer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 67