Meilisearch

What This Skill Does

The Meilisearch skill for OpenClaw provides a robust framework for managing, tuning, and deploying Meilisearch instances. It acts as an orchestrator for search engine operations, enabling you to manage index configurations, handle complex document indexing, and implement production-grade search security. The skill abstracts the complexity of Meilisearch’s asynchronous task system, ensuring that developers can maintain high-performance search experiences without manually monitoring task IDs or managing granular API key permissions.

Installation

To integrate this skill into your environment, execute the following command in your terminal or OpenClaw interface: clawhub install openclaw/skills/skills/ivangdavila/meilisearch

Use Cases

• E-commerce Search: Building responsive product catalogs with typo-tolerant search and granular facet filtering.
• Documentation Portals: Powering lightning-fast search across large technical knowledge bases.
• Multi-tenant Applications: Leveraging scoped API keys to isolate search indexes for different users or organizations.
• Content Management: Orchestrating indexing workflows for CMS data where search speed is critical.

Example Prompts

• "Configure my 'products' index with 'category' as a filterable attribute and 'price' as a sortable attribute, then start a full reindex."
• "Create a restricted search-only API key for the 'frontend-ui' that has access only to the 'blog' index and expires in 30 days."
• "What is the status of my current indexing task, and are there any pending settings updates that might be slowing down my document throughput?"

Tips & Limitations

Success with Meilisearch requires understanding its specific architectural constraints. First, never ignore the asynchronous nature of the engine; always verify completion via the task queue. Second, remember that index settings are global—batch your changes to prevent unnecessary full reindexes, which can be computationally expensive.

Performance is heavily tied to RAM because Meilisearch uses memory-mapped files; if your index exceeds your available memory, performance will degrade significantly. When filtering, remember that syntax is not SQL; avoid using 'BETWEEN' and use the 'TO' keyword instead. Furthermore, be aware that typo tolerance is disabled for the first character of a string, and geographical filtering requires strict adherence to the '_geo' field format. Finally, always protect your production instance with a Master Key and utilize scoped API keys for frontend interactions to prevent unauthorized data exposure. Since there is no native clustering, scaling is strictly vertical.