Apollo's Rust best practices
Write idiomatic Rust — borrowing, error handling, Clippy, testing, generics and the type-state pattern, chapter by chapter
- What
- Write idiomatic Rust — borrowing, error handling, Clippy, testing, generics and the type-state pattern, chapter by chapter
- Cost
- Free
- Needs
- Rust 1.70+ with cargo, clippy and rustfmt available; a Rust project to write or review
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — Apollo GraphQL's Rust best-practices handbook as an agent skill: nine chapters covering coding styles and idioms (borrowing vs cloning, Option/Result handling, iterators), Clippy configuration and key lints, a performance mindset (profiling, avoiding redundant clones, zero-cost abstractions), error handling (Result vs panic, thiserror vs anyhow), automated testing conventions, generics vs dynamic dispatch, the type-state pattern, and comments vs documentation — with a quick-reference section the agent can apply directly. By @apollographql, listed here with credit to its creator. Honest caveats: guidance only — it reviews and shapes code, it doesn't write your project for you; targets Rust 1.70+ with cargo/clippy/rustfmt available. Discovered via skills.sh. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Apollo's Rust best practices is a free skill for Muse. By @apollographql, listed here with credit to its creator. Honest caveats: guidance only — it reviews and shapes code, it doesn't write your project for you; targets Rust 1.70+ with cargo/clippy/rustfmt available.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 5f02fcfStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Rust 1.70+ with cargo, clippy and rustfmt available; a Rust project to write or review Install "Apollo's Rust best practices" for me. Give my agent Apollo's Rust best-practices handbook — nine chapters on idioms, Clippy, performance, error handling, testing, generics, the type-state pattern and documentation, plus a quick reference for direct application Repository: https://raw.githubusercontent.com/apollographql/skills/5f02fcfcebec678e2e55777b639e32346622a963/skills/rust-best-practices/SKILL.md Pinned version: install the code at commit 5f02fcfcebec678e2e55777b639e32346622a963 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the apollographql-skills-rust-best-practices skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "apollographql-skills-rust-best-practices". 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. nothing beyond having Rust 1.70+ with clippy/rustfmt — point it at code to write or review). 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 5f02fcf · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.