Tessl • The package manager for agent skills

SkillPublic

k8s-manifest-generator

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

Quality

60%

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

The canonical home for this skill is k8s-manifest-generator in rmyndharis/antigravity-skills

Quality

Content

32%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 generic template shell with no Kubernetes-specific content: no example manifests, no commands, and no validation steps. Its only resource reference points to a nonexistent `resources/implementation-playbook.md` while the real bundle files in `references/` and `assets/` are never surfaced, making the skill's actual material undiscoverable.

Suggestions

Fix the broken `resources/implementation-playbook.md` reference and instead link the real bundle files — `references/deployment-spec.md`, `references/service-spec.md`, and the `assets/` YAML templates — so the existing material is discoverable.

Add concrete, executable guidance: a minimal Deployment manifest example and a validation step such as `kubectl apply --dry-run=client -f manifest.yaml` before applying.

Replace the generic boilerplate instructions and the tautological "Do not use this skill when" section with Kubernetes-specific steps (naming conventions, resource limits, health probes, security contexts).

Dimension	Reasoning	Score
Conciseness	The body is short, but it carries generic template filler ("Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.") and a tautological "Do not use this skill when - The task is unrelated to kubernetes manifest generator" section — mostly efficient but with unnecessary content that could be tightened (anchor 3).	3 / 5
Actionability	The body contains no concrete Kubernetes guidance — no example YAML, no kubectl commands, no naming conventions or field specifics. It offers only high-level hints ("Create new Kubernetes Deployment manifests") plus a single detail pointer, which is broken — matching anchor 2 (minimal concrete guidance, missing the specific steps).	2 / 5
Workflow Clarity	"Instructions" is a generic four-item list with no manifest-specific sequence and no validation checkpoint (e.g., `kubectl apply --dry-run=client` before applying); the sequence is rough, steps are poorly defined, and validation is only vaguely mentioned as "validate outcomes" — anchor 2.	2 / 5
Progressive Disclosure	Scored against the actual bundle: `references/deployment-spec.md`, `references/service-spec.md`, and three `assets/*.yaml` templates exist but are never mentioned in the body, while the sole reference — `resources/implementation-playbook.md` — points to a nonexistent path. The detail files are undiscoverable and the one pointer is broken, fitting anchor 2 (minimal structure, references buried).	2 / 5
	Total	9 / 20 Passed

Description

70%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 distinct, enumerating the five Kubernetes resource types it covers, but it omits any "Use when..." trigger clause and lacks common synonyms like "k8s" or "YAML". Adding an explicit use-when clause would raise both completeness and trigger term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to create or modify Kubernetes manifests, deployment YAML, services, configmaps, or PVCs."

Include common synonyms such as "k8s" and "YAML" so the description matches how users naturally phrase these requests.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates five concrete resource types ("Deployments, Services, ConfigMaps, Secrets, and PersistentVolumeClaims"), but rests on a single generic action ("creating... manifests") rather than multiple distinct actions, so it matches anchor 4 rather than 5.	4 / 5
Completeness	The "what" is clear and specific, but there is no "Use when..." clause or any equivalent trigger guidance; per the judging guideline this caps completeness at 3.	3 / 5
Trigger Term Quality	"Kubernetes", "manifests", and the five resource names are terms users would naturally say, but common variations like "k8s", "YAML", or "kubectl" are absent — good coverage with a few natural terms missing (anchor 4).	4 / 5
Distinctiveness Conflict Risk	"Kubernetes manifests" plus named resource types is a clear niche with distinct triggers and minimal conflict risk with other skills, matching the anchor 5 example's clear-niche profile.	5 / 5
	Total	16 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/k8s-manifest-generator/SKILL.md
Revision: 64adc55

Reviewed: 22 hours ago

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.

k8s-manifest-generator

Table of Contents

Is this your skill?