Skip to content
TrustedSkillsbeta
Back to all skills

Lint

Checked
redisearch·vlatest·backend

Lint analyzes your Redis search queries for potential performance issues and suggests improvements to optimize speed and efficiency.

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 lint -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/lint/SKILL.md
Scanned
1 file, 52 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 Lint skill checks code quality and formatting before committing changes. It analyzes your codebase for lint errors and identifies any formatting issues that need to be addressed. This helps ensure a consistent coding style and catches potential problems early in the development process, improving overall code maintainability. The skill uses make commands and cargo for Rust-specific checks.

When to use it

  • Before committing changes to a repository.
  • To enforce consistent code formatting within a project.
  • When identifying and resolving linting errors.
  • As part of a continuous integration/continuous delivery (CI/CD) pipeline.

Key capabilities

  • Runs lint checks for potential errors.
  • Checks code formatting according to defined standards.
  • Provides instructions on fixing common Clippy warnings and errors.
  • Includes guidance on adding missing license headers.
  • Supports Rust-specific linting using cargo clippy.

Example prompts

  • "Run a lint check on the current codebase."
  • "Check the formatting of my code."
  • "Fix any formatting issues I have."

Tips & gotchas

  • The skill relies on make commands and cargo, so these tools must be available in your environment.
  • If Clippy reports warnings or errors, it's important to fix them before proceeding.
  • For Rust-only linting, navigate to the src/redisearch_rs directory and run cargo clippy --all-targets --all-features.