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

High

Do not use without reviewing

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.

A thorough, highly actionable manifest-generation skill with complete code examples, explicit validation checkpoints, and well-organized references. Its main weakness is redundancy — several sections restate the frontmatter or repeat inline guidance — plus two advertised template files that are missing from the bundle.

Suggestions

Remove or merge the 'Purpose' and 'When to Use This Skill' sections with the frontmatter description to eliminate redundancy, and drop the 'Best Practices Summary' that reiterates inline best-practice bullets.

Either add the missing assets/secret-template.yaml and assets/pvc-template.yaml or remove them from the Templates listing so referenced paths resolve.

Trim basic-explanation bullets (e.g. 'Use ConfigMaps for non-sensitive data only') that restate Kubernetes knowledge Claude already has.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete YAML and commands, but includes redundant sections — 'Purpose' and 'When to Use This Skill' restate the frontmatter, 'Best Practices Summary' repeats inline guidance, and some points explain K8s basics Claude already knows ('Use ConfigMaps for non-sensitive data only').	3 / 5
Actionability	Fully executable, copy-paste-ready YAML for every resource type plus concrete kubectl commands for validation and troubleshooting; placeholders are appropriate templating, not pseudocode.	5 / 5
Workflow Clarity	A clear 10-step numbered sequence culminating in an explicit 'Validate and Test' step with multiple concrete validation commands (dry-run client/server, kubeval, kube-score, kube-linter), a testing checklist, and a troubleshooting section for error recovery.	5 / 5
Progressive Disclosure	Good structure with one-level-deep, clearly signaled references to real bundle files (references/deployment-spec.md, references/service-spec.md, assets/*.yaml), but the Templates section lists secret-template.yaml and pvc-template.yaml that do not exist in assets/, a minor organization gap.	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, third-person description that cleanly states the skill's purpose and explicit 'Use when' triggers with natural K8s/Kubernetes synonyms. Coverage is solid but slightly narrower than the body, and the K8s-manifest niche brushes against adjacent packaging skills.

Suggestions

Mention PersistentVolumeClaims and StatefulSets in the description so the 'what' matches the body's full resource coverage.

Add at least one natural user phrase like 'k8s yaml' or 'deploy to Kubernetes' to broaden trigger-term coverage.

Sharpen distinctiveness from helm-chart-scaffolding by framing the trigger as raw manifest authoring rather than general Kubernetes work.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions and resource types ('Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets'), but omits PVC/StatefulSet/Ingress that the body covers, leaving minor gaps versus the comprehensive anchor.	4 / 5
Completeness	Explicitly answers both what ('Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards') and when ('Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations').	5 / 5
Trigger Term Quality	Good keyword coverage including the natural synonym 'K8s resources' and 'Kubernetes YAML manifests', though a few natural phrasings users say (e.g. 'k8s yaml', 'deploy to kubernetes') are absent.	4 / 5
Distinctiveness Conflict Risk	Mostly a distinct niche (raw manifest generation) with clear triggers, but minor overlap risk with closely related packaging/deployment skills like helm-chart-scaffolding and gitops-workflow listed as related.	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: 6453c0b

Reviewed: about 9 hours 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.