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.
33
0%
Does it follow best practices?
Impact
96%
1.06xAverage 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-service-manager/SKILL.mdQuality
Discovery
0%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 with no substantive content. It fails on all dimensions: it lists no concrete actions, provides no natural trigger terms beyond the skill name repeated, lacks any 'Use when...' guidance, and is indistinguishable from any other Kubernetes or DevOps skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Deploys, scales, and manages Kubernetes services, configures ingress rules, monitors pod health, and troubleshoots service connectivity.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions Kubernetes services, k8s deployments, pod management, kubectl commands, service mesh, or container orchestration.'
Remove the duplicate trigger term 'kubernetes service manager' and replace with varied natural keywords users would actually use (e.g., 'k8s', 'pods', 'deployments', 'kubectl', 'helm', 'cluster management').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states the skill name 'Kubernetes Service Manager' and that it's part of 'DevOps Advanced' but never describes what it actually does (e.g., deploy services, scale pods, manage ingress). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no description of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'kubernetes service manager' repeated twice. These are not natural phrases users would say; users would more likely say 'deploy service', 'k8s', 'pods', 'kubectl', 'scale deployment', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any Kubernetes-related or DevOps skill. Without specific actions or clear scope boundaries, there's high conflict risk with other DevOps or Kubernetes skills. | 1 / 3 |
Total | 4 / 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 template with no substantive content. It repeatedly references 'kubernetes service manager' without ever defining what that means, providing any Kubernetes commands, YAML manifests, kubectl usage, or any actionable guidance whatsoever. It reads as auto-generated boilerplate that would provide zero value to Claude.
Suggestions
Replace the abstract descriptions with concrete Kubernetes commands and YAML examples (e.g., `kubectl create service`, Service manifest templates, port-forwarding, service types like ClusterIP/NodePort/LoadBalancer).
Add a clear workflow with validation steps, such as: create service → verify with `kubectl get svc` → test connectivity → troubleshoot with `kubectl describe svc`.
Remove all meta-sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the task — these waste tokens without adding actionable value.
Include specific examples for common service management tasks: exposing a deployment, configuring ingress, debugging service connectivity issues, with copy-paste ready manifests.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague information about 'kubernetes service manager' without adding substance. | 1 / 3 |
Actionability | There are zero concrete commands, code snippets, configurations, or executable guidance. The skill describes rather than instructs — phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' are promises with no delivery. | 1 / 3 |
Workflow Clarity | No workflow, steps, or sequence of any kind is provided. There are no validation checkpoints, no procedures, and no actionable process for managing Kubernetes services. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no structure beyond boilerplate headings. There are no references to detailed guides, no links to related files, and no meaningful organization of 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
3076d78
- 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.