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 implements per-user rate limiting using a rule with a `default` fallback value (e.g. `default user_limit := 10`) rather than hardcoding the fallback in conditionals.",
"type": "weighted_checklist",
"checklist": [
{
"name": "import rego.v1",
"description": "The policy file includes `import rego.v1`",
"max_score": 10
},
{
"name": "Default rule value for fallback limit",
"description": "The policy declares a default fallback limit using `default <rule_name> := <value>` (e.g. `default user_limit := 10`) — the same pattern as `default allow := false`, not using `else :=` or `object.get`",
"max_score": 40
},
{
"name": "Per-tier limit lookup",
"description": "The policy defines separate rule heads (or conditions) that return tier-specific limits (e.g. 1000 for premium, 100 for standard) by reading from `data.user_tiers`",
"max_score": 25
},
{
"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