K8S Security Policies
CheckedAutomates Kubernetes security policy enforcement based on rmyndharis best practices, reducing risk and ensuring compliance.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add rmyndharis/antigravity-skills --skill k8s-security-policies -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
rmyndharis
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.
Automated safety checks
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 rmyndharis/antigravity-skills at 3eff4af253.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 3eff4af253
- Scanned
- 3 files, 659 lines
About this skill
What it does
This skill allows AI agents to manage Kubernetes Security Policies. It can create, modify, and delete security policies within a Kubernetes cluster, ensuring that workloads adhere to defined access controls. The skill provides a declarative way to define network traffic rules for pods, enhancing the overall security posture of your applications.
When to use it
- Enforcing Network Segmentation: Implement strict network policies to isolate sensitive microservices from less-trusted components within your Kubernetes environment.
- Restricting Inbound/Outbound Traffic: Control which external services or internal pods can communicate with specific application deployments.
- Automating Security Policy Updates: Dynamically adjust security policies based on changes in application requirements or threat landscape.
- Compliance Auditing: Generate reports and documentation of existing Kubernetes security policies for regulatory compliance purposes.
Key capabilities
- Create Kubernetes Security Policies
- Modify existing Kubernetes Security Policies
- Delete Kubernetes Security Policies
Example prompts
- "Create a security policy that allows pods in the 'frontend' namespace to access only the database service on port 5432."
- "Update the existing security policy for the 'payment-service' to deny all ingress traffic from outside the cluster."
- “Show me all current Kubernetes Security Policies.”
Tips & gotchas
This skill requires appropriate Kubernetes credentials and access rights to manage security policies within a cluster. Ensure your AI agent has sufficient permissions before attempting to create or modify resources.