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'.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill with executable manifests, a validation-gated workflow, and proper progressive disclosure to real bundle files. Conciseness is the weakest dimension due to duplicated inline manifests and generic boilerplate sections.

Suggestions

Trim the redundant inline manifests that duplicate assets/ templates, pointing to the templates instead to reduce token weight.

Remove the repeated '# 8080: HTTP proxy port' comments and the generic Overview/Prerequisites/Output boilerplate, which assume Claude's intelligence unnecessarily.

Consider moving the resource-limit and probe reference tables into references/ to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly concrete manifests, but the body duplicates content available in assets/ templates, repeats noise comments like '# 8080: HTTP proxy port' throughout, and ends with generic boilerplate (Overview/Prerequisites/Output) that adds little.	2 / 3
Actionability	Provides fully executable YAML manifests and concrete kubectl commands ('kubectl apply -f manifests/ --dry-run=server', 'kubectl rollout status deployment/my-api') that are copy-paste ready.	3 / 3
Workflow Clarity	The Instructions section sequences Gather → Generate → Add Production Features → Validate and Apply, with an explicit dry-run=server validation checkpoint before apply and rollout-status monitoring after.	3 / 3
Progressive Disclosure	SKILL.md stays an overview and signals one-level-deep references that exist in the bundle — references/errors.md, references/examples.md, assets/ templates, and scripts/ — with clear navigation.	3 / 3
	Total	11 / 12 Passed

Description

85%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states capabilities and explicit trigger guidance. The main weakness is trigger-term quality: 'creating' is unnatural and useful variations (k8s, manifests) are absent.

Suggestions

Replace the awkward 'creating' trigger with natural phrasing users actually say, e.g. 'deploy to Kubernetes', 'k8s manifests', or 'helm/kubectl deployment'.

Add common variations such as 'k8s', 'manifests', and 'kubectl apply' to broaden natural trigger coverage.

Tighten the 'Use when...' clause to read more naturally, e.g. 'Use when deploying applications to Kubernetes or generating production manifests.'

Dimension	Reasoning	Score
Specificity	Lists many concrete actions and resources — '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'.	3 / 3
Completeness	Explicitly answers both what ('Deploy applications... production-ready manifests') and when ('Use when working with creating kubernetes deployments. Trigger with...'), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Provides relevant keywords ('kubernetes', 'deployments') but 'creating' is an awkward, non-natural trigger and common variations like 'k8s', 'manifests', or 'deploy to' are missing.	2 / 3
Distinctiveness Conflict Risk	Targets a clear Kubernetes-deployment niche with distinct triggers; unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/devops/kubernetes-deployment-creator/skills/creating-kubernetes-deployments/SKILL.md
Commit: c4eafaf

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.