What problem does it solve?
When authoring compliance control files in ComplianceAsCode, rules often depend on XCCDF variables whose values must be selected. Manually tracking which variables each rule uses, reading their .var files, and choosing the correct option key is tedious and error-prone.
Core Features & Use Cases
- Automatic Variable Detection: Looks up rule dependencies in the build-generated rule_variable_mapping.json and deduplicates variables shared across multiple rules.
- Interactive Value Selection: Reads each variable's .var file options and prompts the author to pick a key, with CIS-suggested and default values clearly marked.
- Control File Ready Output: Returns var_name=key selections ready to be written inline into a control file's rules list.
- Use Case: After selecting rules like accounts_password_pam_minlen for a NIST control mapping on RHEL 9, run this skill to resolve var_password_pam_minlen and other dependencies, choosing values aligned with CIS recommendations.
Quick Start
Ask the assistant to resolve rule variables for product rhel9 and the rules accounts_password_pam_dcredit and accounts_tmout, optionally passing CIS variable suggestions.
