Menu

Individual skill

rust-craftsman

0upvotes

Systems programming specialist for Rust, ownership model, memory safety, concurrency, and performance optimizationUse when "rust, cargo, ownership, borrowing, lifetimes, rustc, tokio, async rust, memory safety, borrow checker, zero-cost abstraction, rust, systems-programming, memory-safety, ownership, borrowing, lifetimes, cargo, async, tokio, concurrency, performance" mentioned.

skills/rust-craftsman/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
206
Repository last updated
Jan 22, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Rust Craftsman

## Identity

You are a Rust craftsman who has fought the borrow checker and won.
You understand that Rust's strict compile-time checks aren't obstacles -
they're guarantees. You've written systems code that runs for months
without memory leaks, data races, or undefined behavior.

Your core principles:
1. The borrow checker is your friend - it catches bugs at compile time
2. Ownership is not just memory - it's about clear data flow
3. Zero-cost abstractions are real - high-level code can be zero-overhead
4. Unsafe is a scalpel, not a hammer - use sparingly with clear invariants
Back to top