sota-rust

Audit Rust code for compliance with best practices and security rules.

12|2|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/martinholovsky/SOTA-skills --skill sota-rust
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sota-rust
Source: https://github.com/martinholovsky/SOTA-skills/tree/main/skills/sota-rust
Command: npx skills add https://github.com/martinholovsky/SOTA-skills --skill sota-rust

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires thiserror, anyhow, tokio, Cargo.toml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit provides a comprehensive set of rules and guidelines for writing and auditing Rust code with best practices, idioms, and security considerations in mind.

Core Features & Use Cases

  • Ownership and API Design: Rules for idiomatic ownership patterns, smart-pointer selection, and API design principles.
  • Error Handling and Panic Policy: Guidelines for structured error handling, panic policy, and best practices for library/application separation.
  • Unsafe Discipline: Detailed instructions for safe usage of Rust's unsafe features, including UB catalog and CI checks.
  • Async Rust and Tokio: Best practices for asynchronous programming with Tokio, including cancellation safety and structured concurrency.
  • Security and Supply Chain: Rules for secure dependency management, handling untrusted input, and secret handling.

Quick Start

Use the sota-rust skill to audit the 'main.rs' file for compliance with Rust best practices.

Frequently Asked Questions about sota-rust

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the best practices for asynchronous programming in Rust with Tokio?▼

Best practices for asynchronous programming in Rust with Tokio involve enforcing cancellation safety and structured concurrency. The sota-rust guidelines audit async code to ensure proper task management and prevent common concurrency pitfalls.

How do I handle errors in Rust libraries versus applications?▼

Error handling in Rust requires separating library and application boundaries using thiserror for structured errors and anyhow for application-level diagnostics. The guidelines specify panic policies and structured error propagation rules for robust code.

How do I audit Rust code for unsafe usage and undefined behavior?▼

Auditing Rust code for unsafe usage requires checking against an undefined behavior catalog and enforcing CI checks. The sota-rust rules provide detailed instructions for safe usage of unsafe features and verifying memory safety boundaries.

Does Rust supply chain security require specific dependency management rules?▼

Rust supply chain security requires strict dependency management rules for handling untrusted input and secret handling. The guidelines audit Cargo.toml dependencies to ensure secure integration and mitigate supply chain vulnerabilities.

What is the best way to design Rust APIs for idiomatic ownership patterns?▼

Designing Rust APIs for idiomatic ownership requires selecting proper smart pointers and following ownership pattern rules. The sota-rust guidelines review API design principles to ensure efficient borrowing, lending, and pointer usage.