kubernetes-configmap-handler
Kubernetes Configmap Handler - Auto-activating skill for DevOps Advanced. Triggers on: kubernetes configmap handler, kubernetes configmap handler Part of the DevOps Advanced skill category.
35
3%
Does it follow best practices?
Impact
91%
1.00xAverage 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/kubernetes-configmap-handler/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—it is essentially a title and category label with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would employ, and provides no guidance on when Claude should select this skill. It reads like auto-generated boilerplate rather than a useful skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates, updates, validates, and troubleshoots Kubernetes ConfigMaps from files, literals, or environment variables.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions configmap, k8s config, kubectl create configmap, ConfigMap YAML, or mounting configuration data in Kubernetes pods.'
Remove the duplicated trigger term and replace with diverse natural language variations users would actually say, such as 'configmap', 'k8s configuration', 'config map', 'kubectl configmap', '.yaml config'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names the skill ('Kubernetes Configmap Handler') and states it's part of 'DevOps Advanced' but never describes what it actually does—no verbs like 'create', 'update', 'manage', 'validate', etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'kubernetes configmap handler' repeated twice. These are not natural phrases a user would say; users would more likely say 'configmap', 'k8s config', 'create configmap', 'edit configmap', 'kubectl configmap', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Kubernetes Configmap' does narrow the domain somewhat, distinguishing it from generic document or code skills. However, without specific actions described, it could overlap with any general Kubernetes management 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 entirely boilerplate meta-description with no actual content. It contains no executable code, no kubectl commands, no ConfigMap YAML examples, no best practices, and no workflows. It fails on every dimension because it describes what a skill would do rather than actually teaching anything.
Suggestions
Add concrete, executable examples such as `kubectl create configmap` commands and YAML ConfigMap manifests with realistic key-value pairs and volume mount examples.
Include a clear workflow for common ConfigMap operations: creating, updating, mounting as volumes/env vars, and validating that pods pick up changes (with rollout restart steps).
Add specific best practices like immutable ConfigMaps, size limits, naming conventions, and common pitfalls (e.g., pods not auto-reloading on ConfigMap changes).
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) and replace with actionable content—code snippets, YAML examples, and kubectl commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual knowledge or instructions that Claude doesn't already know. Every section is boilerplate padding. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific ConfigMap examples, no YAML snippets, no kubectl commands. The content only describes what it could do rather than actually instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to related files, and no structured navigation to deeper content. | 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
c8a915c
- 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.