What problem does it solve? Policy templates define the YAML schema users fill in to set policy values, but poorly named keys and mismatches with the Rego rule's data.* paths cause silent evaluation failures and confusing user experiences. This Skill enforces consistent key syntax and schema alignment so templates work correctly at evaluation time. ## Core Features & Use Cases - Key Syntax Enforcement: Validates that every template key is alphanumeric with underscores only, never starts with a number, and uses underscore-separated words like vulnerability_count. - Readability Conventions: Guides template structure toward sentence-like, self-evident schemas (e.g., vulnerabilities.critical.maximum) instead of opaque flat keys. - Rego Schema Alignment: Ensures every template key maps to a data.* reference in the control's Rego rule, preventing undefined evaluation results. - Use Case: When authoring a new control that checks code coverage thresholds, use this Skill to design a template like coverage.overall.minimum and verify the paired Rego rule reads exactly that path before publishing. ## Quick Start Design a YAML policy template for a control that limits critical and high vulnerability counts, with keys that match the Rego rule's data paths.
