rust-coding-skill
Use this skill whenever editing `*.rs` files in the `rust/` SDK in order to write idiomatic, efficient, well-structured Rust code
Best for Rust SDK developmentWorks with GitHubLow risk
⌘source
- author
@github- language
- TypeScript
★8.6kstars
1.2kforks
May 7, 2026
✦overview.md
Key Features
- ·Priority: readable > correct > performant
- ·Centralized error type crate::Error
- ·No anyhow::Result in library code
- ·Prefer ?, let-else, if let; expect for invariants
- ·unwrap() only in tests (enforced by Clippy)
- ·Use inspecterr for logging errors
Use Cases
- →Writing new Rust modules inside the SDK
- →Refactoring error handling to use a single error type
- →Reviewing PRs for compliance with SDK conventions
- →Debugging async code that needs correct error propagation
Best for
- ✓Rust SDK development
- ✓Teams enforcing error-handling standards
- ✓Code review automation
Not ideal for
- !Standalone binaries
- !Projects using anyhow pervasively
FAQs
name
rust-coding-skill
description
Use this skill whenever editing `*.rs` files in the `rust/` SDK in order to write idiomatic, efficient, well-structured Rust code
Rust Coding Skill
Opinionated Rust rules for the Copilot Rust SDK (rust/). Priority order:
- Readable code — every line should earn its place
- Correct code — especially in concurrent/async contexts
- Performant code — think about allocations, data structures, hot paths
Error handling
The SDK's public error type is crate::Error (rust/src/error.rs). Add new
variants there rather than introducing parallel error enums per module — every
public failure mode is part of the API contract and should be expressible in one
type. Internal modules can use thiserror enums when a richer local taxonomy
helps; convert at the boundary.
anyhow is reserved for binaries and example code. Library code never returns
anyhow::Result — callers can't pattern-match on anyhow::Error, so it would
prevent them from handling specific failures.
In production code, prefer ?, let-else, and if let. Reach for expect("…")
when an invariant cannot fail and the message would help debug a future
regression. unwrap() belongs in tests only — Clippy enforces this in the SDK
via #![cfg_attr(test, allow(clippy::unwrap_used))] in lib.rs.
$install
1-click copynpx skills add github/copilot-sdk --skill rust-coding-skillSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.