Skip to content
TrustedSkillsbeta
Back to all skills

Rust Testing

Checked
autumnsgrove·vlatest·backend

Helps with Rust, testing as part of developing backend services and APIs workflows.

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 autumnsgrove/lattice --skill rust-testing -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

autumnsgrove

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 autumnsgrove/lattice at edebdc71a7.

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

Scanned
1 file, 223 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-testing skill enables AI agents to execute Rust unit tests directly within the agent's environment. It automates the verification of code correctness by running test suites defined in Cargo.toml and src directories, providing immediate feedback on compilation errors or failing assertions.

When to use it

  • Validate new logic changes before merging code into a shared repository.
  • Ensure library dependencies are correctly resolved and compatible with your Rust version.
  • Automate regression checks during iterative development cycles for backend services.
  • Verify that generated code adheres to expected behavior without manual intervention.

Key capabilities

  • Executes cargo test commands across specified project paths.
  • Captures stdout/stderr output from failing tests for debugging.
  • Integrates seamlessly with Rust projects using standard Cargo structures.
  • Supports both unit and integration test definitions within the crate.

Example prompts

"Run all unit tests in my Rust backend service to check for recent regressions." "Execute the test suite for the new authentication module and report any failures." "Validate that the latest dependency update doesn't break existing functionality by running cargo test."

Tips & gotchas

Ensure your project has a valid Cargo.toml file before invoking the skill, as it is required to locate test definitions. The agent will fail gracefully if no tests are found in the specified directory, so verify your test coverage first.