redis-query-engine

Design and optimize Redis Search indexes with FT.CREATE schemas and queries.

94|22|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/redis/agent-skills --skill redis-query-engine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redis-query-engine
Source: https://github.com/redis/agent-skills/tree/main/skills/redis-query-engine
Command: npx skills add https://github.com/redis/agent-skills --skill redis-query-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a structured framework for designing, indexing, and querying Redis data with Redis Search, reducing misconfigurations and downtimes in production.

Core Features & Use Cases

  • Guidance on DIALECT 2 usage for consistent query behavior and vector-search readiness
  • Field-type recommendations (TEXT, TAG, NUMERIC, GEO, GEOSHAPE, VECTOR) and index lifecycle best practices
  • Techniques for zero-downtime index updates via aliases and SKIPINITIALSCAN for new data scenarios
  • Practical examples for FT.CREATE, FT.SEARCH, FT.AGGREGATE, and query-tuning patterns
  • Use cases include designing indexes for HASH or JSON documents and optimizing production queries

Quick Start

Create a basic HASH index with FT.CREATE and run a sample FT.SEARCH to validate results.

Frequently Asked Questions about redis-query-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update Redis search indexes with zero downtime in production?

Update Redis search indexes with zero downtime by creating a new index and swapping it atomically using aliases. This approach prevents production query interruptions while you rebuild schemas or change field types.

How do I create a Redis search index for JSON documents?

Create a Redis search index for JSON documents by defining the schema in the FT.CREATE command with appropriate prefixes. Specify field types like TEXT, TAG, or NUMERIC to match your JSON structure.

What Redis search dialect should I use for FT.SEARCH queries?

Use DIALECT 2 for Redis search FT.SEARCH and FT.AGGREGATE queries. DIALECT 2 ensures consistent query behavior and provides readiness for advanced features like vector search.

When should I use SKIPINITIALSCAN with FT.CREATE?

Use SKIPINITIALSCAN with FT.CREATE when adding indexes for new data scenarios. It skips scanning existing data, reducing initial indexing overhead when you only need to index new documents going forward.

What field types should I choose for Redis search indexing?

Choose Redis search field types based on data needs: TEXT for full-text, TAG for exact matches, NUMERIC for ranges, GEO for coordinates, and VECTOR for similarity searches. Selecting correctly optimizes query performance.

Can I optimize FT.AGGREGATE queries for production Redis search?

Optimize FT.AGGREGATE queries in production by applying query-tuning patterns and selecting appropriate field types during indexing. Proper schema design reduces query latency and improves aggregation efficiency.