kubernetes-service-manager
Kubernetes Service Manager - Auto-activating skill for DevOps Advanced. Triggers on: kubernetes service manager, kubernetes service manager Part of the DevOps Advanced skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill kubernetes-service-managerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, functioning more as a label than a useful skill description. It provides no concrete actions, no usage triggers, and relies entirely on the skill name to convey meaning. Claude would struggle to know when to select this skill over other DevOps or Kubernetes-related options.
Suggestions
Add specific actions the skill performs, e.g., 'Creates, scales, and manages Kubernetes services, deployments, and pods. Handles service discovery, load balancing configuration, and rolling updates.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions k8s, kubectl, pods, deployments, services, clusters, or needs to manage containerized applications.'
Remove the redundant trigger term and expand to include common variations and abbreviations users actually type (k8s, kube, container orchestration).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Kubernetes Service Manager') without describing any concrete actions. There are no verbs or specific capabilities listed - no mention of what operations it performs on Kubernetes services. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Only states it's part of a category. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('kubernetes service manager' listed twice) and overly specific. Missing natural variations users would say like 'k8s', 'pods', 'deployments', 'kubectl', 'cluster', or common service management tasks. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Kubernetes Service Manager' is somewhat specific to Kubernetes, the lack of detail about what aspects of service management it handles could cause overlap with other Kubernetes-related skills or general DevOps skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no substantive content. It describes what a Kubernetes service manager skill would do without providing any actual guidance, commands, YAML examples, or workflows. The content fails all dimensions by being entirely abstract and non-actionable.
Suggestions
Add concrete kubectl commands and YAML manifests for common service operations (create, expose, scale, update services)
Include a clear workflow for service lifecycle management with validation steps (e.g., verify service is running, check endpoints, test connectivity)
Provide specific examples showing different service types (ClusterIP, NodePort, LoadBalancer) with copy-paste ready configurations
Remove generic boilerplate sections ('When to Use', 'Example Triggers') and replace with actionable technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actionable information. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The entire skill describes what it does abstractly without any executable examples, kubectl commands, YAML manifests, or specific Kubernetes service management instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, sequences, or processes for managing Kubernetes services. The 'Capabilities' section mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no references to detailed materials, no links to examples, and no structured navigation to deeper content about Kubernetes service management. | 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.