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 solid skill description that clearly communicates what it does (Kubernetes manifest generation with specific resource types) and when to use it. Its main weakness is the narrow set of trigger terms, which misses common user language like 'k8s', 'deploy to cluster', 'pod', or 'YAML manifests'. The explicit trigger term list at the end feels artificially constrained compared to the rich detail in the rest of the description.
Suggestions
Expand trigger terms to include common variations users would naturally say: 'k8s', 'deploy', 'manifests', 'pods', 'containers', 'cluster', 'YAML', '.yaml'
Remove the rigid 'Trigger with' clause and instead integrate natural keywords into the 'Use when' clause, e.g., 'Use when deploying apps to Kubernetes/k8s, creating manifests, configuring pods, or setting up cluster resources.'
| 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 to Kubernetes with production-ready manifests, supporting various resource types) 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 the explicit trigger list ('creating', 'kubernetes', 'deployments') is narrow and misses common variations users would say like 'k8s', 'deploy', 'manifests', 'pods', 'helm', 'cluster', 'container orchestration', or 'YAML manifests'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around Kubernetes deployment manifests with specific resource types listed. Unlikely to conflict with generic coding or infrastructure skills due to the highly specific Kubernetes terminology. | 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 solid, actionable Kubernetes deployment skill with excellent concrete YAML examples and a clear workflow including validation steps. Its main weaknesses are structural: the document is somewhat long with content that could be offloaded to reference files, it has oddly placed sections at the end (Overview, Prerequisites, Output) that feel like boilerplate appended after the real content, and it references bundle files that don't exist. The repeated '# 8080: HTTP proxy port' comments and some redundant explanations could be trimmed.
Suggestions
Remove or relocate the 'Overview', 'Prerequisites', and 'Output' sections at the bottom — they duplicate the introduction or state obvious information and feel like misplaced boilerplate.
Move detailed examples (blue-green deployment, full probe configurations) into the referenced files like examples.md to reduce the main skill's length and improve progressive disclosure.
Eliminate repeated inline comments like '# 8080: HTTP proxy port' — state it once and trust Claude to understand port references throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and concrete YAML, 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 comments like '# 8080: HTTP proxy port' are repeated excessively throughout. The resource limits table and service types table add value but the overall document could be tightened. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready YAML manifests for deployments, services, ingress, HPA, ConfigMaps, Secrets, and more. It includes concrete kubectl commands for validation and deployment, specific resource limit recommendations by workload type, and complete health check configurations with meaningful parameter values. | 3 / 3 |
Workflow Clarity | The 'Instructions' section provides a clear 4-step workflow from gathering requirements through validation. Step 4 includes explicit validation via `kubectl apply --dry-run=server` before applying, and a rollout status check afterward. The error handling table provides quick diagnostic steps for common failure modes, creating an implicit feedback loop. | 3 / 3 |
Progressive Disclosure | The skill references external files (errors.md, examples.md, implementation.md, assets/, scripts/) which is good progressive disclosure structure, but no bundle files are provided to back these references. The document itself is quite long (~250 lines of YAML examples inline) and some content like the full blue-green deployment example or detailed probe configurations could be moved to reference files. The 'Overview' and 'Prerequisites' sections at the bottom feel misplaced and disorganized. | 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
3a2d27d
- 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.