Rust Best Practices
v1.0.0Development guidance for writing idiomatic Rust. Use when: (1) writing new Rust functions or modules, (2) choosing between borrowing, cloning, or ownership p...
⭐ 0· 5·0 current·0 all-time
byKevin Anderson@anderskev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the content: all required files are Rust guidance and the SKILL.md and references focus on idiomatic Rust, linting, performance, generics, pointer choices, and type-state. There are no unrelated credentials, binaries, or config demands.
Instruction Scope
SKILL.md stays within a development guidance scope. It suggests running standard Rust developer commands (cargo clippy, cargo bench, cargo flamegraph, cargo install flamegraph) and editing Cargo.toml/CI. It does not instruct reading arbitrary host files, exfiltrating data, or contacting external endpoints beyond typical developer tools.
Install Mechanism
No install spec or bundled code is present; this is instruction-only so nothing is downloaded or written by the skill itself.
Credentials
The skill requests no environment variables, credentials, or config paths. Any tooling it references (cargo, flamegraph) are standard developer tools appropriate for the stated purpose.
Persistence & Privilege
always is false, model invocation is allowed (platform default). The skill does not request permanent presence or system-level modifications and does not propose changing other skills or global agent configuration.
Assessment
This is an instruction-only Rust best-practices guide and appears coherent. Before using it: (1) be aware the guidance recommends running developer commands (cargo clippy, cargo bench, cargo flamegraph and occasionally cargo install) — verify those tools in your environment before executing; (2) applying strict lints (e.g., -D warnings or deny(missing_docs)) can break builds/CI until code is updated, so review CI impact; and (3) although the skill itself contains no network or credential access, any agent or CI you give permission to run the suggested commands may read or build your code — ensure you trust the runtime that will execute them.Like a lobster shell, security has layers — review code before you run it.
latestvk976jzmc2dt4pzhqfhvn1z4b6584mxxd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.