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 avoids common Rego bugs: uses `x in collection` (not `x != collection[_]`) for negative membership, and uses sprintf with matching argument counts.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses `in` for membership check (not `!=` in a loop)",
"description": "Restricted name check uses `input.metadata.name in data.restricted_names` — not `some name in data.restricted_names; name != input.metadata.name` which is a not-equals-in-loop bug",
"max_score": 40
},
{
"name": "sprintf argument count matches format string",
"description": "All `sprintf` calls have the same number of `%v`/`%s` verbs as arguments in the array",
"max_score": 20
},
{
"name": "Checks for restricted name and missing annotation",
"description": "Separate deny rules for restricted namespace names and missing `owner` annotation",
"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