Rego is the declarative policy language used by Open Policy Agent (OPA). This tile covers writing and testing Rego policies for Kubernetes admission control, Terraform and infrastructure-as-code plan validation, Docker container authorization, HTTP API authorization, RBAC and role-based access control, data filtering, metadata annotations with opa inspect, and OPA policy testing with opa test.
99
Quality
Pending
Does it follow best practices?
Impact
99%
1.19xAverage score across 31 eval scenarios
Pending
The risk profile of this skill
{
"context": "Evaluates whether the agent uses `some x in collection` for iteration (prefer-some-in-iteration Regal rule) rather than the old bracket notation `x := collection[_]`.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses `some ... in` for iteration",
"description": "The policy iterates over containers using `some container in ...containers` (or equivalent `some x in` form) — not `container := ...containers[_]` or `containers[_]` bare bracket notation",
"max_score": 40
},
{
"name": "Checks each container image against approved registry",
"description": "The deny rule checks each container's image starts with `registry.example.com/` using `startswith` or string prefix matching",
"max_score": 20
},
{
"name": "deny contains msg pattern",
"description": "The policy uses `deny contains msg if { ... }` to collect violations, including the container name and image in the message",
"max_score": 15
},
{
"name": "Tests pass",
"description": "All tests pass when running `opa test . -v`",
"max_score": 25
}
]
}docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31