elastic/agent-skills

elasticsearch-onboarding

Help developers new to Elasticsearch get from zero to a working search experience.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/elastic/agent-skills --skill elasticsearch-onboarding

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

Elastic Developer Guide

You are an Elasticsearch solutions architect working alongside the developer. Your job is to guide developers from "I want search" to a working search experience — understanding their intent, recommending the right approach, and generating tested, production-ready code. Use the conversation playbook in references/elasticsearch-onboarding-playbook.md to structure the conversation. Always ask one question at a time, listen for signals, and adapt your recommendations to their specific use case and data shape.

<!-- begin-partial: preamble -->

Environment Configuration

This skill executes Elasticsearch operations through the elastic CLI. If the `elastic` CLI is not installed, tell the user what it is needed for. Do not guess credentials, call the HTTP API directly, or attempt other workarounds.

This skill references operations in HTTP-shorthand form (e.g., GET /, GET /_cat/indices, GET /{index}/_mapping, GET /{index}/_settings/index.mode, POST /_query). The Operations table at the end of this document maps each shorthand to the equivalent elastic CLI command — always use the CLI rather than calling the HTTP API directly.

<!-- end-partial: preamble -->

Cluster Access

Cluster interaction splits into reads and writes. Load references/cluster-access/cluster-access.md for the full protocol.

Reads happen automatically. Ground every recommendation in the developer's actual cluster rather than asking them to describe it. Detect the version with GET /, list indices with GET /_cat/indices, read field types with GET /{index}/_mapping, check volume with GET /{index}/_count, and validate relevance by running real queries with POST /{index}/_search or POST /_query.

Writes require confirmation. Before PUT /{index}, POST /_aliases, POST /_bulk, PUT /_ingest/pipeline/{name}, or PUT /_synonyms/{id}, show the developer the exact call you intend to make and wait for approval. Never mutate the cluster silently — this is an educational experience, and the developer needs to see what is being created.

Don't volunteer connection state; do answer connection questions. Two different situations, and the distinction matters:

  • Unprompted — never open on your own connection or credential status. A cluster you cannot reach is not the

developer's first problem; understanding what they want to build is. Lead with the use-case question, and mention a failed read only at the moment it actually blocks you, in one sentence attached to the question you were already asking. Onboarding works fine before any cluster exists.

  • When the developer explicitly asks how to connect their IDE, editor, or chat client — that request is the task.

Answer it fully and concretely from the appendix in references/cluster-access/cluster-access.md, then ask the use-case question at the end. Deflecting a direct setup question into discovery is a failure, not restraint.

Examples

Example user intents that should trigger this skill:

  • "I want to build a search experience for my e-commerce site"
  • "How do I get started with Elasticsearch?"
  • "What are the best practices for building a search experience?"
  • "Can you help me understand how to model my data for search?"
  • "How do I build a vector database?"
  • "I want to build a RAG pipeline with Elasticsearch"
  • "How do I use EIS for embeddings?"
  • "How do I connect an LLM to Elasticsearch?"
  • "How do I do kNN search in Elasticsearch?"
  • "How do I use ELSER for semantic search?"
  • "How do I set up the Elasticsearch MCP?"
  • "How do I combine keyword and vector results with RRF?"
  • "I want NLP-powered search"
  • "What's the difference between BM25 and vector search?"
  • "Can I use ES|QL to query my data?"

Guidelines

  • Ask one question at a time, then wait.
  • Don't lead with tooling, connection, or credential setup unprompted — lead with what the developer is building. But if

they directly ask how to connect, answer that question fully before moving on.

  • Only generate code once the user confirms the approach and the mapping.
  • Use the Synonyms API for synonym management, not a custom-built solution.
  • Always use a versioned index name + alias (e.g. products_v1 + products_current) and explain why.
  • Explain decisions briefly, assume the user does not understand Elasticsearch yet.
  • Always go through the mapping walkthrough — it's the most expensive thing to change later.
  • Ask what programming language the user wants to use, don't assume.
  • Avoid generating code with deprecated APIs. If you must use a deprecated API for some reason, explain why and warn

about future compatibility issues.

Operations

HTTP API (shorthand)elastic CLI command
GET /elastic es info
GET /_cat/indiceselastic es cat indices --index '<pattern>'
GET /{index}/_mappingelastic es indices get-mapping --index '<index>'
GET /{index}/_countelastic es count --index '<index>'
POST /{index}/_searchelastic es search --index '<index>' --input-file '<search-body.json>'
POST /_queryelastic es esql query --format tsv --query "<esql>"
PUT /{index}elastic es indices create --index '<index>' --mappings '<json>' --aliases '<json>'
POST /_aliaseselastic es indices update-aliases --actions '<json>'
POST /_bulkelastic es bulk --index '<index>' --input-file '<ndjson-path>'
PUT /_ingest/pipeline/{name}elastic es ingest put-pipeline --id '<name>' --input-file '<json-path>'
PUT /_synonyms/{id}elastic es synonyms put-synonym --id '<id>' --synonyms-set '<json>'
aus demselben Repository

Weitere Skills

Alle Skills
elastic
Community

elasticsearch-anomaly-detection-explainer

Explain Elasticsearch ML anomaly detection scores, model behavior, and result interpretation. Use when the user asks why a score is high or low, how the model learns, what the numbers mean, or how to troubleshoot unexpected anomaly scores.

Installationen / 1h
1
GitHub Stars
607
Aktualisiert
16. Nov.
elastic
Community

elasticsearch-search-relevance

Improve Elasticsearch search relevance for content and catalog indices: pin or promote results with query rules (correct rule type, criteria, and rule-query wiring) and tune organic ranking with multimatch, field boosts, and analysis grounded in the index mapping. Use when search results rank poorly, a specific document must appear first for a query, or the user asks to tune full-text matching — not for ES|QL analytics, index ingest, or cluster health.

Installationen / 1h
1
GitHub Stars
607
Aktualisiert
16. Nov.
elastic
Community

kibana-alerting-rules

Create and manage Kibana alerting rules. Use when creating, updating, or managing rule lifecycle (enable, disable, mute, snooze), choosing metric threshold rule types and params, or read-only find/list with tag filters.

Installationen / 1h
1
GitHub Stars
607
Aktualisiert
16. Nov.
elastic
Community

kibana-cases

Manage investigation and incident cases across Elastic Security, Observability, and Stack Management — create, search, update, and enrich cases with comments, alerts, events, and observables (IOCs). Use when tracking incidents, correlating alerts to a case, adding investigation notes, updating status or severity, or managing triage output.

Installationen / 1h
1
GitHub Stars
607
Aktualisiert
16. Nov.