creating-kubernetes-deployments
Deploy applications to Kubernetes with production-ready manifests. Supports Deployments, Services, Ingress, HPA, ConfigMaps, Secrets, StatefulSets, and NetworkPolicies. Includes health checks, resource limits, auto-scaling, and TLS termination. Use when working with creating kubernetes deployments. Trigger with 'creating', 'kubernetes', 'deployments'.
83
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
85%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 is a strong description that clearly communicates what the skill does (generate production-ready Kubernetes manifests across many resource types) and when to use it. The main weakness is the trigger term coverage, which is too narrow and misses common user terms like 'k8s', 'pods', 'containers', 'manifest', and 'YAML'. The explicit 'Trigger with' clause feels mechanical and doesn't capture the breadth of how users naturally request Kubernetes help.
Suggestions
Expand trigger terms to include common variations users would naturally say: 'k8s', 'pods', 'containers', 'manifest', 'YAML', 'kubectl', 'cluster deployment', 'deploy to cluster'.
Rephrase the 'Trigger with' clause to be more natural, e.g., 'Use when the user asks about deploying to Kubernetes, creating k8s manifests, configuring pods, services, or any Kubernetes resource definitions.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and resource types: Deployments, Services, Ingress, HPA, ConfigMaps, Secrets, StatefulSets, NetworkPolicies, health checks, resource limits, auto-scaling, and TLS termination. | 3 / 3 |
Completeness | Clearly answers both 'what' (deploy applications with production-ready manifests, supporting various K8s resources) and 'when' (explicit 'Use when working with creating kubernetes deployments' clause with trigger terms). | 3 / 3 |
Trigger Term Quality | Includes 'kubernetes' and 'deployments' as trigger terms, but misses common natural variations users would say like 'k8s', 'deploy to cluster', 'helm', 'pods', 'containers', 'manifest', 'YAML', or 'kubectl'. The explicit trigger list ('creating', 'kubernetes', 'deployments') is narrow and overly prescriptive. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Kubernetes deployment manifests with specific resource types listed, making it highly distinguishable from general DevOps, Docker, or cloud deployment skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, highly actionable Kubernetes deployment skill with excellent executable examples and a clear workflow including validation steps. Its main weakness is length and organization—the document includes substantial inline content that could be referenced externally, and has structural issues like the Overview appearing at the bottom. Some redundancy (repeated port comments, obvious prerequisites) could be trimmed.
Suggestions
Move the Overview and Prerequisites sections to the top of the document, or remove them entirely since the Quick Start section already serves as an effective introduction.
Consider moving detailed manifests (Blue-Green deployment, HPA, ConfigMap/Secret examples) to reference files to keep the main skill leaner, with clear one-level-deep links.
Remove repeated inline comments like '# 8080: HTTP proxy port' after the first occurrence—Claude will understand the pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code blocks, but includes some unnecessary content: the 'Prerequisites' section states obvious things ('Familiarity with Kubernetes concepts'), the 'Overview' section at the bottom repeats the title, and some inline comments are redundant (e.g., '# 8080: HTTP proxy port' repeated 8+ times). The resource limits table and service types table add value but the overall document is quite long. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready YAML manifests for every resource type (Deployment, Service, Ingress, HPA, ConfigMap, Secret). Includes concrete kubectl commands for validation and deployment. The code examples are complete and production-ready with specific values. | 3 / 3 |
Workflow Clarity | The 'Instructions' section provides a clear 4-step workflow from gathering requirements through validation. Step 4 includes explicit validation with `--dry-run=server` before applying, and a rollout status check. The error handling table provides quick feedback loops for common failure modes. | 3 / 3 |
Progressive Disclosure | References to external files exist (errors.md, examples.md, implementation.md, assets/, scripts/) which is good, but the main file itself is quite long with extensive inline YAML that could be split out. The 'Overview' and 'Prerequisites' sections appear at the bottom after all the detailed content, suggesting poor organization. The structure would benefit from a more concise overview up top with more content pushed to reference files. | 2 / 3 |
Total | 10 / 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.