Iac Scan Kube Linter
CheckedThis skill scans Kubernetes configurations using IAC linters to identify potential issues and vulnerabilities for improved security & 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 vchirrav-eng/owasp-secure-coding-md --skill iac-scan-kube-linter -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
vchirrav
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 vchirrav/owasp-secure-coding-md at a0f04031cb.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- a0f04031cb
- Manifest
- iac-scan-kube-linter/SKILL.md
- Scanned
- 1 file, 50 lines
About this skill
What it does
This skill, vchirrav-iac-scan-kube-linter, performs static analysis of Infrastructure as Code (IaC) files and Kubernetes manifests. It identifies potential security vulnerabilities and policy violations based on the OWASP Secure Coding Practices. The tool helps ensure that infrastructure deployments adhere to secure coding standards and best practices, reducing risk exposure.
When to use it
- Pre-deployment checks: Integrate into CI/CD pipelines to scan IaC code before deployment.
- Security audits: Regularly audit existing infrastructure configurations for security flaws.
- Policy enforcement: Verify that deployments comply with organizational security policies.
- New project setup: Ensure new projects start with secure infrastructure foundations.
Key capabilities
- OWASP Secure Coding Practices compliance checks
- Static analysis of IaC files (e.g., Terraform, CloudFormation)
- Kubernetes manifest scanning
- Vulnerability identification and reporting
Example prompts
- "Scan this Terraform file for security vulnerabilities: [file content]"
- "Analyze this Kubernetes YAML manifest against OWASP best practices."
- "Check this IaC code for policy violations."
Tips & gotchas
- The skill requires access to the IaC files or Kubernetes manifests being analyzed.
- Results should be interpreted in context; false positives may occur and require manual review.