rust-dependency-portabilitylisted

## Outcome Produce a repository-aligned dependency or portability change with an explicit MSRV/toolchain contract, minimal justified feature surface, reviewed supply-chain impact, platform-correct paths and processes, and verification across the combinations the project actually supports. ## Compatibility Portable across Claude Code, Codex, and OpenCode. The target repository controls Rust toolchain, edition, MSRV, resolver, lockfile, supported targets, features, and CI commands; Edition 2024 examples require Rust 1.85 or newer. Templates are adaptable snippets and do not authorize adding `directories` or platform crates. Network access for registry, advisory, license, and maintenance research is optional; without it, report freshness gaps and do not claim a current supply-chain review. Native-client compatibility remains unverified until a validated report records the client version and exact source SHA. ## Use this skill when - Adding, removing, upgrading, replacing, or feature-tuning a Cargo dependency. - Defining or validating `rust-version`, edition, resolver, lockfile, or workspace inheritance. - Reviewing licenses, advisories, maintenance, unsafe/FFI, native libraries, or transitive cost. - Making paths, application directories, process execution, environment, or OS-specific behavior portable across supported targets. ## Do not use this skill when - Crate/module/workspace decomposition is the requested deliverable; use `rust-project-architecture`. - HTTP/gRP