Skills k8s-manifest-generator

📦

k8s-manifest-generator

Name: k8s-manifest-generator
Author: sickn33

Content revision r1 Safe ⚙️ External commands🌐 Network access📁 Filesystem access🔑 Env variables

Generate Kubernetes Manifests Safely

Kubernetes manifests are easy to misconfigure when teams write them from memory. This skill turns requirements into structured YAML guidance with security, probes, resources, and service patterns.

Supports: Claude Codex Code(CC)

🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "k8s-manifest-generator" from https://skillstore.io/skills/sickn33-k8s-manifest-generator.md and its manifest at https://skillstore.io/api/skills/sickn33-k8s-manifest-generator/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-k8s-manifest-generator.md Signed manifest GET /api/skills/sickn33-k8s-manifest-generator/manifest Signed lockfile GET /api/skills/sickn33-k8s-manifest-generator/lockfile

Test it

Using "k8s-manifest-generator". Create a production web Deployment for image acme/api:1.4.2 with port 8080.

Expected outcome:

A Deployment plan with three replicas, rolling updates, health probes, resource requests, and non-root container settings.
A short checklist covering namespace, labels, image tag, secret references, and rollout verification.

Using "k8s-manifest-generator". Expose my internal payment service to other pods only.

Expected outcome:

A ClusterIP Service recommendation with named ports, selectors, and DNS guidance for same-namespace and cross-namespace access.
Notes explaining why NodePort and public LoadBalancer are not appropriate for this internal service.

Using "k8s-manifest-generator". Review this manifest before production deployment.

Expected outcome:

A prioritized review of missing resource limits, unsafe service exposure, weak secret handling, and absent readiness checks.
Concrete remediation steps that keep the manifest aligned with Kubernetes production practices.

Security Audit

Safe

v5 • 7/9/2026 Open versioned report

Most static alerts are false positives caused by Kubernetes examples, reserved documentation IP ranges, placeholder secrets, and Markdown file references. One medium issue remains: the service reference includes a public 0.0.0.0/0 LoadBalancer range that could be unsafe if copied into production. No prompt injection, host-side command execution, credential exfiltration, or unauthorized external network behavior was found.

Files scanned

2,699

Lines analyzed

Review items

False positives ignored

Capability review items (1)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium

references/service-spec.md:505

Hardcoded IP address

- 0.0.0.0/0

The LoadBalancer example allows 0.0.0.0/0 as a source range, which exposes the service to all clients if copied into production. This is not malware, but it is an unsafe production pattern without a clear warning.

Risk Factors

⚙️ External commands (9)

assets/configmap-template.yaml:209 assets/configmap-template.yaml:183 assets/configmap-template.yaml:206 assets/deployment-template.yaml:167 references/deployment-spec.md:187 references/deployment-spec.md:190 references/deployment-spec.md:718 SKILL.md:31 SKILL.md:35

🌐 Network access (17)

assets/configmap-template.yaml:100 assets/configmap-template.yaml:209 assets/configmap-template.yaml:36 assets/configmap-template.yaml:127 assets/service-template.yaml:59 references/service-spec.md:358 references/service-spec.md:363 references/service-spec.md:92 references/service-spec.md:179 references/service-spec.md:181 references/service-spec.md:196 references/service-spec.md:198 references/service-spec.md:202 references/service-spec.md:377 references/service-spec.md:505 references/service-spec.md:571 resources/implementation-playbook.md:181

📁 Filesystem access (2)

references/deployment-spec.md:187 references/deployment-spec.md:432

🔑 Env variables (3)

references/deployment-spec.md:105 references/deployment-spec.md:658 resources/implementation-playbook.md:207

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-k8s-manifest-generator/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-k8s-manifest-generator/security.svg)](https://skillstore.io/skills/sickn33-k8s-manifest-generator?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-k8s-manifest-generator?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-k8s-manifest-generator/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-k8s-manifest-generator.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). k8s-manifest-generator security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-k8s-manifest-generator/audits/5

BibTeX citation

@techreport{sickn33-sickn33-k8s-manifest-generator-2026,
  author = {sickn33},
  title = {k8s-manifest-generator security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-k8s-manifest-generator/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "k8s-manifest-generator security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/sickn33-k8s-manifest-generator/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-k8s-manifest-generator:audit:5"
    description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

sickn33 Recommended Current

sickn33-k8s-manifest-generator

Skillstore Score 79

Evidence Confidence High

Skillstore usage 16

Updated

2026-08-21

wshobson

wshobson-k8s-manifest-generator

Skillstore Score 77

Evidence Confidence High

Skillstore usage 12

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Create a Web Service Release

Generate a Deployment and Service for a containerized web application with probes, resource limits, and safe rollout settings.

Standardize Platform Templates

Build reusable manifest patterns for namespaces, labels, ConfigMaps, Secrets, Services, and storage claims.

Review Production Readiness

Compare proposed Kubernetes manifests against production practices for security contexts, availability, resources, and service exposure.

Try These Prompts

Generate a Basic Deployment

Generate a Kubernetes Deployment for image <image>:<tag>, namespace <namespace>, container port <port>, and three replicas. Include probes and resource requests.

Add Service Exposure

Create the matching Kubernetes Service for my Deployment. Explain whether ClusterIP, LoadBalancer, NodePort, or headless Service fits my access requirements.

Build Environment Configuration

Create ConfigMap and Secret manifest guidance for these environment variables and files. Use placeholders and call out any values that must stay out of Git.

Harden a Production Manifest

Review this Kubernetes manifest for production readiness. Check security context, probes, resources, update strategy, service exposure, labels, and secret handling.

Best Practices

Provide image names, ports, namespaces, storage needs, and service exposure requirements before asking for a manifest.
Replace placeholders and review Secret, LoadBalancer, and ExternalIP fields before applying any generated manifest.
Validate generated manifests with kubectl, policy checks, and a staging cluster before production use.

Avoid

Do not apply generated placeholder values directly to production clusters.
Do not expose a LoadBalancer to every source range unless that is an intentional public API decision.
Do not store real passwords, private keys, or tokens in generated YAML files committed to source control.