CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

55

Quality

61%

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

Quality

Content

22%

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

The body is thin and generic: instructions are abstract boilerplate with no executable guidance or validation loop, and the one referenced resource path is missing while the real bundle files go unused. It reads as a placeholder rather than actionable skill content.

Suggestions

Replace the abstract Instructions with concrete, executable guidance — show kubectl apply commands or inline a minimal Deployment/Service YAML example drawn from the existing assets/ templates.

Add a real workflow with a validation checkpoint, e.g. generate manifest → `kubectl apply --dry-run=client -f` or `kubeval` → fix and re-validate before presenting.

Fix progressive disclosure by pointing to the actual bundle files (references/deployment-spec.md, references/service-spec.md, assets/*-template.yaml) instead of the non-existent resources/implementation-playbook.md.

DimensionReasoningScore

Conciseness

The body is mostly lean with clear sections, but the 'Do not use this skill when' bullets ('unrelated to kubernetes manifest generator', 'a different domain or tool outside this scope') are generic filler and the 'Use this skill when' list partly re-states the description.

2 / 3

Actionability

The Instructions are abstract directives — 'Clarify goals, constraints, and required inputs', 'Apply relevant best practices', 'Provide actionable steps' — with no concrete code, commands, or executable examples; it describes rather than instructs, matching the score-1 anchor.

1 / 3

Workflow Clarity

There is no real sequenced workflow for multi-step manifest generation and no validation checkpoint; the listed bullets are generic directives, not a validate→fix→retry loop, matching the score-1 anchor for missing sequence and validation.

1 / 3

Progressive Disclosure

Sections provide some structure and a reference is signaled, but the referenced `resources/implementation-playbook.md` does not exist and the actual bundle files in references/ and assets/ are never surfaced, so navigation is broken rather than one-level-deep clean.

2 / 3

Total

6

/

12

Passed

Description

100%

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, third-person description that states concrete capabilities, provides explicit 'Use when' triggers with natural keyword variations, and occupies a clear, low-conflict niche. No meaningful gaps relative to the rubric anchors.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across named resource types — 'Deployments, Services, ConfigMaps, and Secrets' — matching the top specificity anchor rather than the vague score-2 phrasing that names only a domain.

3 / 3

Completeness

Explicitly answers both what ('Create production-ready Kubernetes manifests...') and when via an explicit 'Use when...' clause, satisfying the score-3 bar rather than the implied-when score-2 case.

3 / 3

Trigger Term Quality

Covers natural user phrasings including 'Kubernetes YAML manifests', 'K8s resources', and 'production-grade Kubernetes configurations', giving good variation as the score-3 anchor expects.

3 / 3

Distinctiveness Conflict Risk

The Kubernetes-manifest niche with concrete resource triggers is clearly distinguishable and unlikely to fire for unrelated skills, matching the clear-niche score-3 anchor.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-skills
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.