k8s-manifest-generator

Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations.

1.15x

Quality

82%

Does it follow best practices?

Impact

97%

1.15x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is k8s-manifest-generator in wshobson/agents

Quality

Content

81%Weight 40%Scale 1-5

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

Highly actionable content with complete executable templates, a well-sequenced workflow ending in explicit validation and troubleshooting recovery. The main weaknesses are token inefficiency from redundant restatement of the skill's purpose and duplicated best-practices lists, and two phantom asset files listed in the Templates section.

Suggestions

Remove the redundant "Purpose" and "When to Use This Skill" sections (they restate the opening paragraph and frontmatter description) and consolidate the "Best Practices Summary" with the inline "Best practices to apply" bullets, which currently repeat the same points.

Fix the Templates listing: either create assets/secret-template.yaml and assets/pvc-template.yaml or remove them from the list, since only configmap-, deployment-, and service-template.yaml actually exist in the bundle.

Trim guidance Claude already knows (e.g., "Never commit secrets to Git in plain text", "Follow naming conventions") and move the detailed Kustomize directory structures into a reference file to reduce inline token load.

Dimension	Reasoning	Score
Conciseness	The opening paragraph, "Purpose", and "When to Use This Skill" sections triple-restate the frontmatter, and the 10-item "Best Practices Summary" duplicates the inline "Best practices to apply" bullets (resource limits, health checks, security contexts, labels appear twice). Mostly efficient templates, but noticeable tightening needed — more than the minor trimming of anchor 4, less than the heavy concept padding of anchor 2.	3 / 5
Actionability	Complete placeholder-templated YAML for every resource kind (Deployment, Service, ConfigMap, Secret, PVC, security context), copy-paste kubectl validation commands ("kubectl apply -f manifest.yaml --dry-run=server", "kube-score score manifest.yaml"), and concrete troubleshooting commands fully cover the common cases.	5 / 5
Workflow Clarity	A clear 10-step sequence culminating in explicit validation (client/server dry-run, kubeval, kube-score, kube-linter) with a testing checklist, plus a Troubleshooting section giving error-recovery commands — matching the anchor with explicit validation steps and feedback for error recovery.	5 / 5
Progressive Disclosure	Good structure with clearly signaled one-level-deep references (references/deployment-spec.md and references/service-spec.md both exist), but the Templates section lists assets/secret-template.yaml and assets/pvc-template.yaml which do not exist in the bundle (only configmap-, deployment-, and service-template.yaml are present), and some full YAML blocks duplicate what the referenced files cover.	4 / 5
	Total	17 / 20 Passed

Description

83%Weight 40%Scale 1-5

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 description that clearly states what the skill does and when to use it, with concrete resource-kind enumeration and natural trigger phrasing including the K8s abbreviation. Minor improvements possible: vary the action verbs beyond "create", drop the generic best-practices clause, and add missing natural triggers like kubectl and PersistentVolumeClaims.

Dimension	Reasoning	Score
Specificity	"Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets" enumerates concrete resource kinds, matching the several-specific-actions anchor with minor gaps (single action verb, generic "following best practices and security standards" filler, PVCs omitted even though the body covers them).	4 / 5
Completeness	Explicitly answers both what ("Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets") and when ("Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations" includes natural phrasings and the K8s abbreviation, but misses common user terms like kubectl, "deploy to Kubernetes", or .yaml file extensions.	4 / 5
Distinctiveness Conflict Risk	Kubernetes manifest generation is a distinct niche, but "creating K8s resources" and "implementing production-grade Kubernetes configurations" are broad enough to overlap with closely related skills such as helm-chart-scaffolding or k8s-security-policies referenced in the body.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (535 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/kubernetes-operations/skills/k8s-manifest-generator/SKILL.md
Commit: a65ce00

Reviewed: 6 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.