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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill elasticsearch-index-managerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It names the technology but fails to describe any capabilities, use cases, or natural trigger terms. The redundant trigger terms and boilerplate category information add no value for Claude's skill selection process.
Suggestions
Add specific actions the skill performs, e.g., 'Creates, deletes, and manages Elasticsearch indices. Configures mappings, aliases, and index settings. Monitors index health and performs reindexing operations.'
Add a 'Use when...' clause with natural trigger terms like 'Use when working with Elasticsearch indices, ES clusters, index mappings, shards, replicas, or when the user mentions reindexing, index templates, or ILM policies.'
Remove the redundant trigger term and replace with varied natural language terms users would actually say, such as 'elastic search', 'ES index', 'index settings', 'cluster health'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Elasticsearch Index Manager') without describing any concrete actions. There are no verbs or specific 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 naming itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than describing use cases. | 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', 'reindex'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Elasticsearch' is a specific technology that provides some distinctiveness, the lack of detail about what index operations are supported could cause confusion with other Elasticsearch-related skills or general DevOps skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content. It contains only generic placeholder text that describes what a skill should do without providing any concrete guidance for Elasticsearch index management. There are no commands, no code examples, no workflows, and no actionable information whatsoever.
Suggestions
Add concrete Elasticsearch commands for common index operations (create, delete, reindex, alias management) with executable curl or API examples
Include a clear workflow for index lifecycle management with validation steps (e.g., check index health, verify mappings before reindex)
Provide specific code examples for index templates, mappings, and settings configurations
Add references to detailed guides for advanced topics like ILM policies, rollover strategies, and shard optimization
| 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 entire skill describes what it does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. 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 structure pointing to detailed materials. No references to actual implementation guides, API documentation, or examples. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.