Elasticsearch Index Manager - Auto-activating skill for DevOps Advanced. Triggers on: elasticsearch index manager, elasticsearch index manager Part of the DevOps Advanced skill category.
36
3%
Does it follow best practices?
Impact
99%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/02-devops-advanced/elasticsearch-index-manager/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a title and category label with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would use, and provides no guidance on when Claude should select this skill. It would be nearly useless for skill selection in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates, configures, and deletes Elasticsearch indices, manages index mappings and settings, handles index lifecycle policies, and performs reindexing operations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions Elasticsearch indices, index mappings, shards, replicas, index templates, ILM policies, reindexing, or ES cluster index management.'
Remove the duplicate trigger term ('elasticsearch index manager' is listed twice) and replace with varied, natural keywords users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'Elasticsearch Index Manager' but provides no concrete actions—it doesn't describe what the skill actually does (e.g., create indices, manage mappings, configure shards, delete indices). It's essentially just a title repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title and completely lacks a 'when should Claude use it' clause. There is no explicit trigger guidance or use-case description. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'elasticsearch index manager' repeated twice. It misses natural user terms like 'elasticsearch indices', 'index settings', 'mappings', 'shards', 'reindex', 'index lifecycle', or 'ES cluster'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Elasticsearch Index Manager' does narrow the domain somewhat—it's unlikely to conflict with unrelated skills. However, without specific actions described, it could overlap with other Elasticsearch-related skills if they exist. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder with no actual technical content. It contains only auto-generated boilerplate that describes what the skill would do without providing any Elasticsearch index management guidance, commands, configurations, or examples. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples for common Elasticsearch index operations (e.g., creating indices with mappings, configuring ILM policies, reindexing) using curl commands or API calls.
Define a clear multi-step workflow for index lifecycle management with validation checkpoints (e.g., check cluster health before/after operations, verify alias assignments).
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content like index template configurations, rollover policies, and shard sizing guidance.
Add references to detailed sub-topics (e.g., ILM_POLICIES.md, INDEX_TEMPLATES.md, TROUBLESHOOTING.md) to provide progressive disclosure for advanced scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague information about 'elasticsearch index manager' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no commands, no code, no configuration examples, no API calls, no index management patterns. The skill describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The phrase 'step-by-step guidance' is promised but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to configuration examples, API references, or related documentation. There is no meaningful structure beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
c8a915c
Table of Contents
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.