agentleFS
Sign inStart free
ElasticKnown publisherelastic/agent-skills/plugins/elasticsearch/skills/elasticsearch-onboarding/SKILL.md

elasticsearch-onboarding

Skill583 starsChanged 58 days agoApache-2.0View on GitHub

Help developers new to Elasticsearch get from zero to a working search experience. Guide them through understanding their intent, mapping their data, and building a search experience with best practices baked in. Use this when the user shows intent to build search-related functionality, asks about Elasticsearch-related concepts for their use case, or expresses the need for help getting started with Elasticsearch.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask one question at a time, then wait.

    line 46
  2. Distinctive:

    Only generate code once the user confirms the approach and the mapping.

    line 47
  3. Distinctive:

    Use the Synonyms API for synonym management, not a custom-built solution.

    line 48
  4. Very specific:

    Always use a versioned index name + alias (e.g.

    line 49
  5. Distinctive:

    Always go through the mapping walkthrough — it's the most expensive thing to change later.

    line 51
  6. Distinctive:

    Ask what programming language the user wants to use, don't assume.

    line 52
  7. Distinctive:

    Avoid generating code with deprecated APIs.

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

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.
  • 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free