elasticsearch-index-manager
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 extremely weak, functioning essentially as a label rather than a useful skill description. It provides no concrete actions, no meaningful trigger terms beyond the skill name itself, and no guidance on when Claude should select this skill. The repeated trigger term and boilerplate category mention add no value.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates, deletes, and manages Elasticsearch indices, configures mappings and settings, manages aliases, and monitors index health.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Elasticsearch indices, index mappings, shards, replicas, reindexing, aliases, or index lifecycle management.'
Remove the duplicate trigger term and expand with natural variations users might say, such as 'ES index', 'Elastic index', 'index template', 'ILM policy', etc.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Elasticsearch Index Manager') without describing any concrete actions. There are no specific capabilities listed such as creating indices, managing mappings, configuring shards, or monitoring index health. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause with meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'elasticsearch index manager' repeated twice. It lacks natural user keywords like 'index', 'mapping', 'shard', 'reindex', 'alias', 'cluster health', or 'Elasticsearch' in broader contexts. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Elasticsearch' provides some domain specificity that distinguishes it from generic DevOps skills, but the lack of concrete actions means it could overlap with any other Elasticsearch-related skill. | 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 substantive content. It contains only generic boilerplate descriptions that could apply to any topic, with no Elasticsearch-specific commands, configurations, code examples, or workflows. It provides zero value to Claude in performing Elasticsearch index management tasks.
Suggestions
Add concrete, executable examples for common Elasticsearch index operations (e.g., creating indices with mappings, reindexing, managing aliases) using curl commands or Python elasticsearch-py client code.
Define a clear multi-step workflow for index lifecycle management (create → configure → validate → monitor → rotate/delete) with explicit validation checkpoints such as checking cluster health and index status.
Include specific configuration examples for ILM (Index Lifecycle Management) policies, index templates, and shard allocation settings as production-ready JSON/YAML.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content covering common patterns like rolling indices, snapshot/restore, and reindex strategies.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific Elasticsearch index management details, and wastes tokens on generic placeholder text like 'Provides step-by-step guidance' without any actual guidance. | 1 / 3 |
Actionability | There is zero actionable content—no commands, no code, no API calls, no configuration examples, no concrete steps for managing Elasticsearch indices. Every section is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. Elasticsearch index management involves potentially destructive operations (reindexing, deleting indices) that demand explicit workflows with validation, yet none are provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to disclose progressively. | 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 | |
- Commit
13d35b8
- 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.