CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/kubernetes-operations/skills/k8s-manifest-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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.

The body is a well-organized overview that correctly defers detail to a real reference file, but it over-defers: for a manifest generator it contains no inline YAML example or ordered workflow, and its Purpose/When-to-Use/Next-Steps sections pad tokens with content Claude already has. Strongest in progressive disclosure and troubleshooting; weakest in executable guidance for the primary task.

Suggestions

Add one minimal copy-paste Deployment+Service YAML skeleton (or point explicitly to assets/deployment-template.yaml) so the core generation task has executable guidance without opening the reference file.

Delete the "Purpose" section (it restates the opening line), collapse "When to Use This Skill" into the description's triggers or a one-line pointer, and trim the generic "Next Steps" advice.

Include an explicit ordered workflow in the body — gather requirements, draft manifests, validate with `kubectl apply -f manifest.yaml --dry-run=server`, then apply — instead of the unordered ten-principle Best Practices list.

DimensionReasoningScore

Conciseness

The "Purpose" section restates the intro, "When to Use This Skill" duplicates the frontmatter description nearly verbatim, and "Next Steps" offers generic advice (store in Git, set up CI/CD, consider Helm) that Claude already knows.

3 / 5

Actionability

Troubleshooting supplies concrete commands ("kubectl describe pod <pod-name>", "kubectl get endpoints <service-name>", a busybox debug one-liner), but the core manifest-generation task has zero inline YAML — only principle bullets like "Always set resource requests and limits".

3 / 5

Workflow Clarity

No ordered creation workflow appears in the body (the 10-step sequence lives in references/details.md), and validation is only bullet #8 "Validate before applying - Use dry-run and validation tools" with no command; the troubleshooting symptom-to-check sequences keep this above a 2.

3 / 5

Progressive Disclosure

A lean 77-line overview with a clearly signaled, verified reference ("Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient."), but the chain is two levels deep (SKILL.md → details.md → specs/assets) and three of the four bundle files are invisible from the top level.

4 / 5

Total

13

/

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 with a clear what, an explicit multi-trigger when-clause, good synonym coverage (Kubernetes/K8s, YAML), and third-person phrasing. Its weaknesses are reliance on one action verb, mild buzzword padding ("best practices and security standards"), and omission of PersistentVolumeClaims despite the body covering them.

DimensionReasoningScore

Specificity

Names the domain and four concrete resource types ("Deployments, Services, ConfigMaps, and Secrets") but leans on a single action verb and the generic filler "following best practices and security standards" rather than listing multiple distinct concrete actions.

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 three concrete trigger phrases.

5 / 5

Trigger Term Quality

Triggers cover the key synonyms and formats ("Kubernetes YAML manifests", "K8s resources", "production-grade Kubernetes configurations"), but natural user phrases like "write a deployment yaml", "kubectl apply", or resource-specific asks are missing.

4 / 5

Distinctiveness Conflict Risk

Raw manifest generation is a clear niche, but the broad trigger "creating K8s resources" risks minor overlap with closely related Kubernetes skills such as security-policy or Helm scaffolding skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/kubernetes-operations/skills/k8s-manifest-generator/SKILL.md

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.