Skip to content
TrustedSkillsbeta
Back to all skills

Verify

Checked
redisearch·vlatest·database

Verifies data integrity by querying a Redis database for expected values, ensuring accuracy and preventing inconsistencies.

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 verify -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/verify/SKILL.md
Scanned
1 file, 123 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 redisearch-verify skill allows AI agents to validate data integrity and query results directly within Redis databases. It ensures that search operations return accurate, consistent information before it is processed further by the application logic. This capability is essential for maintaining trust in data-driven workflows where precision is critical.

When to use it

  • Confirming that a complex full-text search returned all expected documents without false positives or negatives.
  • Validating schema changes or index updates immediately after deployment to prevent downstream errors.
  • Ensuring data consistency between Redis and external systems before triggering automated business processes.
  • Debugging query performance issues by verifying the actual state of the dataset against expected metrics.

Key capabilities

  • Direct verification of search results within the Redis environment.
  • Validation of data integrity for indexed datasets.
  • Real-time confirmation of index health and query accuracy.

Example prompts

  • "Verify that the 'products' index contains all items tagged with 'electronics' from the last 24 hours."
  • "Check if the user count in the 'sessions' key matches the total number of active connections reported by the load balancer."
  • "Validate that the full-text search for 'urgent maintenance' returned exactly three tickets and list their IDs."

Tips & gotchas

Ensure your AI agent has read permissions on the specific Redis keys it intends to verify, as unauthorized access will block validation attempts. For large datasets, consider sampling results rather than verifying every single entry to avoid performance bottlenecks during peak traffic times.