Crate Publishing Skill

Project scaffolding and crates.io releases - an Agent Skill for Rust 1.97.0 and workspace publishing.

What This Skill Does

Creates library crate skeletons with lib.rs, examples/, tests/, README.md, LICENSE, and Cargo.toml metadata (description, repository, keywords, categories, rust-version). Runs cargo publish --dry-run and doc test validation.

When to Invoke

• Open-sourcing internal utility crate
• Preparing first 0.1.0 publish
• Reviewing publish PR for metadata and semver
• Splitting module from monolith into standalone crate

Inputs

Outputs

• Cargo.toml with workspace-ready deps
• src/lib.rs with crate-level docs
• examples/basic.rs
• CHANGELOG.md stub
• Publish checklist commands

Guardrails

1. cargo publish --dry-run must pass before real publish.
2. No path/git deps in published manifest unless versioned on crates.io.
3. docs.rs builds - package.metadata.docs.rs features set.
4. SemVer on 0.x - document breaking minor policy.
5. Crate name matches repo - discoverability and trust.

Recipe

cargo test --all-features
cargo doc --no-deps
cargo publish --dry-run
cargo package --list
# cargo publish when ready

Working Example

[package]
name = "acme-utils"
version = "0.1.0"
edition = "2024"
rust-version = "1.97"
license = "MIT OR Apache-2.0"
description = "Shared utilities for Acme Rust services"
repository = "https://github.com/acme/acme-utils"

FAQs

Related

• Publishing to crates.io
• Cargo.toml explained
• Release & versioning
• Essential Crates Best Practices

Stack versions: This page was written for Rust 1.97.0 (edition 2024), Tokio 1.x, Axum 0.8, serde 1.0, sqlx 0.8, clap 4, and Polars 0.46+.