Skip to content
TrustedSkillsbeta
Back to all skills

Rust Deps Visualizer

Checked
zhanghandong·vlatest·backend

Visually maps Rust project dependencies, identifying transitive relationships and potential conflicts for improved backend development.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add actionbook/rust-skills --skill rust-deps-visualizer -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

zhanghandong

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned zhanghandong/rust-skills at 5c40d3ad78.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 101 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The rust-deps-visualizer skill helps analyze and visualize dependencies in Rust projects. It parses Cargo.toml files to map out crate dependencies, showing both direct and transitive relationships. This makes it easier for developers to understand the structure of their project's dependency graph.

When to use it

  • You need a clear overview of your Rust project’s dependencies for debugging or optimization.
  • You're trying to identify unused or redundant crates in your project.
  • You want to document or present the dependency tree to team members or stakeholders.
  • You’re preparing to upgrade a crate and need to understand its impact on the rest of the project.

Key capabilities

  • Parses Cargo.toml files for dependency information
  • Visualizes both direct and transitive dependencies
  • Highlights potential issues like cyclic dependencies

Example prompts

  • "Visualize the dependency tree for my Rust project."
  • "Show me all transitive dependencies of the serde crate in this project."
  • "Generate a graph of my project's dependencies and highlight unused crates."

Tips & gotchas

  • Ensure your project has a valid Cargo.toml file before using this skill.
  • Large projects may take longer to process due to the complexity of dependency graphs.