rust-systems
v2.56.0Rust patterns for CLI tools, backend services, and general application code. Use when working with Rust, Cargo workspaces, axum/tokio services, clap CLIs, as...
⭐ 0· 40·0 current·0 all-time
byIlia Alshanetsky@iliaal
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description, the SKILL.md, and the two reference docs all describe Rust application patterns (CLIs, axum/tokio services, clap). There are no required binaries, env vars, or install steps that are unrelated to that purpose.
Instruction Scope
The instructions are prose guidance and code examples for writing/testing Rust services and CLIs. The skill manifest lists file paths ('**/*.rs,**/Cargo.toml') which is consistent with operating on Rust projects. The instructions do not tell the agent to read arbitrary system files, exfiltrate data, or call external endpoints beyond normal development/testing guidance.
Install Mechanism
No install spec and no code files to execute; this is instruction-only, the lowest-risk installation model.
Credentials
The skill itself requires no environment variables, but the documentation mentions common environment usage (e.g., DATABASE_URL, MYAPP_API_KEY, RUST_LOG) and config files as implementation details for projects. This is expected for a Rust patterns guide, but users should note the doc references environment-backed workflows (sqlx offline cache, config layering).
Persistence & Privilege
Defaults are used (not always:true). The skill is user-invocable and can be called autonomously by the agent (platform default), which is appropriate for a guidance skill and not combined with broad credential or install demands.
Assessment
This skill is a documentation-only guide for Rust application patterns and appears coherent with its purpose. It doesn't request credentials or install software, but it assumes typical developer workflows (e.g., use of DATABASE_URL, config files, and CI that may need sqlx prepared queries). Before enabling autonomous use, consider: (1) permit it only on repos containing Rust code you trust (it is intended to operate on **/*.rs and Cargo.toml files); (2) be careful when following any advice that refers to environment variables or secret-bearing config files—those examples are illustrative and the skill itself will not declare or require your secrets; (3) if you expect the agent to make code changes automatically, review diffs or restrict the agent's write permissions so you approve changes before they are applied.Like a lobster shell, security has layers — review code before you run it.
latestvk977v63b6zdf42cptwx7g1qv7x84tw3f
License
MIT-0
Free to use, modify, and redistribute. No attribution required.