Create, configure, and manage Elasticsearch indices — mappings, settings, templates, data streams, and lifecycle policies.
Help users design and manage Elasticsearch indices for optimal search performance.
Use when the user asks to:
Also activates on keywords: "mappings", "index template", "ILM", "data stream", "reindex", "analyzer", "tokenizer"
Do NOT use when:
esql_query or elasticsearch_api directly)vector-search rule, but this skill handles the index creation part)get_cluster_context — Cluster orientation, version, and existing indiceselasticsearch_api — Index CRUD, mappings, settings, templates, ILMesql_query — Validate data after indexingdiscover_data — Discover existing indices and data patternsget_data_summary — Understand existing data for migration or redesignCall get_cluster_context for cluster version and capabilities.
Ask about:
| Use Case | Strategy |
|---|---|
| Time-series data (logs, metrics, events) | Data stream with ILM |
| Application/reference data | Regular index |
| Search content with evolving schema | Index template + aliases |
| Multi-tenant data | Index per tenant or filtered aliases |
Use elasticsearch_api to create the index with optimized mappings:
keyword for exact match / aggregations, text for full-text searchdate with appropriate format for timestampssemantic_text for vector/semantic search fieldsindex: false on fields that don't need searchingobject vs nested deliberately (nested is expensive)Create ILM policy via elasticsearch_api:
elasticsearch_apiesql_query to verify mappings behave as expected_mapping endpoint to confirm dynamic fields mapped correctlyES_URL and ES_API_KEY (or ES_USERNAME/ES_PASSWORD) configuredcluster-onboarding skill if starting from scratch)Interactive Dashboard: When using Claude Desktop or other ext-apps hosts,
manage_indicesrenders an interactive index management dashboard with a visual mapping tree, shard allocation view, and bulk index operations. In Cursor/CLI, it returns markdown.
cluster-onboarding — If the user doesn't have a cluster yeto11y-full-setup — If the index is for O11Y data, use the dedicated setupagent-builder-skill-builder — Build custom tools that query the new index