agentleFS
TeddyAlbinaTeddyAlbina/skills/rust-deps-visualizer/SKILL.md

rust-deps-visualizer

Skill2 starsChanged 28 days agoMITView on GitHub

Visualize Rust project dependencies as ASCII art. Triggers on: /deps-viz, dependency graph, show dependencies, visualize deps, 依赖图, 依赖可视化, 显示依赖

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use these box-drawing characters:

    line 64
  2. Very specific:

    Check for Cargo.toml in current directory

    line 103
  3. Very specific:

    Run cargo tree with specified options

    line 104

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Rust Dependencies Visualizer

Generate ASCII art visualizations of your Rust project's dependency tree.

Usage

/rust-deps-visualizer [--depth N] [--features]

Options:

  • --depth N: Limit tree depth (default: 3)
  • --features: Show feature flags

Output Format

Simple Tree (Default)

my-project v0.1.0
├── tokio v1.49.0
│   ├── pin-project-lite v0.2.x
│   └── bytes v1.x
├── serde v1.0.x
│   └── serde_derive v1.0.x
└── anyhow v1.x

Feature-Aware Tree

my-project v0.1.0
├── tokio v1.49.0 [rt, rt-multi-thread, macros, fs, io-util]
│   ├── pin-project-lite v0.2.x
│   └── bytes v1.x
├── serde v1.0.x [derive]
│   └── serde_derive v1.0.x (proc-macro)
└── anyhow v1.x [std]

Implementation

Step 1: Parse Cargo.toml for direct dependencies

cargo metadata --format-version=1 --no-deps 2>/dev/null

Step 2: Get full dependency tree

cargo tree --depth=${DEPTH:-3} ${FEATURES:+--features} 2>/dev/null

Step 3: Format as ASCII art tree

Use these box-drawing characters:

  • ├── for middle items
  • └── for last items
  • │ for continuation lines

Visual Enhancements

Dependency Categories

my-project v0.1.0
│
├─[Runtime]─────────────────────
│ ├── tokio v1.49.0
│ └── async-trait v0.1.x
│
├─[Serialization]───────────────
│ ├── serde v1.0.x
│ └── serde_json v1.x
│
└─[Development]─────────────────
  ├── criterion v0.5.x
  └── proptest v1.x

Size Visualization (Optional)

my-project v0.1.0
├── tokio v1.49.0        ████████████ 2.1 MB
├── serde v1.0.x         ███████ 1.2 MB
├── regex v1.x           █████ 890 KB
└── anyhow v1.x          ██ 120 KB
                         ─────────────────
                         Total: 4.3 MB

Workflow

  1. Check for Cargo.toml in current directory
  2. Run cargo tree with specified options
  3. Parse output and generate ASCII visualization
  4. Optionally categorize by purpose (runtime, dev, build)

Related Skills

WhenSee
Crate selection advicem11-ecosystem
Workspace managementm11-ecosystem
Feature flag decisionsm11-ecosystem

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.