Elasticsearch

What This Skill Does

The Elasticsearch skill enables the OpenClaw AI agent to interface directly with Elasticsearch clusters. It provides a robust framework for managing search indices, defining complex mappings, executing high-performance queries, and handling bulk data operations. This skill is designed to abstract away the nuances of document indexing, ensuring that data is stored in a way that maximizes search accuracy while adhering to industry best practices regarding schema design and query efficiency.

Installation

To install this skill, execute the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/elasticsearch This command pulls the latest stable version from the openclaw/skills repository.

Use Cases

This skill is ideal for developers building high-scale search infrastructure. Common use cases include:

• Designing schema architectures for e-commerce product catalogs where fast filtering and full-text search must coexist.
• Implementing efficient logging pipelines using bulk indexing to minimize cluster overhead.
• Optimizing user-facing search bars with language-specific analyzers (e.g., english) to handle stemming and tokenization.
• Performing data migration or reindexing tasks to update field types without causing downtime.
• Implementing deep pagination strategies for massive datasets where standard limit/offset queries fail.

Example Prompts

1. "Initialize a new index for user profiles with strict dynamic mapping, ensuring fields like 'email' and 'username' are set as keyword types while 'bio' is text."
2. "Perform a bulk upload of the items in the 'inventory.json' file to the 'store_v2' index with a batch size of 5MB."
3. "Optimize the current query for user product searches by moving categorical filters into a filter context and using a search_after cursor for consistent pagination."

Tips & Limitations

• Schema Rigidity: Once a field is indexed, its type is immutable. Always define explicit mappings to avoid dynamic mapping disasters.
• Performance: Use the profile: true parameter to debug slow queries. Avoid leading wildcards as they trigger expensive full-scans.
• Nested Objects: If you are dealing with arrays of objects, use the nested type to preserve attribute associations; otherwise, Elasticsearch will flatten the data and break your queries.
• Pagination: Never rely on from + size for deep pagination. Use search_after for large datasets to maintain performance and consistency.
• Filtering: Leverage filter context whenever relevance scoring is not required to take advantage of the built-in request cache.