opensearch-docs
Skill7 starsChanged 15 days agoMITView on GitHub
Official OpenSearch documentation, answered with links to the exact pages. Use for any OpenSearch question, including Query DSL, mappings and ISM, k-NN vector search and ML Commons, the security plugin, OpenSearch Dashboards, Data Prepper, or migration from Elasticsearch.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- caching-strategiesSkill
- database-normalizationSkill
- design-patternsSkill
- object-oriented-programming-paradigmSkill
- aadc-complianceSkill
- app-store-complianceSkill
- ccpa-cpra-complianceSkill
- coppa-complianceSkill
- dpdp-complianceSkill
- eprivacy-complianceSkill
- eu-ai-act-complianceSkill
- eu-dsa-complianceSkill
- gdpr-complianceSkill
- hipaa-hds-complianceSkill
- lgpd-complianceSkill
- pci-dss-complianceSkill
- pipeda-law25-complianceSkill
- pipl-csl-complianceSkill
- psd2-sca-complianceSkill
- uk-gdpr-complianceSkill
- us-state-privacy-complianceSkill
- world-wide-complianceSkill
- aws-cli-docsSkill
- aws-dynamodb-docsSkill
- aws-ecs-docsSkill
- aws-eks-docsSkill
- aws-iam-docsSkill
- aws-lambda-docsSkill
- aws-s3-docsSkill
- bullmq-docsSkill
- cassandra-docsSkill
- django-docsSkill
- docker-docsSkill
- elasticsearch-docsSkill
- expressjs-docsSkill
- fastapi-docsSkill
- fastify-docsSkill
- firebase-docsSkill
- flask-docsSkill
- git-docsSkill
- github-actions-docsSkill
- gitlab-ci-docsSkill
- grafana-docsSkill
- graphql-docsSkill
- helm-docsSkill
- kafka-docsSkill
- kubernetes-docsSkill
- mongodb-docsSkill
- mysql-docsSkill
- nestjs-docsSkill
- nginx-docsSkill
- opentelemetry-docsSkill
- phoenix-docsSkill
- pinecone-docsSkill
- postgresql-16-docsSkill
- postgresql-17-docsSkill
- postgresql-18-docsSkill
- qdrant-docsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Verify plugin and API behavior in the OpenSearch docs.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
OpenSearch Docs
OpenSearch answers drift toward stale Elasticsearch memory and wrong plugin names, so ground each one in the live docs at https://docs.opensearch.org/latest/, not memory, and link the exact page behind every claim.
Route Elastic-licensed Elasticsearch or Kibana features documented only on elastic.co to elasticsearch-docs, MySQL questions to mysql-docs, and PostgreSQL questions to the version's skill (postgresql-16-docs, postgresql-17-docs, or postgresql-18-docs). Amazon OpenSearch Service console operations, Solr, Meilisearch and other search engines belong to their own docs unless the question turns on OpenSearch behavior.
Workflow
- Locate the question in
references/topic-map.md, a selective index of docs entry points. Done when each part of the question maps to a section of the map, or you have noted that none fits. - Search
docs.opensearch.org/latestwith the user's exact terms plus OpenSearch vocabulary such asQuery DSL,k-NN,ISM,security plugin,index template, orML Commons, starting from the map's pages and the Routing rules below. Done when you hold the one page that most directly answers each part. - Read each page down to the relevant section. Done when you have read the passage behind every claim you will make. When a page has moved, been renamed, or stops short, say so and link the nearest authoritative pages.
- Answer with the direct answer first, each docs link beside the claim it supports, and API requests, mappings or security configuration only when the user asks or the page needs them. Mark any conclusion that joins several pages as
Inference:. Done when every claim cites a specific page, not the docs home.
Routing
- Versions: the
latestdocs, unless the user names a specific version. - REST API questions: the API reference, before forum posts or Elasticsearch docs.
- Plugin behavior: the plugin's own docs, before core cluster defaults.
- Data modeling: the mappings and index management docs.
- Query behavior: the Query DSL docs, before syntax recalled from Elasticsearch.
- Vector search: the vector-search docs and k-NN plugin pages.
- Security: the security plugin docs, before generic TLS guidance.
- Dashboards: the OpenSearch Dashboards docs, not Kibana pages.
- Migration: Migration Assistant and the version-specific upgrade guides.
Gotchas
- Verify plugin and API behavior in the OpenSearch docs; it differs from Elasticsearch in places.
- Name features in OpenSearch Dashboards terms; Kibana feature names do not carry over.
- Recommend current index settings; deprecated index types and settings from older Elasticsearch versions are not current guidance.
- ML Commons, k-NN, and neural search are distinct features; check the docs for which one applies.
- Answer authentication and TLS questions through the security plugin.
- Amazon OpenSearch Service may lag or restrict plugins; confirm support there before recommending a plugin for the managed service.
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
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.

