Skip to content
TrustedSkillsbeta
Back to all skills

Rust Call Graph

Checked
actionbook·vlatest·backend

Analyzes Rust code call graphs within Actionbook projects to identify dependencies and potential optimization opportunities.

Repository

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-call-graph -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

actionbook

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 actionbook/rust-skills at 5c40d3ad78.

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

Commit
5c40d3ad78
Manifest
skills/rust-call-graph/SKILL.md
Scanned
1 file, 187 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

The rust-call-graph skill generates visual call graphs directly from Rust source code, helping developers understand function dependencies and execution flows. It processes .rs files to map out how different parts of a program interact without requiring manual tracing.

When to use it

  • Analyze complex legacy Rust codebases to identify tightly coupled modules before refactoring.
  • Debug performance bottlenecks by visualizing the sequence of function calls during specific operations.
  • Onboard new team members by providing an immediate overview of the project's architectural structure.
  • Validate that recent changes in one module did not inadvertently break dependencies in others.

Key capabilities

  • Parses Rust source files to extract function definitions and call sites.
  • Constructs a directed graph representing the hierarchy and relationships between functions.
  • Renders interactive visualizations showing parent-child relationships in the call stack.
  • Handles both simple scripts and large-scale library structures efficiently.

Example prompts

  • "Generate a call graph for src/main.rs to show all entry points."
  • "Visualize the dependencies between database.rs and api_handler.rs."
  • "Create a call graph highlighting functions that are called more than five times in this crate."

Tips & gotchas

Ensure your Rust project is clean and free of syntax errors before running the analysis, as parsing failures can halt graph generation. For very large projects with thousands of functions, consider limiting the scope to specific modules to keep the visualization readable.