rust-pro
Build Production Rust Systems
Rust projects often require careful choices across ownership, async runtimes, safety, and performance. This skill guides Claude, Codex, and Claude Code through production Rust design and implementation.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "rust-pro" from https://skillstore.io/skills/sickn33-rust-pro.md and its manifest at https://skillstore.io/api/skills/sickn33-rust-pro/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "rust-pro". Design a high-performance async web service with proper error handling.
Expected outcome:
A service architecture with crate choices, route layout, typed errors, middleware, test strategy, and deployment considerations.
Using "rust-pro". Optimize this Rust code for better memory usage and cache locality.
Expected outcome:
A performance review covering allocation sources, data layout options, profiling steps, and benchmark targets.
Using "rust-pro". Create a safe wrapper around a C library using FFI.
Expected outcome:
A wrapper design with ownership rules, lifetime boundaries, error mapping, unsafe invariants, and validation tests.
Security Audit
SafeThe single static finding appears to be a false positive. The cited lines describe Rust type-system behavior and memory-safety priorities, with no network reconnaissance intent or instructions.
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-rust-pro/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-rust-pro?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-rust-pro?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-rust-pro/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-rust-pro.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). rust-pro security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-rust-pro/audits/5BibTeX citation
@techreport{sickn33-sickn33-rust-pro-2026,
author = {sickn33},
title = {rust-pro security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-rust-pro/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "rust-pro security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-rust-pro/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-rust-pro:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Design Async Services
Plan an axum, tower, or Tokio service with structured errors, middleware, tests, and backpressure.
Resolve Ownership Problems
Untangle lifetime, borrowing, trait-bound, and generic design issues in complex Rust modules.
Harden Systems Code
Review unsafe blocks, FFI wrappers, allocators, and low-level I/O designs for clearer safety invariants.
Try These Prompts
Explain this Rust compiler error in plain language. Show the ownership or lifetime issue, then suggest a minimal fix.
Design a Rust async service for this requirement. Choose Tokio, axum, or related crates, and outline modules, errors, tests, and runtime concerns.
Review this Rust hot path for memory layout, allocation, concurrency, and cache behavior. Recommend measurable optimizations and benchmark strategy.
Audit this unsafe Rust or FFI design. Identify required safety invariants, lifetime assumptions, aliasing risks, and a safer public API.
Best Practices
- Provide compiler errors, relevant code, Cargo features, target platform, and runtime constraints.
- Ask for tests, benchmarks, and linting plans when requesting implementation guidance.
- State safety, latency, memory, and compatibility requirements before selecting crates or APIs.
Avoid
- Do not ask for unsafe optimizations without documenting safety invariants.
- Do not request broad rewrites when a focused ownership, API, or performance issue is known.
- Do not accept performance advice without measurements on representative workloads.