Rust Coding
Use this skill for anything Rust-related. It encodes specific conventions that must be followed. Always consult it before reading or writing Rust code.
Install
$ agentstack add skill-perongh-skills-rust-coding ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-perongh-skills-rust-coding) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Rust Coding
File Size
Recommended file size is under 500 lines. Hard limit is 1000 lines; if reached, break the file down.
Error Handling
Use thiserror for library errors, anyhow in binary/CLI layers.
Documentation
Doc comments on every public item. cargo doc should produce useful, navigable documentation.
Before Commit
Before committing, cargo fmt --check, cargo clippy, and cargo test must pass.
Lint Suppressions
Follow the lint policy. Any non-test lint suppression must use the narrowest scope possible and include an explicit reason = "...".
Panic Policy
Do not use panic-prone code casually in non-test code. unwrap, expect, and similar operations are acceptable when a local invariant guarantees the value and making it fallible would only force fallibility onto callers up the call chain; make that invariant explicit in the code or comments.
Unsafe Policy
Each unsafe block must contain a single operation with a SAFETY comment explaining why the invariant holds. Every unsafe function must have a # Safety doc section.
Performance
Hot paths must have benchmarks. Any performance regression must be explained to the human before committing.
Hygiene
Handle every Result — never silently discard. Do not hold locks or RefCell borrows across await points. Do not mark functions async unless they await.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: PeronGH
- Source: PeronGH/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.