Rust Docs Guidelines
CheckedHelps with Rust, guidelines 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
Run this in your project
terminal$ npx skills add redisearch/redisearch --skill rust-docs-guidelines -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto 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.
Automated safety checks
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
- Scanned
- 1 file, 35 lines
About this skill
The rust-docs-guidelines skill provides AI agents with access to Redisearch documentation specifically tailored for Rust development. It enables precise retrieval of code examples, API references, and best practices within the Redisearch ecosystem using the Rust language.
When to use it
- Debugging complex indexing issues in a Rust-based Redisearch application.
- Finding specific syntax for creating or querying indexes in Rust.
- Learning how to integrate Redisearch functionality into new Rust projects.
- Verifying correct usage of Redisearch commands within Rust codebases.
Key capabilities
- Access to official Redisearch documentation focused on Rust implementations.
- Retrieval of specific API methods and function signatures for Rust developers.
- Searchable content covering indexing strategies, query syntax, and configuration options.
- Context-aware answers derived from the
redisearchrepository's documentation structure.
Example prompts
- "Show me how to create a full-text index in Redisearch using Rust."
- "What are the best practices for configuring Redisearch indexes in a Rust application?"
- "Find the Rust code example for querying a geospatial index in Redisearch."
Tips & gotchas
Ensure your AI agent has context about your specific Rust version or Redisearch module version, as documentation may vary slightly between releases. This skill is specialized; if you need general Rust syntax unrelated to Redisearch, use a broader Rust documentation skill instead.