About rust-crate-publishing-readiness
A skill for preparing Rust crates for publication or sharing, focused on the package consumers receive rather than service deployment. It covers metadata, API and documentation checks, Cargo dry runs, and release contents.
Key features
- 01Metadata and license review
- 02Public API and feature checks
- 03Tests, docs, and formatting checks
- 04Cargo package dry runs
- 05Package contents and secret checks
- 06Clean release-state review
Use cases
- 01Prepare a crate release pull request
- 02Review Cargo metadata and package files
- 03Diagnose package dry-run failures
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ lvtd-llc/ skills --skill rust-crate-publishing-readinessAfter installing, type/rust-crate-publishing-readinessin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
guidelines.mdagents/openai.yamlreferences/publishing-patterns.mdworkflows/prepare-crate-release.mdDetails
From the project READMERust 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 packageorcargo 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.