Skip to content
TrustedSkillsbeta
Back to all skills

Kubernetes Security Policies

Checked
nickcrew·vlatest·cloud·MIT

Helps with Kubernetes, security as part of deploying and managing cloud infrastructure workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add nickcrew/claude-cortex --skill kubernetes-security-policies -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

nickcrew

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned nickcrew/claude-ctx-plugin at bb47af79ad.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
bb47af79ad
Manifest
skills/kubernetes-security-policies/SKILL.md
Scanned
9 files, 1,205 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to generate and manage Kubernetes SecurityPolicy objects, enforcing strict access controls within cluster environments. It helps automate the creation of policies that restrict pod capabilities and define network rules for enhanced security posture.

When to use it

  • Enforcing non-root execution requirements for all pods in a namespace.
  • Defining specific network egress rules to limit external data exfiltration.
  • Automating compliance checks against industry security standards like CIS benchmarks.
  • Restricting privilege escalation paths by disabling dangerous capabilities such as NET_ADMIN.

Key capabilities

  • Generates YAML definitions for Kubernetes SecurityPolicy resources.
  • Configures pod-level restrictions including runAsUser and fsGroup settings.
  • Applies network policies to isolate workloads from unauthorized traffic.
  • Integrates directly with the Claude context plugin for seamless workflow execution.

Example prompts

  • "Create a SecurityPolicy that prevents any container from running as root in the production namespace."
  • "Generate a policy allowing pods to reach only specific internal IP ranges while blocking all external egress."
  • "Draft a security configuration that disables NET_RAW and SYS_ADMIN capabilities for my microservices deployment."

Tips & gotchas

Ensure your Kubernetes cluster version supports SecurityPolicy objects, as newer versions may have deprecated this in favor of PodSecurityPolicies or OPA Gatekeeper. Always test policies in a staging environment before applying them to production clusters to avoid accidental service disruption.