k8s-manifest-generator

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

Quality

51%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/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 well-sectioned and concise but offers almost no concrete, executable guidance, and its only file reference points to a path that does not exist in the bundle. Fixing the broken references and replacing generic instructions with specific k8s steps would substantially improve the score.

Suggestions

Correct the reference path and filename: point to the real bundle files (e.g. `references/deployment-spec.md`, `references/service-spec.md`, and the `assets/*-template.yaml` templates) instead of the non-existent `resources/implementation-playbook.md`.

Replace the generic 'Instructions' bullets with concrete, k8s-specific steps, e.g. example manifest snippets, `kubectl apply -f` commands, and a `kubectl validate`/`kubectl describe` verification step.

Add an explicit validation checkpoint in the workflow (e.g. 'Run `kubectl apply --dry-run=server -f manifest.yaml` before applying; only proceed when it passes') to support destructive/batch manifest operations.

Dimension	Reasoning	Score
Conciseness	The body is short and avoids explaining Kubernetes concepts Claude already knows, but the 'Instructions' bullets are generic boilerplate applicable to any skill and the 'Do not use this skill when' bullets are circular, so it could be tightened.	3 / 5
Actionability	Guidance is only high-level hints ('Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') with no concrete commands, YAML examples, or specific steps to execute.	2 / 5
Workflow Clarity	A rough generic sequence exists (clarify -> apply+validate -> provide+verify) but steps are poorly defined and validation is only vaguely mentioned with no checkpoints, which is a problem for batch/destructive manifest operations.	2 / 5
Progressive Disclosure	The body references `resources/implementation-playbook.md`, but the actual bundle is `references/` containing `deployment-spec.md` and `service-spec.md` plus `assets/*.yaml` templates; the referenced path is the wrong directory and a non-existent file, and the real bundle files are never referenced, defeating navigation.	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 clearly occupies a distinct niche, but it omits any explicit 'when to use' trigger guidance, which the rubric caps at completeness 3. Adding a 'Use when...' clause would meaningfully raise the score.

Suggestions

Append an explicit trigger clause, e.g. 'Use when creating or editing Kubernetes manifests for Deployments, Services, ConfigMaps, Secrets, or PVCs, or when the user mentions k8s/yaml resource definitions.'

Add common synonyms/extensions ('k8s', 'yaml', 'manifest files') to broaden trigger-term coverage.

Vary the action verbs beyond 'creating' (e.g., 'generate, validate, and edit') to reflect a fuller set of concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('production-ready Kubernetes manifests') and enumerates several concrete resource types (Deployments, Services, ConfigMaps, Secrets, PersistentVolumeClaims), but the action is a single verb ('creating') rather than multiple distinct actions, leaving minor coverage gaps.	4 / 5
Completeness	Clearly states 'what' (creating production-ready manifests for the listed resource types) but contains no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes natural terms users say ('Kubernetes manifests', 'Deployments', 'Services', 'ConfigMaps', 'Secrets'), but omits common synonyms/extensions like 'k8s', 'yaml', or 'helm', so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Kubernetes manifest generation for specific resource types) with distinct triggers and minimal overlap risk with other skills.	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: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/k8s-manifest-generator/SKILL.md
Commit: 57c135b

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.