Rust Specialist

VerifiedSafe

Expert in Rust development focusing on async services, safe systems programming, and production tooling. Uses Tokio, Axum, SQLx, and enforces clippy-driven quality checks. Ideal when building or refactoring Rust code, especially for ownership/lifetime sensitive tasks.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#rust#async#systems-programming#clippy

Recommended for

Automated summary

This skill specializes the agent in Rust development for async services, safe systems programming, and production tooling, using Tokio, Axum, SQLx, and Clippy-driven quality checks.

Strengths

  • Enforces clippy and rustfmt as non-optional quality gates.
  • Supports modern frameworks like Tokio, Axum, and SQLx.
  • Pragmatic approach to error types and concurrency primitives.

Limitations

  • Assumes prior familiarity with Rust and its core concepts (ownership, lifetimes).
  • Does not automatically handle complex environment setup (CI/CD, deployment).
  • Architectural decisions are left to the developer.
When to use it

Use this skill when writing or refactoring Rust code in projects involving async services, systems components, or CLI tools.

When not to use it

Avoid this skill if you are new to Rust or if your project does not require Rust code (consider a more general skill).

Security analysis

Safe
Quality score92/100

The skill uses Bash only for standard Rust development commands (`cargo fmt`, `clippy`, `test`, `build`). No destructive, exfiltrating, or obfuscated actions are present. It is a safe, development-oriented skill.

No concerns found

How this analysis is made

Examples

Build async HTTP server with Axum
Create a new Rust project using Axum that exposes a GET /hello endpoint returning a JSON response. Include error handling with custom error types, proper async main with Tokio, and add a few unit tests. Ensure clippy passes with -D warnings.
Refactor Rust module for safety
Refactor the Rust module in src/unsafe_ops.rs to minimize unsafe code. Isolate any remaining unsafe blocks with documentation, replace raw pointers with safe abstractions where possible, and verify no panics in non-test code. Run cargo fmt and clippy after changes.
Integrate SQLx with existing service
Add a SQLx database layer to the existing Rust service in src/main.rs. Connect to a PostgreSQL database, define a query function for fetching users by ID, and wrap it in a Result type. Add integration tests and ensure all clippy warnings are addressed.

name: moai-lang-rust description: Rust specialist for async services, safe systems programming, and production tooling with Tokio, Axum, SQLx, and clippy-driven quality checks. Use when building or refactoring Rust code. license: Apache-2.0 compatibility: Designed for Claude Code allowed-tools: Read, Grep, Glob, Bash user-invocable: false metadata: version: "2.0.0" category: "language" status: "active" updated: "2026-02-22"

Rust Development (Lean)

When to use

  • .rs files and Cargo.toml
  • Async services, CLI tools, systems components
  • Ownership/lifetime, trait, or performance-sensitive work

Defaults

  • Prefer explicit error types at library boundaries.
  • Keep unsafe usage isolated and documented.
  • Use clippy and rustfmt as non-optional quality gates.
  • Favor simple ownership flows over complex lifetimes when possible.

Quick workflow

  1. Identify crate boundaries and public APIs.
  2. Implement minimal change with clear types/errors.
  3. Add/update tests for changed behavior.
  4. Run fmt, clippy, and tests.

Commands

  • Format: cargo fmt --all
  • Lint: cargo clippy --all-targets --all-features -- -D warnings
  • Test: cargo test --all-features
  • Build release: cargo build --release

Implementation checklist

  • Result<T, E> and ? used consistently.
  • Avoid panics in non-test code paths unless explicitly fatal.
  • Serialization contracts versioned when exposed externally.
  • Concurrency primitives chosen deliberately (Mutex, RwLock, channels, semaphore).

Validation checklist

  • cargo fmt clean.
  • cargo clippy clean.
  • Tests pass.
  • New dependencies justified.

References

  • references/reference.md - compact guidance and docs links
  • references/examples.md - concise service/test patterns
  • ../AGENT_SKILL_SPEC.md - shared Anthropic/Copilot alignment

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/rust-specialist-mm8o5224/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/rust-specialist-mm8o5224' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/rust-specialist-mm8o5224/download' --output '.skill-downloads/rust-specialist-mm8o5224/SKILL.md.part' && mv '.skill-downloads/rust-specialist-mm8o5224/SKILL.md.part' '.skill-downloads/rust-specialist-mm8o5224/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Environment declared by the author: Designed for Claude Code

Tools declared by the author (check availability in your agent): Read, Grep, Glob, Bash

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/rust-specialist-mm8o5224/SKILL.md' && test -s '.skill-downloads/rust-specialist-mm8o5224/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/moai-lang-rust' && cp -R '.skill-downloads/rust-specialist-mm8o5224' '.claude/skills/moai-lang-rust'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/rust-specialist-mm8o5224'

openskills read 'rust-specialist-mm8o5224'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/rust-specialist-mm8o5224/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills