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

—

Does it follow best practices?

Impact

97%

1.15x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

Quality

Content

77%

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 K8s manifest guide with a clear sequenced workflow and concrete validation, but it is verbose with redundant summary sections and has broken template references alongside inline content that overlaps with existing bundle files.

Suggestions

Add the missing 'assets/secret-template.yaml' and 'assets/pvc-template.yaml' files (or remove them from the Templates list) so every advertised reference resolves.

Collapse the 'Best Practices Summary' section — its points already appear inline in steps 2, 7, and 8 — to reduce redundancy and token cost.

Move the full inline Deployment/Service/ConfigMap/Secret/PVC templates into the existing asset templates and keep SKILL.md as an overview with signaled links, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (concrete YAML, checklists, commands) but is lengthy with redundancy: the 'Best Practices Summary' restates points already made in steps 2/7/8, and 'Purpose'/'When to Use' sections echo the frontmatter, so it could be tightened rather than earning the lean anchor 3.	2 / 3
Actionability	It provides fully executable, copy-paste-ready YAML manifests for every resource type plus concrete validation commands ('kubectl apply --dry-run=server', 'kube-score score', 'kube-linter lint'); placeholders like '<app-name>' are appropriate for a generator skill, matching the executable anchor.	3 / 3
Workflow Clarity	A clearly sequenced 10-step workflow (Gather Requirements through Validate and Test) includes an explicit validation step with dry-run/server-side checks and supporting checklists (security checklist, testing checklist), satisfying the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	References are clearly signaled and one level deep (e.g. 'See references/deployment-spec.md'), but two advertised template files do not exist ('assets/secret-template.yaml', 'assets/pvc-template.yaml') and full manifest templates are duplicated inline rather than delegated to the asset templates, fitting the some-structure-but-could-be-better-organized anchor.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 well-crafted description that states a concrete capability, enumerates specific resource types, and includes an explicit 'Use when' trigger clause with natural keywords. Minor buzzword padding ('production-ready'/'production-grade', 'best practices and security standards') does not undermine its clarity.

Dimension	Reasoning	Score
Specificity	The description names a concrete action ('Create production-ready Kubernetes manifests') applied to specific resource kinds ('Deployments, Services, ConfigMaps, and Secrets'), and the 'Use when' clause adds further actions ('generating... creating... implementing'), matching the multiple-concrete-actions anchor rather than the single-action anchor 2.	3 / 3
Completeness	It explicitly answers both what ('Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets') and when via an explicit 'Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations.' clause, satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered ('Kubernetes YAML manifests', 'K8s resources', 'Kubernetes configurations'), with both 'Kubernetes' and 'K8s' variants present, aligning with the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	Manifest generation is a clear niche with distinctive triggers ('generating Kubernetes YAML manifests'); while sibling K8s skills exist, the primary trigger is specific enough to avoid misfiring, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 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
Commit: e9f9b67

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