Rust Cleanup
ListedAutomatically removes unused dependencies and outdated code in Rust projects, improving build times and reducing bloat.
Install on your platform
rust-cleanup. alb-o/pw-rs is deleted or private, so it cannot be installed from.We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.
What we know about this skill
Publisher
alb-o
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
We could not read this skill's source, so none of the checks below were run.
About this skill
What it does
The rust-cleanup skill automates the process of cleaning up Rust project dependencies. It removes unused crates, updates outdated dependencies, and generally optimizes a Rust project's Cargo.toml file. This helps reduce build times, minimize binary sizes, and improve overall project health.
When to use it
- Large projects: Ideal for projects with many dependencies where manual cleanup is time-consuming and error-prone.
- Dependency bloat: Use when your
Cargo.tomlseems overly large or you suspect unused crates are present. - Build performance issues: If builds are slow, cleaning up dependencies can often contribute to faster compilation times.
- Reducing binary size: Removing unnecessary dependencies directly reduces the final executable's footprint.
Key capabilities
- Removes unused crates from
Cargo.toml. - Updates outdated Rust dependencies.
- Optimizes dependency versions.
Example prompts
- "Clean up my Rust project and remove any unused dependencies."
- "Update all the dependencies in my Cargo.toml to their latest compatible versions."
- "Optimize my Rust project's dependencies for size."
Tips & gotchas
The skill requires a valid Cargo.toml file to be present in the working directory. It’s recommended to review the changes made by the tool before committing them, as aggressive cleanup could potentially break existing functionality if not carefully considered.