Skip to content
TrustedSkillsbeta
Back to all skills

Rust Code Quality Guide

Checked
masayuki-kono·vlatest·backend·MIT

Analyzes Rust code for common pitfalls, suggesting improvements in safety, performance, and idiomatic style based on Kono's expertise.

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 masayuki-kono/agent-skills --skill rust-code-quality-guide -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

masayuki-kono

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 masayuki-kono/agent-skills at e46e1a51b9.

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

Commit
e46e1a51b9
Manifest
skills/rust-code-quality-guide/SKILL.md
Scanned
1 file, 129 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 suggestions for improving its quality. It leverages established best practices and linting rules to identify potential issues, including stylistic inconsistencies, common errors, and opportunities for optimization. The tool aims to enhance code readability, maintainability, and overall robustness within a Rust project.

When to use it

  • Code Review: Automate initial code review checks before human review to catch basic quality issues early on.
  • New Project Setup: Ensure new Rust projects adhere to consistent coding standards from the start.
  • Refactoring Existing Code: Identify areas in legacy code that could benefit from improvements and modernization.
  • Continuous Integration (CI): Integrate into CI pipelines to enforce code quality checks with every commit.

Key capabilities

  • Rust code analysis
  • Linting based on established best practices
  • Identification of stylistic inconsistencies
  • Error detection and prevention
  • Optimization suggestions

Example prompts

  • "Analyze this Rust code snippet for potential quality issues: [code snippet]"
  • "Run the linter on my project's src/main.rs file."
  • "Suggest improvements to this function to enhance readability: [function definition]"

Tips & gotchas

  • This skill requires a Rust development environment and access to the codebase being analyzed.
  • The quality of suggestions depends on the complexity and structure of the code provided.