Skip to content
TrustedSkillsbeta
Back to all skills

Check Rust Coverage

Checked
redisearch·vlatest·backend

Analyzes Redisearch codebases to identify areas lacking Rust test coverage, improving reliability and maintainability.

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 redisearch/redisearch --skill check-rust-coverage -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

redisearch

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 redisearch/redisearch at c8f9d94e77.

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

Commit
c8f9d94e77
Manifest
.skills/check-rust-coverage/SKILL.md
Scanned
1 file, 31 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 allows AI agents to verify code coverage metrics specifically for Rust projects. It executes coverage analysis tools to determine how much of the source code is exercised by existing tests, ensuring quality assurance in backend development workflows.

When to use it

  • Before merging a pull request to confirm new test cases adequately cover added logic.
  • During CI/CD pipelines to enforce minimum coverage thresholds for Rust services.
  • When auditing legacy codebases to identify untested modules requiring attention.
  • To generate reports for stakeholders on the current state of test reliability.

Key capabilities

  • Analyzes Rust source code and associated test suites.
  • Calculates specific line, function, or branch coverage percentages.
  • Identifies uncovered lines or functions within the project structure.
  • Integrates directly into automated testing workflows for immediate feedback.

Example prompts

  • "Run a coverage check on my Rust backend service and summarize which modules have less than 80% coverage."
  • "Compare the code coverage of the main branch against the feature branch to see if new tests were added."
  • "List all uncovered functions in the auth module of this Rust project."

Tips & gotchas

Ensure your Rust project has a compatible test runner (like cargo) configured before invoking this skill, as it relies on standard coverage tools. Coverage metrics can vary based on how the tool is configured; specify flags if you need specific report formats or thresholds.