CtrlK
BlogDocsLog inGet started
Tessl Logo

elasticsearch

Elasticsearch expert for queries, mappings, aggregations, index management, and cluster operations

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./crates/openfang-skills/bundled/elasticsearch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A well-organized, token-efficient reference that delivers specific Elasticsearch guidance, but it lacks complete executable examples and validation checkpoints for its destructive operations.

Suggestions

Add at least one complete, copy-paste-ready example (e.g. a full bool query JSON or a complete _reindex request body) to lift actionability.

Insert a validation/verification checkpoint for destructive operations — e.g. after _reindex, verify document counts match before swapping aliases.

Consider a short sequenced workflow for reindex-with-alias-swap (create new index -> reindex -> verify -> swap alias -> delete old) with explicit verify steps.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — terse bullets like 'Use index aliases for zero-downtime reindexing' and 'Size shards between 10-50 GB' add domain-specific knowledge without padding or explaining basics Claude already knows.

3 / 3

Actionability

It names concrete APIs ('POST _reindex', 'GET _cluster/allocation/explain') and specific clauses/types, but provides no complete executable code blocks (no full query JSON or reindex request body), so it is not copy-paste ready as the score-3 anchor requires.

2 / 3

Workflow Clarity

The content is organized into clear sections and each technique is individually clear, but destructive/batch operations like reindexing and ILM delete phases are mentioned without validation checkpoints, which caps workflow clarity at 2 per the guidelines.

2 / 3

Progressive Disclosure

This is a single ~35-line SKILL.md with no need for external references, and its four well-organized sections (Key Principles, Techniques, Common Patterns, Pitfalls) meet the guideline allowing a 3 for short skills with good organization and no bundle files.

3 / 3

Total

10

/

12

Passed

Description

82%

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 concise, specific description with a clear niche and natural trigger term, but it omits an explicit 'Use when...' clause so it does not fully answer when Claude should invoke the skill.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user works with Elasticsearch, Elastic stack, or needs help with queries, mappings, aggregations, or cluster operations.'

Add a couple of common user variations (e.g. 'Elastic search', 'Kibana queries', 'log analytics') to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'queries, mappings, aggregations, index management, and cluster operations' — matching the score-3 anchor that rewards listing several specific actions rather than vague language.

3 / 3

Completeness

It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

'Elasticsearch' is the primary natural trigger a user would say, supplemented by common ES terms ('queries, mappings, aggregations') that users naturally invoke, giving good coverage of natural keywords.

3 / 3

Distinctiveness Conflict Risk

'Elasticsearch expert' names a distinct, well-known niche with unique triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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
RightNow-AI/openfang
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.