kubernetes-deployment-creator
Kubernetes Deployment Creator - Auto-activating skill for DevOps Advanced. Triggers on: kubernetes deployment creator, kubernetes deployment creator Part of the DevOps Advanced skill category.
36
3%
Does it follow best practices?
Impact
100%
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-deployment-creator/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 lacks concrete actions, natural trigger terms, and any explicit guidance on when Claude should select this skill. It would be nearly useless for skill selection among a large set of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Kubernetes Deployment YAML manifests, configures replicas, resource limits, liveness/readiness probes, and environment variables.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a Kubernetes deployment, generate k8s YAML, configure pods, or set up container orchestration.'
Remove the duplicated trigger term ('kubernetes deployment creator' listed twice) and replace with varied natural phrases users would actually say, such as 'k8s deploy', 'deployment manifest', 'kubectl apply', 'container deployment'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Kubernetes Deployment Creator') but does not describe any concrete actions like generating YAML manifests, configuring replicas, setting resource limits, etc. It is essentially just a title repeated with no actionable detail. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'kubernetes deployment creator' repeated twice. It misses natural user phrases like 'k8s deployment', 'deploy to kubernetes', 'create deployment YAML', 'pod spec', 'kubectl', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Kubernetes Deployment' provides some domain specificity that distinguishes it from generic DevOps skills, but the lack of concrete actions or scope means it could overlap with other Kubernetes-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 a placeholder or template with no actual instructional content. It contains only meta-descriptions of what the skill purportedly does without any Kubernetes YAML manifests, kubectl commands, Helm examples, validation steps, or concrete guidance. It fails on every dimension because it describes rather than instructs.
Suggestions
Add concrete, executable Kubernetes deployment YAML examples (e.g., a production-ready Deployment manifest with resource limits, health checks, and rolling update strategy).
Include a clear multi-step workflow: create manifest → validate with `kubectl apply --dry-run=client` → apply → verify with `kubectl rollout status` → rollback instructions if needed.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') and replace with actionable content such as common deployment patterns, security best practices (non-root containers, resource quotas), and Helm chart structure.
Add references to supporting files for advanced topics (e.g., HELM_CHARTS.md, MONITORING.md, RBAC.md) to enable progressive disclosure of complex Kubernetes topics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vague platitudes. There is no actual Kubernetes deployment content—no YAML, no commands, no concrete information whatsoever. | 1 / 3 |
Actionability | There is zero actionable content: no Kubernetes manifests, no kubectl commands, no Helm charts, no code examples, no concrete steps. The entire skill describes what it could do rather than instructing Claude how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequencing, no validation checkpoints. For a skill about creating Kubernetes deployments—which involves multi-step processes with potential for misconfiguration—this is a critical gap. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no references to supporting files, no structured sections with real content, and no bundle files to point to. There is nothing to progressively disclose because there is no substantive 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
13d35b8
- 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.