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
Quality
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 placeholder that provides almost no useful information for skill selection. It names the technology (Elasticsearch) but fails to describe any concrete capabilities, use cases, or natural trigger terms. The redundant trigger terms and boilerplate category information add no value.
Suggestions
Add specific actions the skill performs, e.g., 'Creates, deletes, and reindexes Elasticsearch indices. Manages index mappings, settings, aliases, and lifecycle policies.'
Add a proper 'Use when...' clause with natural trigger terms: 'Use when working with Elasticsearch indices, ES cluster management, index mappings, shards, replicas, or index lifecycle management.'
Include common variations users might say: 'elastic search', 'ES indices', 'index templates', 'reindex', 'cluster health', '.es files'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Elasticsearch Index Manager') without describing any concrete actions. There are no verbs or capabilities listed - no mention of what operations can be performed on indices. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' line is not a proper 'Use when...' clause and only repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('elasticsearch index manager' listed twice) and overly specific. Missing natural variations users would say like 'ES indices', 'elastic search', 'index management', 'shards', 'mappings', or common operations. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Elasticsearch' provides some specificity that distinguishes it from generic database or search skills, but without describing actual capabilities, it could still conflict with other Elasticsearch-related skills. | 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 essentially an empty placeholder with no substantive content. It describes what an Elasticsearch index manager skill should do but provides absolutely no actionable guidance, code examples, or concrete instructions for any index management tasks. The entire content could be replaced with actual Elasticsearch commands and patterns.
Suggestions
Add concrete, executable examples for common index operations (create index, update mappings, reindex, delete indices) with actual Elasticsearch API calls or CLI commands
Define clear workflows for index lifecycle management including validation steps (e.g., check index health before deletion, verify mappings after creation)
Include specific configuration examples for index settings, mappings, and aliases in JSON format
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific Elasticsearch operations. The skill describes what it claims to do but provides no actual instructions for managing Elasticsearch indices. | 1 / 3 |
Workflow Clarity | No workflow is defined whatsoever. There are no steps, no sequences, and no validation checkpoints for any Elasticsearch index management operations. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples, and no structured navigation to actual implementation guidance. | 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
994edc4
- 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.