Name: elastic-cli-usage
Rating: 76.8 (1 reviews)
Author: elastic

elastic-cli-usage

Guides execution of elasticsearch CLI commands via elastic_cli, resolves serverless-specific errors, and routes tasks between CLI and MCP/Kibana API tools. Use when running es or kb commands, debugging elastic CLI argument syntax, hitting 410 serverless errors, or deciding whether to use elastic_cli vs native Kibana tools.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

90%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 highly actionable, token-efficient gotcha catalog with copy-paste command examples and explicit WRONG/CORRECT contrasts. Workflow clarity and progressive disclosure are slightly below the top because the body is a flat reference rather than a sequenced workflow and is just past the size where a separate reference file would help.

Suggestions

Add a short 'Decision flow' at the top (try MCP native tool first → fall back to CLI → apply gotchas) to make the workflow sequence and its verification checkpoint explicit.

Consider moving the longer per-command WRONG/CORRECT blocks (docs, esql, agent-builder) into a references/cli-gotchas.md file, leaving SKILL.md as a concise overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	Lean gotcha list with no concept padding (no 'what is Elasticsearch' filler); assumes Claude's competence and every line is a verified pitfall or corrective example, matching the lean-and-efficient anchor.	5 / 5
Actionability	Copy-paste-ready JSON argv arrays (e.g. ["es","cluster","health","--json"]) and explicit WRONG vs CORRECT blocks for docs/esql/slo cover the common cases fully; not a 4 because guidance is directly executable with specific flags rather than having minor gaps.	5 / 5
Workflow Clarity	A routing table (CLI vs MCP) and a connectivity checkpoint ('Use es cat count --json to verify connectivity on serverless') are present, but the body is a reference of discrete gotchas rather than an explicitly sequenced workflow with feedback loops; not 5 because checkpoints are distributed and implicit, not 3 because verification guidance does exist.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is appropriately inline with clear section headers (Shorthands, Prefer MCP, Gotchas) and easy navigation; not 5 because at ~95 lines (above the 50-line simple-skill threshold) the Gotchas block bundles many distinct pitfalls that could warrant a one-level-deep reference file.	4 / 5
	Total	18 / 20 Passed

Description

100%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 strong, tightly-scoped description that names concrete capabilities and provides explicit, natural trigger phrases with good synonym coverage. It clearly answers both what the skill does and when to use it with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Guides execution of elasticsearch CLI commands via elastic_cli', 'resolves serverless-specific errors', 'routes tasks between CLI and MCP/Kibana API tools' — matching the comprehensive-coverage anchor; not a 4 because three distinct specific actions are named rather than having minor gaps.	5 / 5
Completeness	Explicitly answers both what ('Guides execution... resolves... routes...') and when ('Use when running es or kb commands, debugging..., hitting 410 serverless errors, or deciding whether to use elastic_cli vs native Kibana tools') with concrete trigger phrases, exactly matching the score-5 anchor.	5 / 5
Trigger Term Quality	Natural triggers a user would actually say ('running es or kb commands', 'debugging elastic CLI argument syntax', 'hitting 410 serverless errors') plus synonyms (es/kb, elastic CLI, elastic_cli, Kibana, MCP); comprehensive coverage, not a 4 since synonyms and domain-specific error terms are well represented.	5 / 5
Distinctiveness Conflict Risk	Clear niche (elasticsearch CLI on serverless) with highly specific triggers (410 serverless errors, elastic_cli vs Kibana) giving minimal conflict risk; not a 4 because the triggers are tightly scoped to this one tool/stack.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: elastic/elastic-ramen
Path: packages/opencode/src/elastic/skills/elastic-cli-usage/SKILL.md
Commit: 28588e8

Reviewed: 11 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.