Skip to content
TrustedSkillsbeta
Back to all skills

Rust Symbol Analyzer

Checked
actionbook·vlatest·backend

Analyzes Rust code symbols from Actionbook projects to extract metadata for documentation generation and tooling.

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-symbol-analyzer -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-symbol-analyzer/SKILL.md
Scanned
1 file, 205 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

Rust Symbol Analyzer

What it does

This skill enables AI agents to parse and analyze Rust source code files, extracting structured symbol information such as functions, structs, and methods. It provides a programmatic way to understand code topology without manual inspection.

When to use it

  • Codebase Navigation: Quickly locate specific modules or dependencies within a large Rust project.
  • Dependency Analysis: Identify external crates used in a specific function or file.
  • Refactoring Support: Map out call graphs to understand the impact of changing a specific struct or trait.
  • Documentation Generation: Automatically extract symbol signatures for generating API docs.

Key capabilities

  • Parses Rust source files into an internal representation.
  • Extracts detailed metadata for functions, structs, enums, and traits.
  • Supports filtering symbols by visibility (public/private) and attributes.
  • Returns structured JSON data suitable for further processing or display.

Example prompts

  • "Analyze src/main.rs and list all public functions along with their signatures."
  • "Find every struct in the project that derives the Serialize attribute."
  • "Extract the call graph starting from the run function in lib.rs."

Tips & gotchas

Ensure the target file is valid Rust code; syntax errors may cause parsing failures. For large projects, consider splitting analysis into smaller chunks to avoid memory overhead.