Name: elastic
Rating: 52.8 (1 reviews)
Author: membranedev

elastic

Elastic integration. Manage data, records, and automate workflows. Use when the user wants to interact with Elastic data.

Quality

59%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/elastic/SKILL.md

Quality

Content

56%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.

The body delivers executable, well-flagged Membrane CLI commands and a reasonably validated connection workflow. Its weaknesses are a large padding-heavy entity list and the absence of any progressive-disclosure structure or external references.

Suggestions

Move the ~150-line entity enumeration into a separate reference file (e.g. ENTITIES.md) and link to it, keeping SKILL.md as a lean overview.

Fix the step numbering (add a '1a' or relabel '1b') and explicitly label 'Step 2' so the connection-to-action workflow is unambiguous.

Trim the introductory paragraph explaining what Elastic is, since Claude already knows the product; lead directly with the working commands.

Dimension	Reasoning	Score
Conciseness	The ~150-line enumerated list of entity types and the opening paragraph explaining what Elastic is add substantial padding Claude does not need, even though the CLI command examples themselves are tight.	2 / 5
Actionability	Provides concrete, copy-paste-ready `membrane` commands with real flags (--json, --wait, --connectionId) and a clear proxy-options table; minor gaps such as the placeholder QUERY/CONNECTION_ID tokens are obvious.	4 / 5
Workflow Clarity	The connection flow is sequenced with state-based validation checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop, though the step numbering is broken ('1b' with no '1a') and 'Step 2' is referenced but unlabeled.	4 / 5
Progressive Disclosure	No bundle files exist and there are no references to separate materials; the large entity-type enumeration is inlined monotonically where a structured or externalized reference would aid navigation.	3 / 5
	Total	13 / 20 Passed

Description

62%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.

The description answers both what and when with an explicit Elastic trigger, giving it solid completeness and distinctiveness. Specificity and trigger-term quality are mid-range because the action verbs are generic and several natural synonyms (search, logs, Kibana, index) are absent.

Suggestions

Replace generic verbs ('Manage', 'automate workflows') with concrete Elastic actions such as 'search and query indices, manage data streams, create index templates, and run transforms'.

Add natural trigger terms users actually say, e.g. 'Use when the user wants to search Elastic, query logs, manage Kibana dashboards, or work with Elasticsearch indices.'

Dimension	Reasoning	Score
Specificity	Names the Elastic domain and a few actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete operations like indexing, searching, or snapshotting.	3 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Elastic data'); the 'when' is present and explicit but fairly generic.	4 / 5
Trigger Term Quality	Includes 'Elastic', 'data', 'records', 'workflows', and 'interact with Elastic data', but misses common synonyms users would say (e.g. 'search', 'logs', 'Kibana', 'index documents').	3 / 5
Distinctiveness Conflict Risk	The 'Elastic integration' framing with an explicit Elastic-data trigger carves a clear niche with minimal overlap risk against other skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/elastic/SKILL.md
Commit: f484c82

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