Rust coding guidelines: 50 core rules for idiomatic Rust

Prerequisites: a Rust project the agent can read and refactor — the skill is a style methodology, not software Install "Rust coding guidelines: 50 core rules for idiomatic Rust" for me. It gives my agent @actionbook's 50-rule Rust style playbook: Rust-specific naming (no get_ prefix, as_/to_/into_ conversions, iter conventions), error-handling discipline (? propagation, expect() over unwrap()), memory/lifetime habits, concurrency and async rules (atomics for primitives, never hold locks across await), macro discipline, a quick reference (rustfmt, clippy::all, doc comments), and a deprecated→better migration table. IMPORTANT: the repo states no license — fetch from the link only, and reproduce nothing beyond the link. Repository: https://github.com/actionbook/rust-skills/blob/main/skills/coding-guidelines/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "coding-guidelines". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my Rust project or file to review; nothing else — it's a methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.