CtrlK
BlogDocsLog inGet started
Tessl Logo

elasticsearch-esql

Use this skill when writing or debugging ES|QL queries for Elasticsearch. Activate when the user asks to query logs, metrics, traces, or any Elasticsearch data using ES|QL syntax.

86

1.20x
Quality

80%

Does it follow best practices?

Impact

94%

1.20x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

A compact, highly actionable ES|QL reference with concrete executable examples and useful guardrail tips. Its main limitations are minor syntax/pattern redundancy, an unarticulated query-then-validate workflow, and a monolithic structure that could split the function catalogs into a reference file.

Suggestions

Collapse the standalone Syntax block into the Common Patterns or trim it to remove redundancy with the worked examples.

Add a short "Authoring workflow" sequence (e.g., start with LIMIT 10 and KEEP to inspect fields, then refine WHERE/STATS) with a verify-then-expand checkpoint.

Move the Type Functions and Aggregation Functions catalogs into a references/ file (e.g., FUNCTIONS.md) linked from the body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly lean reference material with compact function lists and code, but the standalone Syntax block partially overlaps the Common Patterns that follow; not a 5 due to that minor redundancy and one definitional line.

4 / 5

Actionability

Copy-paste-ready executable ES|QL queries plus a concrete CLI command ("elastic es query '...'") cover the common cases (time filter, count-by, percentiles, bucketing, multi-field filter); fully actionable.

5 / 5

Workflow Clarity

The run action is concrete and the Tips provide lightweight guardrails (time range, LIMIT, KEEP), but there is no explicit sequenced workflow or validation checkpoint; not a 5 because no feedback loop is articulated.

4 / 5

Progressive Disclosure

Well-organized into clear sections with no nested references and appropriately compact for a single-file skill; not a 5 because it exceeds ~50 lines as a monolithic reference with no one-level-deep split for the function catalogs.

4 / 5

Total

17

/

20

Passed

Description

78%Weight 40%Scale 1-5

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 clear, well-triggered description that names a specific niche and concrete trigger terms an observability user would naturally say. The only real gap is limited action breadth (writing/debugging only) and a few missing synonyms.

Suggestions

Add one or two more concrete actions (e.g., "optimizing" or "translating DSL to ES|QL") to lift specificity beyond the 1-2 action anchor.

Include common synonyms such as Kibana, ELK, or "Elasticsearch Query Language" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (ES|QL/Elasticsearch) and two concrete actions ("writing or debugging ES|QL queries"), matching the 1-2 concrete actions anchor; not a 4 because no broader action coverage is listed.

3 / 5

Completeness

Explicitly states the what ("writing or debugging ES|QL queries for Elasticsearch") and an explicit when with concrete trigger phrases ("Activate when the user asks to query logs, metrics, traces..."), satisfying both halves clearly.

5 / 5

Trigger Term Quality

"logs, metrics, traces, or any Elasticsearch data using ES|QL syntax" gives good natural keyword coverage an observability user would say; not a 5 because synonyms like Kibana/ELK/search are absent.

4 / 5

Distinctiveness Conflict Risk

ES|QL is a specific niche with distinct triggers, giving minimal conflict risk; not a 5 because of minor potential overlap with a general Elasticsearch/Kibana querying skill.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
elastic/elastic-ramen
Reviewed

Table of Contents

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.