Rust Best Practices

Name: Rust Best Practices
Author: apollographql

Official

apollographql·vlatest·backend·MIT

Helps with Rust, best practices as part of developing backend services and APIs workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add apollographql/skills --skill rust-best-practices -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

apollographql

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 28 Sept 2026

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned apollographql/skills at 322da824b2.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 322da824b2
Manifest: skills/rust-best-practices/SKILL.md
Scanned: 10 files, 2,315 lines

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

The rust-best-practices skill provides guidance on writing efficient, safe, and maintainable Rust code. It includes recommendations on memory management, error handling, and idiomatic usage of Rust's standard library and common crates.

When to use it

When developing a new Rust project and looking for structured coding guidelines.
When refactoring legacy Rust code to improve performance or safety.
When preparing documentation or training materials for a Rust team.
When optimizing existing code for better concurrency or resource usage.

Key capabilities

Code structure recommendations
Memory safety best practices
Error handling patterns
Idiomatic use of standard library and crates
Performance optimization strategies

Example prompts

"How should I handle errors in a Rust function?"
"What are the best practices for writing safe concurrent code in Rust?"
"Can you suggest idiomatic ways to manage memory in Rust?"

Tips & gotchas

This skill assumes familiarity with basic Rust concepts like ownership and borrowing.
Some recommendations may require additional crate dependencies, so ensure they align with your project's requirements.