Skip to content
TrustedSkillsbeta
Back to all skills

Rust Symbol Analyzer

Checked
goooice·vlatest·backend

Analyzes Rust code symbols (functions, structs, traits) to extract metadata and dependencies for automated tooling.

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 goooice/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

goooice

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 goooice/rust-skills at 57af2e8da9.

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

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

What it does

The goooice-rust-symbol-analyzer skill provides analysis of Rust code, likely extracting information about symbols (functions, variables, structs, etc.). It allows AI agents to understand and reason about Rust source code. This can be used for tasks like code documentation generation, bug detection, or automated refactoring.

When to use it

  • Code Understanding: When an agent needs to comprehend the purpose of a specific function or module within a Rust project.
  • Documentation Generation: To automatically create summaries and explanations of Rust code components.
  • Automated Refactoring: For identifying potential areas for improvement or optimization in existing Rust projects.

Key capabilities

  • Symbol extraction from Rust source code
  • Analysis of Rust code structure
  • Potential for documentation generation (implied)

Example prompts

  • "Analyze this Rust code and tell me what functions are defined: [code snippet]"
  • "Describe the purpose of the main function in this file: [file path]"
  • "List all structs declared in this project."

Tips & gotchas

The skill's effectiveness depends on providing accurate and complete Rust code as input. The specific output format and level of detail may vary depending on the underlying implementation.