Rust Crate Publishing Readiness
Use this skill before publishing or sharing a Rust crate. It focuses on the
consumer-facing package, not on deployment of a running service.
Core Workflow
- Verify package metadata, license, README, repository, and categories.
- Check public API, feature flags, examples, and docs from a consumer's view.
- Run tests, docs, formatting, and feature-matrix checks.
- Run
cargo package or cargo publish --dry-run.
- Inspect packaged contents for missing files and accidental secrets.
- Publish only from a clean, tagged, intentional release state.
Read Next
| Task |
Load |
| Prepare a crate release PR |
guidelines.md, workflows/prepare-crate-release.md |
| Review Cargo metadata and package contents |
references/publishing-patterns.md |
| Diagnose dry-run failures |
references/publishing-patterns.md |
Source Notes
Guidance is transformed and paraphrased from Herbert Wolverson,
Advanced Hands-On Rust, especially Chapter 15 on sharing libraries and the
earlier chapters on tests, docs, benchmarks, and features. Examples are
original skeletons.
1---2name: rust-crate-publishing-readiness3description: Prepare Rust crates for publishing with Cargo metadata, versioning, README and license checks, package dry-runs, feature verification, docs.rs readiness, examples, changelog notes, and secret-safe release gates. Use before cargo publish, crate release PRs, or sharing a reusable Rust library.4license: MIT5compatibility: Codex, Claude Code, and other Agent Skills-compatible clients.6metadata:7 version: "0.1.0"8 displayName: Rust Crate Publishing Readiness9 category: Rust10 tags: rust,cargo,publishing,release,library11---1213# Rust Crate Publishing Readiness1415Use this skill before publishing or sharing a Rust crate. It focuses on the16consumer-facing package, not on deployment of a running service.1718## Core Workflow19201. Verify package metadata, license, README, repository, and categories.212. Check public API, feature flags, examples, and docs from a consumer's view.223. Run tests, docs, formatting, and feature-matrix checks.234. Run `cargo package` or `cargo publish --dry-run`.245. Inspect packaged contents for missing files and accidental secrets.256. Publish only from a clean, tagged, intentional release state.2627## Read Next2829| Task | Load |30|------|------|31| Prepare a crate release PR | `guidelines.md`, `workflows/prepare-crate-release.md` |32| Review Cargo metadata and package contents | `references/publishing-patterns.md` |33| Diagnose dry-run failures | `references/publishing-patterns.md` |3435## Source Notes3637Guidance is transformed and paraphrased from Herbert Wolverson,38*Advanced Hands-On Rust*, especially Chapter 15 on sharing libraries and the39earlier chapters on tests, docs, benchmarks, and features. Examples are40original skeletons.
ConcertoNotes