638 GitHub stars and counting — leonardomso/rust-skills is a Python project TopGit is tracking across repositories on the platform. A collection of 265 rules across 26 categories that AI coding agents can use to write idiomatic, fast, and safe Rust.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
265 Rust rules your AI coding agent can use to write better code. Current for Rust 1.96 (2024 edition).
Works with Claude Code, Cursor, Windsurf, Copilot, Codex, Aider, Zed, Amp, Cline, and pretty much any other agent that supports skills.
Why
Out of the box, coding agents write average Rust — they clone to dodge the borrow checker, .unwrap() everything, and reach for Box<dyn Trait> when impl Trait would do. These rules encode what expert Rust actually looks like: idiomatic, fast, and safe. Each rule is small and focused, so the agent pulls in only what's relevant to the code in front of it.
Install
npx add-skill leonardomso/rust-skills
That's it. The CLI figures out which agents you have and installs the skill to the right place.
How to use it
After installing, just ask your agent:
/rust-skills review this function
/rust-skills is my error handling idiomatic?
/rust-skills check for memory issues
/rust-skills is this unsafe block sound?
The agent loads the relevant rules and applies them to your code.
See it in action
Ask the agent to review a function like this:
// before
fn first_word(s: &String) -> String {
s.clone().split_whitespace().next().unwrap().to_string()
}
With these rules loaded, it knows to take &str instead of &String, drop the
needless clone() and allocation, and return an Option instead of panicking:
The design is built for low token cost and easy auditing:
SKILL.md is a lightweight index — every rule listed as a one-line summary, grouped by category, with a link to its file. The agent reads this first.
rules/ holds one Markdown file per rule (<prefix>-<name>.md). The agent opens only the handful relevant to your code instead of loading all 218 — progressive disclosure keeps context small.
Prefixes (own-, err-, unsafe-, async-, …) map directly to categories, so an agent reviewing async code can pull just async-, conc-, and own- rules.
CLAUDE.md and AGENTS.md are symlinks to SKILL.md, so the same content works across agent conventions.
Manual install
If add-skill doesn't work for your setup, here's how to install manually:
See SKILL.md for the full list with links to each rule file.
Sources & attribution
These rules are an independent synthesis of official Rust guidance, well-known books, and patterns drawn from widely-used open-source crates. They are not affiliated with or endorsed by the Rust project or any crate author. The text and code examples are original summaries — no substantial content is copied from the sources below.
This project is MIT-licensed. Referenced upstream materials remain under their own licenses — the official Rust documentation and API Guidelines are dual MIT / Apache-2.0.
Contributing
PRs welcome. To add or change a rule:
Create rules/<prefix>-<name>.md using a kebab-case id with an existing category prefix (own-, err-, mem-, …).
Follow the format of existing rules: a > one-line summary, then ## Why It Matters, ## Bad, ## Good, and ## See Also (with links that resolve).
Make sure code examples compile on current stable Rust.
Add the rule to the index in SKILL.md (Quick Reference list + the category count) so it stays in sync.
# prefix-rule-name
> One-line imperative summary.
## Why It Matters
Two to four sentences.
## Bad
```rust
// the anti-pattern
```
## Good
```rust
// the recommended pattern
```
## See Also
- [other-rule](other-rule.md) - why it's related
How active is development on leonardomso/rust-skills?
The most recent commit recorded on leonardomso/rust-skills was 4 months ago, based on the GitHub push timestamp. The repository has 70 forks — one of the better signals of community interest.
How many stars does leonardomso/rust-skills have?
leonardomso/rust-skills has 638 GitHub stars — refresh the page for the live number, or check github.com/leonardomso/rust-skills. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What else is in the AI Tools space?
leonardomso/rust-skills is tracked by TopGit under the AI Tools category, alongside 13 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What language is leonardomso/rust-skills written in?
leonardomso/rust-skills is written primarily in Python. GitHub's language field is based on the largest share of bytes in the default branch.
What topics is leonardomso/rust-skills associated with?
GitHub's repository topics for leonardomso/rust-skills: "agent-skills", "ai-coding", "best-practices", "claude-code", "code-quality", "codex", "coding-guidelines", "copilot", "llm", "opencode", "rust", "rust-lang", "rust-language". TopGit's editorial category is AI Tools.
Where do I read more about leonardomso/rust-skills?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/leonardomso/rust-skills is the definitive source.
Why is leonardomso/rust-skills categorized under AI Tools?
TopGit places leonardomso/rust-skills in the AI Tools category based on its GitHub topics and description (tagged: "agent-skills", "ai-coding", "best-practices"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Curious whether rust-skills is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about rust-skills.