Skip to content
TrustedSkillsbeta
Back to all skills

Rust Quality Checker

Checked
matteocervelli·vlatest·backend·MIT

Analyzes Rust code for common errors, style violations, and potential performance bottlenecks using clippy and other tools.

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 matteocervelli/llms --skill rust-quality-checker --full-depth -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

matteocervelli

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 matteocervelli/llms at 1e1f2089eb.

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

Commit
1e1f2089eb
Manifest
.archive/claude-v1/skills/rust-quality-checker/SKILL.md
Scanned
1 file, 738 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

This skill analyzes Rust code and provides feedback on its quality, identifying potential issues and suggesting improvements. It leverages external tools to perform linting and static analysis, helping developers maintain a high standard of code. The tool aims to improve code reliability and reduce the likelihood of runtime errors.

When to use it

  • Code Review Automation: Integrate into CI/CD pipelines for automated quality checks before merging changes.
  • Learning Rust Best Practices: Use to understand common pitfalls and learn how to write idiomatic, robust Rust code.
  • Refactoring Existing Codebases: Identify areas in a legacy codebase that could benefit from improvements based on current best practices.
  • New Project Setup: Enforce quality standards from the beginning of a new project by integrating it into your development workflow.

Key capabilities

  • Rust linting
  • Static analysis
  • Code quality feedback
  • Integration with external tools

Example prompts

  • "Check this Rust code for potential errors and style issues: [paste code here]"
  • "Analyze this function and suggest improvements to its efficiency and readability: [paste function definition]"
  • "Run a lint check on my project's src/main.rs file."

Tips & gotchas

The skill relies on external tools, so ensure these dependencies are available in your environment for accurate results. The quality of the feedback depends on the configuration and capabilities of the underlying analysis tools.