amazon-opensearch-service

Amazon OpenSearch Service and Serverless across five capabilities — migration (Solr/ES/self-managed OpenSearch into AOS/AOSS, schema/query translation, sizing, cutover); provisioning (domain + AOSS lifecycle, upgrades, storage tiers, FGAC, monitoring); search (vector / semantic / hybrid / RAG with Bedrock connectors); log-analytics (PPL, OSI ingestion, anomaly detection, OpenSearch Dashboards, Splunk/Datadog alternatives); trace-analytics (OTel spans, service maps, Data Prepper). Triggers on OpenSearch, AOS, AOSS, Elasticsearch, ELK, Solr, Lucene, vector / k-NN / semantic / hybrid / neural search, RAG, ELSER, log analytics, observability, Kibana, OSI, OCU, PPL, trace analytics, BM25, eDisMax, schema.xml, ILM, ISM, FAISS, HNSW, Migration Assistant for Amazon OpenSearch Service, Historical Data Migration, Live Traffic Migration, UltraWarm, OR1, Splunk/Datadog alternative, moving off Solr. Picks ONE capability per ask, names instance class + count + shard math, ships query DSL examples.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplary routing overview: concise, assumes competence, provides concrete rule templates, sequences capability detection as an explicit first step, and cleanly delegates detail to verified one-level-deep references. It adds only what Claude would not already know about this product's five-capability structure.

Dimension	Reasoning	Score
Conciseness	The ~50-line body is a lean routing overview that assumes Claude's competence — it never explains what OpenSearch/k-NN/ISM are, and every line (Step 0 routing, universal rules, cross-cutting refs, 'does NOT do') earns its place.	3 / 3
Actionability	Although this instruction-only body delegates executable DSL/sizing to references, it gives concrete copy-paste templates — the exact report-header format, a specific banned-word list, and a literal cross-capability handoff sentence — which is actionable guidance per the instruction-only carve-out.	3 / 3
Workflow Clarity	Step 0 is explicitly flagged 'first thing you do', sequences detect-capability → state-it → load-entry-ref, and hard constraints ('Route every cost question to calculator.aws and stop') act as validation gates; cross-capability handoff is specified.	3 / 3
Progressive Disclosure	A clear overview with a capability→entry-point routing table and one-level-deep cross-cutting references, each given a one-line description; all 12 referenced files exist, so navigation is clean and shallow.	3 / 3
	Total	12 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A dense, specific, third-person description that concretely enumerates five capabilities, their sub-actions, and an explicit trigger list, clearly answering both what the skill does and when to use it. It is comprehensive without resorting to vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions per capability — 'schema/query translation, sizing, cutover', 'domain + AOSS lifecycle, upgrades, storage tiers, FGAC, monitoring', 'vector / semantic / hybrid / RAG with Bedrock connectors' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers what ('Amazon OpenSearch Service and Serverless across five capabilities ...') and when ('Triggers on ...'), with an explicit trigger clause rather than an implied one, satisfying the top anchor.	3 / 3
Trigger Term Quality	The explicit 'Triggers on OpenSearch, AOS, AOSS, Elasticsearch, ELK, Solr, Lucene, vector / k-NN / semantic / hybrid / neural search, RAG, ELSER, log analytics, observability, Kibana, OSI, OCU, PPL, trace analytics, BM25, eDisMax, schema.xml, ILM, ISM, FAISS, HNSW ... Splunk/Datadog alternative, moving off Solr' gives broad coverage of natural terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and product-specific (Amazon OpenSearch Service/Serverless) with highly distinctive trigger terms (ELSER, OCU, eDisMax, schema.xml, Migration Assistant), making conflict with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: aws/agent-toolkit-for-aws
Path: plugins/aws-data-analytics/skills/amazon-opensearch-service/SKILL.md
Commit: 222ce56

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.