Index of every page on this site: llms.txt

Author a Skill for your Rust crate

Draft a Skill for your crate, include its files, and check the package with Cargo before publishing to crates.io.

Authoring guide

1. Draft your Skill

crates.io

Choose your package

Open your agent in the package repository. Give it these instructions to draft your Skill.

Read the authoring Skill

Read https://raw.githubusercontent.com/skilld-dev/skilld/main/skills/generate-package-skill/SKILL.md. Draft a Skill for the package I maintain, published through crates.io, using this repository. Read Cargo.toml, the public API, and the current official documentation. Show the draft for review before replacing existing Skills.

Point your agent at the crate directory containing Cargo.toml. For a workspace, use the member crate you maintain. Ask it to save the draft in skills/your-skill/SKILL.md.

Cover public exports, feature flags, error handling, and supported Rust versions. State which features each example needs. Explain ownership or lifetime constraints where they affect real usage.

2. Review the draft

Compile the examples with their stated features. Use the cross-Agent selection and task checks before publishing the Skill. Check that they use public APIs from the release you plan to publish. Remove generic Rust advice and cite your crate documentation for specific rules. Review the draft before committing it.

3. Include and check the Skill

Check include and exclude under [package] in Cargo.toml. If you use an inclusion list, add skills/** beside the existing release paths. Keep every file referenced by SKILL.md. See Cargo's include and exclude rules.

From the crate directory, list the archive contents:

cargo package --list

Confirm the list includes your Skill and its references. Then run the publishing checks without uploading:

cargo publish --dry-run

See the Cargo package and Cargo publish references.

4. Publish and share

Commit the reviewed Skill and publish through your normal crates.io release process. Link to its repository directory from the crate README. Adding the crate as a dependency does not automatically install the Skill into an agent. Review the Skill when public APIs, default features, or compiler requirements change.