rust-best-practicesDevelopment guidance for writing idiomatic Rust. Use when: (1) writing new Rust functions or modules, (2) choosing between borrowing, cloning, or ownership p...
Install via ClawdBot CLI:
clawdbot install anderskev/rust-best-practicesGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://api.example.comAudited Apr 18, 2026 · audit v1.0
Generated Apr 19, 2026
Developing backend APIs and microservices in Rust where low latency and memory safety are critical. This skill helps engineers implement proper error handling with Result types, optimize performance through profiling, and choose correct pointer types for concurrent request handling.
Writing firmware and embedded applications where resource constraints require careful memory management. The skill guides developers on ownership patterns to avoid cloning, static dispatch to reduce binary size, and type state patterns for compile-time validation of hardware interactions.
Building linters, code analyzers, and development tools that process source code efficiently. This skill provides guidance on clippy configuration for consistent linting, documentation standards for public APIs, and performance optimization through proper iterator chaining and allocation strategies.
Creating secure cryptographic primitives and distributed ledger components where safety and performance are paramount. The skill helps with error handling for fallible operations, choosing between borrowing and cloning for sensitive data, and using generics for flexible algorithm implementations.
Developing game systems and graphics pipelines that require both high performance and maintainability. This skill assists with pointer type selection for asset management, performance profiling for real-time rendering, and documentation practices for complex APIs used by multiple teams.
Offering specialized Rust development consulting to help companies adopt Rust best practices in their projects. Revenue comes from hourly or project-based contracts for code reviews, architecture design, and team training on ownership patterns and performance optimization.
Providing a cloud-based development environment with integrated Rust tooling that enforces best practices automatically. Revenue is generated through subscription tiers based on team size, with features like automated clippy enforcement, performance profiling tools, and documentation generators.
Delivering structured training programs and certification exams for Rust developers at large organizations. Revenue streams include corporate training packages, individual certification fees, and ongoing support contracts for maintaining best practice standards across development teams.
💬 Integration Tip
Integrate this skill during active development phases rather than code reviews, and configure clippy lints as part of your CI/CD pipeline to automatically enforce best practices on every commit.
Scored Apr 19, 2026
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Systematic code review patterns covering security, performance, maintainability, correctness, and testing — with severity levels, structured feedback guidance, review process, and anti-patterns to avoid. Use when reviewing PRs, establishing review standards, or improving review quality.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Provides a 7-step debugging protocol plus language-specific commands to systematically identify, verify, and fix software bugs across multiple environments.
Control and operate Opencode via slash commands. Use this skill to manage sessions, select models, switch agents (plan/build), and coordinate coding through Opencode.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions