k8s-manifest-generator

Step-by-step guidance for creating production-ready Kubernetes manifests including Deployments, Services, ConfigMaps, Secrets, and PersistentVolumeClaims.

Quality

45%

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 ./skills/k8s-manifest-generator/SKILL.md

Quality

Content

25%Scale 1-5

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

This skill is essentially a placeholder that provides no actionable Kubernetes manifest guidance. It contains zero YAML examples, no specific kubectl commands, no template patterns, and no concrete best practices despite claiming to be a 'production-ready' manifest generator. The entire body consists of generic meta-instructions that could apply to any skill topic, with all real content deferred to a bundle file that doesn't exist.

Suggestions

Add concrete, copy-paste ready YAML examples for at least the core resource types (Deployment, Service, ConfigMap) with production best practices like resource limits, health checks, and security contexts already included.

Include specific validation steps such as `kubectl apply --dry-run=client -f manifest.yaml` or `kubectl diff -f manifest.yaml` to verify manifests before applying them.

Replace the generic instructions ('Apply relevant best practices') with specific Kubernetes best practices like label conventions, resource naming patterns, and recommended resource limit values.

Either provide the referenced `resources/implementation-playbook.md` bundle file or inline the essential patterns directly in the SKILL.md so the skill is self-contained enough to be useful.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections add moderate padding without providing actionable value. The instructions section is generic and could apply to almost any skill. However, it's not egregiously verbose.	3 / 5
Actionability	The skill provides no concrete code, no YAML examples, no specific commands, and no executable guidance whatsoever. For a 'Kubernetes Manifest Generator' skill, there are zero manifest examples, templates, or copy-paste ready content. Everything is vague direction like 'Apply relevant best practices' and 'Provide actionable steps.'	1 / 5
Workflow Clarity	There is a rough implied sequence ('Clarify goals' → 'Apply best practices' → 'Provide actionable steps and verification') but the steps are extremely generic and poorly defined. No validation checkpoints, no specific commands for verifying manifests (e.g., kubectl dry-run, kubeval), and no feedback loops for error recovery.	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable structure, but no bundle files are provided so the reference is unverifiable and potentially broken. The SKILL.md itself contains almost no substantive content to serve as a useful overview — it delegates everything to a file that may not exist.	2 / 5
	Total	8 / 20 Passed

Description

66%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 does a good job listing specific Kubernetes resource types and clearly communicating the skill's purpose. However, it lacks an explicit 'Use when...' clause, which limits its completeness and makes it harder for Claude to know exactly when to select this skill. Adding common abbreviations like 'k8s' and trigger phrases would further improve discoverability.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about Kubernetes, k8s, deploying containers, writing YAML manifests, or configuring cluster resources.'

Include common synonyms and abbreviations such as 'k8s', 'YAML', 'kubectl apply', '.yaml files' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists several specific Kubernetes resource types (Deployments, Services, ConfigMaps, Secrets, PersistentVolumeClaims) and describes the action as 'creating production-ready Kubernetes manifests.' Minor gaps—doesn't mention Ingress, StatefulSets, RBAC, or other common resources.	4 / 5
Completeness	Clearly answers 'what' (creating production-ready Kubernetes manifests for specific resource types) but has no explicit 'when' clause or trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes strong natural keywords like 'Kubernetes manifests', 'Deployments', 'Services', 'ConfigMaps', 'Secrets', and 'PersistentVolumeClaims' that users would naturally mention. Missing common variations like 'k8s', 'YAML', 'kubectl', 'pods', or file extensions like '.yaml'/'.yml'.	4 / 5
Distinctiveness Conflict Risk	Fairly distinct by specifying Kubernetes manifests and listing specific resource types, which narrows the domain well. Minor overlap risk with general YAML generation skills or broader DevOps/infrastructure skills.	4 / 5
	Total	15 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/k8s-manifest-generator/SKILL.md
Commit: fbdfd63

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.