Skip to content
TrustedSkillsbeta
Back to all skills

Redis

Checked
thinkfleetai·vlatest·database

Efficiently manages and queries Redis data stores, optimizing performance and simplifying integration for thinkfleetAI applications.

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 thinkfleetai/thinkfleet-engine --skill redis -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

thinkfleetai

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 thinkfleetai/thinkfleet-engine at 1256c5192f.

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

Commit
1256c5192f
Manifest
skills/redis/SKILL.md
Scanned
1 file, 35 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 provides access to a Redis database, enabling AI agents to store and retrieve data with high performance. It facilitates key-value storage, allowing agents to manage session information, caching frequently accessed content, or tracking user activity. The skill allows for persistent data management beyond the agent's runtime.

When to use it

  • Session Management: Store and retrieve user session data across multiple interactions.
  • Caching: Cache API responses or computationally expensive results to improve response times.
  • Real-time Analytics: Track events and metrics in real time for dashboards or analysis.
  • Persistent Storage: Store agent state or other important information that needs to survive restarts.

Key capabilities

  • Redis key-value store access
  • Data persistence
  • High performance data retrieval

Example prompts

  • "Store the user's shopping cart with ID 12345."
  • "Retrieve the session data for user 'john.doe'."
  • “Increment the view count for product ‘XYZ’ by one.”

Tips & gotchas

The skill requires a running Redis instance to connect to. Ensure that your agent has the necessary connection details (host, port, password) configured correctly before attempting to interact with the database.