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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill creating-kubernetes-deployments86
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 excels at specificity and distinctiveness by listing concrete Kubernetes resources and production features. However, it lacks explicit trigger guidance ('Use when...') and misses common user terminology like 'k8s' or 'kubectl'. Adding a 'Use when' clause would significantly improve Claude's ability to select this skill appropriately.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when deploying to Kubernetes, creating k8s manifests, or setting up container orchestration'
Include common user terminology variations: 'k8s', 'kubectl', 'pods', 'containers', 'YAML manifests', 'cluster deployment'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and Kubernetes resources: Deployments, Services, Ingress, HPA, ConfigMaps, Secrets, StatefulSets, NetworkPolicies, plus specific features like health checks, resource limits, auto-scaling, and TLS termination. | 3 / 3 |
Completeness | Clearly answers 'what' with detailed capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through the domain context. | 2 / 3 |
Trigger Term Quality | Includes good technical terms like 'Kubernetes', 'Deployments', 'Ingress', 'HPA' that users would mention, but missing common variations like 'k8s', 'kubectl', 'pods', 'containers', or 'YAML manifests' that users naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Kubernetes deployment with production manifests. The specific resource types and features make it highly distinguishable from general deployment, Docker, or cloud infrastructure skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that provides comprehensive, production-ready Kubernetes deployment guidance. It efficiently covers deployments, services, ingress, HPA, ConfigMaps, and Secrets with executable YAML examples. The content is well-organized with clear workflows, appropriate validation steps, and good progressive disclosure to external references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing production-ready YAML manifests without explaining basic Kubernetes concepts Claude already knows. Every section delivers actionable configuration with minimal prose. | 3 / 3 |
Actionability | All examples are complete, copy-paste ready YAML manifests with specific values. The kubectl commands for validation and deployment are executable, and tables provide concrete configuration values for different scenarios. | 3 / 3 |
Workflow Clarity | The Instructions section provides a clear 4-step sequence with explicit validation using dry-run before applying, and includes a rollout status check. The workflow covers gathering requirements through validation with appropriate checkpoints. | 3 / 3 |
Progressive Disclosure | The skill provides a comprehensive quick start with essential patterns inline, then appropriately references external files for errors, examples, assets, and scripts. References are one level deep and clearly signaled. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
68%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
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_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | 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.