kubernetes-manifests

Generate Kubernetes manifests for Deployments, Services, Ingress, ConfigMaps, Secrets, HPA, PVCs with kustomize overlay structure, health probes, and resource limits.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./infrastructure/kubernetes-manifests/SKILL.md

Quality

Content

76%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 content is highly actionable with complete, executable manifests and commands and no filler, and is cleanly sectioned. Its weaknesses are the lack of an explicit sequenced apply-workflow with validation checkpoints and the large volume of inline template content.

Suggestions

Add an explicit numbered deployment workflow with checkpoints, e.g. 1) customize images/resources, 2) 'kubectl diff -k' to validate, 3) 'kubectl apply -k', 4) 'kubectl rollout status' to verify, 5) on failure 'kubectl describe pod' and retry.

Move the full per-resource manifest templates (PVC, HPA, Ingress) into a references/ file and keep SKILL.md as an overview pointing to them, tightening the inline token budget.

Remove the duplicated blockquote description at the top and the empty 'touch' scaffold steps, or replace the scaffold with a single 'mkdir + kustomize init' command.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence — no concept explanations — but the top blockquote repeats the frontmatter description and the scaffold section creates empty files whose full contents are then re-shown, minor redundancies that could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready YAML manifests for every resource type plus concrete kubectl commands covering the common cases (apply, diff, rollout status, port-forward, scale, restart).	5 / 5
Workflow Clarity	The sections imply a sequence (scaffold → structure → patterns → commands) and a validation step exists ('kubectl diff -k' before apply), but there is no explicit numbered workflow with validation checkpoints for the batch/cluster-apply operation, so the workflow-clarity cap applies.	3 / 5
Progressive Disclosure	The file is well-organized with clear section headers and easy navigation, and no bundle files are needed; however ~380 lines of full manifest templates are inlined, some of which could be split into reference files for a tighter overview.	4 / 5
	Total	16 / 20 Passed

Description

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

The description is specific and clearly distinct, listing concrete resource types and structural features. Its main weakness is the absence of any explicit 'when to use' trigger guidance, which caps completeness.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when generating Kubernetes manifests, scaffolding kustomize base/overlay structure, or when the user mentions Deployments, Services, Ingress, HPA, or PVCs.'

Include natural synonyms and file extensions (e.g. 'k8s', '.yaml manifests', 'kubectl apply') to broaden trigger-term coverage.

Consider mentioning environment overlays (dev/staging/production) in the description itself to surface that common use case.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions and resource types — 'Deployments, Services, Ingress, ConfigMaps, Secrets, HPA, PVCs with kustomize overlay structure, health probes, and resource limits' — giving comprehensive coverage of what the skill generates.	5 / 5
Completeness	It clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	It includes strong natural domain terms a user would say (Kubernetes manifests, kustomize overlays, HPA, Ingress) but omits common synonyms and file extensions like .yaml, so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche — kustomize-based Kubernetes manifest generation with overlays and probes — and the integration notes explicitly delineate it from paired skills (dockerfile-generator, terraform-starter), minimizing conflict risk.	5 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: achreftlili/deep-dev-skills
Path: infrastructure/kubernetes-manifests/SKILL.md
Commit: 181fcbc

Reviewed: 1 day 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.