Checkov
Use Checkov to scan Terraform and infrastructure-as-code repositories for policy violations, explain findings, choose safe fixes, rerun scans, and prepare pull requests with remediations.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Checkov when an AI agent needs a reusable SKILL.md workflow for this job: Use Checkov to scan Terraform and infrastructure-as-code repositories for policy violations, explain findings, choose safe fixes, rerun scans, and prepare pull requests with remediations.
When not to use it
Skip Checkov when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/checkov # Save SKILL.md to ~/.claude/skills/checkov/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/checkov/SKILL.md. For a shared project, commit the folder at .claude/skills/checkov/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Checkov skill for this task: Confirm the repository path before scanning. Repository resources are usually mounted under /workspace/repos/<host>/<owner>/<repo>; use the session's resolved resource path instead of guessing. Confirm any required inputs or files before making changes.
What supports this recommendation?
82/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 92/100
- Practical detail
- 92/100
- Source evidence
- 56/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Checkov
Use this skill when the user asks to scan Terraform or infrastructure-as-code for security, compliance, or best-practice issues.
## Workflow
1. Confirm the repository path before scanning. Repository resources are usually mounted under `/workspace/repos/<host>/<owner>/<repo>`; use the session's resolved resource path instead of guessing. 2. Run Checkov from the repository root or the relevant Terraform subdirectory:
```bash checkov -d . --framework terraform --compact ```
3. For a machine-readable result that is easier to inspect and summarize, write JSON to a temporary file:
```bash checkov -d . --framework terraform -o json --output-file-path /tmp/checkov-results ```
4. Summarize the failed checks in plain language. Include the check ID, file, resource, and reason. 5. When the user asks for fixes, edit only the selected findings. Keep changes focused and preserve the existing Terraform style. 6. Validate after edits:
```bash terraform fmt -recursive terraform init -backend=false terraform validate checkov -d . --framework terraform --compact ```
7. If GitHub credentials are available, create a branch and draft pull request for the fix.
## Guardrails
- Do not run `terraform apply` unless the user explicitly asks for it. - Prefer `terraform init -backend=false` for validation so remote state is not touched. - Do not suppress Checkov findings unless the user asks for a suppression and the reason is documented in code. - If provider credentials are missing, still run static checks and explain which validation steps could not be completed.
Intended uses
- Confirm the repository path before scanning. Repository resources are usually mounted under /workspace/repos/<host>/<owner>/<repo>; use the session's resolved resource path instead of guessing.
- Run Checkov from the repository root or the relevant Terraform subdirectory:
- For a machine-readable result that is easier to inspect and summarize, write JSON to a temporary file:
- Summarize the failed checks in plain language. Include the check ID, file, resource, and reason.
- When the user asks for fixes, edit only the selected findings. Keep changes focused and preserve the existing Terraform style.
- Validate after edits:
- If GitHub credentials are available, create a branch and draft pull request for the fix.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.