skywalkskills

CatalogueDevOps & Platform

I1Ready

Container & Kubernetes Hardening Audit

Reads your Dockerfiles and Kubernetes manifests for the settings that let one flaw become a break-in.

What it examines

  • Containers that run as root or with extra privileges
  • Base images that are unpinned, bloated, or from an unknown source
  • Secrets left behind in image layers
  • Pods with no resource limits and a single replica
  • Cluster roles and namespaces with no network rules
  • Whether images are scanned before they ship

What you get back

A findings file. Each item has the evidence, how serious it is, and a fix.

Dependencies

  • An AI coding agent that reads SKILL.md files, such as Claude Code, Codex or Gemini CLI
  • Read access to the repository: Dockerfiles, compose files, Kubernetes manifests, Helm charts, Kustomize overlays and the CI files that build images
  • Optional: a read-only kubeconfig, to compare the running cluster with the repository
  • Optional: Hadolint, kube-linter, Kubescape or Trivy, if already installed. Their output is treated as leads only.
  • Python 3 with the jsonschema package, to check findings.json before fixing anything

How it works

The audit only reads. It never builds or pulls an image, runs a container or changes a cluster.

It finds every Dockerfile and manifest afresh, then runs all the hardening checks, from base image trust to cluster access, network policy and image scanning in the pipeline.

With a kubeconfig it uses get and describe calls to compare what runs with what the repository says. Any scanner output is a lead; a finding still needs a line the audit read itself.

You get findings.json and findings.md, ordered by what an attacker or an outage gains. The remediate skill reads findings.json and applies the safe fixes one change at a time.

Setup

  1. Unzip the download, then copy the audit and remediate folders into your agent's skills folder (for Claude Code, .claude/skills/) in the repository you want to check.
  2. If you want the live comparison, point your agent at a read-only kubeconfig. Skip this if you do not.
  3. Open the repository in your agent and ask it to run the i1-container-kubernetes-hardening-audit skill.
  4. Check the result with the validator: pip install jsonschema, then python3 schema/validate.py findings.json.
  5. Ask your agent to run the i1-container-kubernetes-hardening-remediate skill using findings.json. Fixes that need approval wait for you.

Run it with your agent

Copy the prompt, fill in the parts in square brackets, and paste it into your agent.

Audit prompt

Run the i1-container-kubernetes-hardening-audit skill on this repository. Cluster access: [path to a read-only kubeconfig, or none]. Mode: audit only. Do not change any code. Write findings.json and findings.md in the repository root.

Fix prompt, after you have findings.json

Run the i1-container-kubernetes-hardening-remediate skill using findings.json. Work through the findings I choose, and leave the rest open.

What is inside

The files that make up this skill, as your agent reads them.

packages/i1-container-kubernetes-hardening

audit › SKILL.md

Sign in to download

Use the email and password you signed up with.