CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/policy-as-code-runner

Configures policy-as-code testing using OPA / Conftest / Cedar - authors policies in Rego (OPA's language), runs Conftest against Kubernetes manifests / Terraform plans / Dockerfiles / arbitrary structured data, integrates with CI for PR-time policy gates. Per OPA's docs: "an open source, general-purpose policy engine that unifies policy enforcement across the stack." Use to express + enforce custom policies (cost limits, tagging requirements, security baselines) that Checkov / tfsec / KICS don't cover.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thoroughly actionable, well-sequenced guide that would let Claude execute policy-as-code work directly. Its main weakness is structure: everything lives inline in one long file rather than being split into one-level-deep reference files.

Suggestions

Move the full Rego policy examples (k8s required_labels, terraform cost_center, dockerfile no_latest) into a references/ directory and keep only one representative inline example in SKILL.md.

Add an inline validate→fix→retry feedback loop in Step 8 (e.g., 'if opa test fails, fix the policy and re-run before proceeding to conftest') rather than relying on the anti-patterns table.

Trim the inline OPA docs quote and the 'deny rule pattern' restatement since the executable Rego already demonstrates the semantics.

DimensionReasoningScore

Conciseness

Mostly lean with executable code per step and minimal padding, but a few lines restate Rego semantics and an inline OPA docs quote that slightly over-explain what the code already shows.

4 / 5

Actionability

Fully executable, copy-paste-ready install commands, Rego policies, conftest invocations, CI YAML, and a Gatekeeper template covering the common k8s/Helm/Terraform/Dockerfile/test cases.

5 / 5

Workflow Clarity

A clear 9-step sequence with an `opa test` validation checkpoint before CI and an anti-patterns table covering failure modes, but error-recovery feedback loops are conveyed via the table rather than inline validate→fix→retry steps.

4 / 5

Progressive Disclosure

Well-organized into labeled sections, but with no bundle files the ~240-line body inlines multiple full Rego policies and CI/Gatekeeper blocks that would fit better in separate reference files; navigation is via external URLs only.

3 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-triggered description that clearly defines both capabilities and use conditions while staking out a distinct niche from built-in scanners. Minor room only on synonym/extension coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — authors Rego policies, runs Conftest against Kubernetes/Terraform/Dockerfile/structured data, integrates CI for PR-time gates, enforces cost limits/tagging/security baselines — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (configures testing, authors policies, runs Conftest, CI integration) and 'when' via the explicit 'Use to express + enforce custom policies ... that Checkov / tfsec / KICS don't cover' trigger clause.

5 / 5

Trigger Term Quality

Strong natural keywords (policy-as-code, Conftest, OPA, Kubernetes manifests, Terraform plans, Dockerfiles, CI, PR-time policy gates) that users would say, but a few synonyms/extensions are absent and Cedar appears without a trigger role.

4 / 5

Distinctiveness Conflict Risk

Clear custom-policy niche explicitly positioned against named sister scanners (Checkov/tfsec/KICS) and tied to specific engines (OPA/Conftest/Cedar), yielding minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents