manage-profile

Creates and updates versioned compliance profile pairs for ComplianceAsCode products.

2.8k|823|Updated Apr 29, 2014
One-click install
npx skills add https://github.com/ComplianceAsCode/content --skill manage-profile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-profile
Source: https://github.com/ComplianceAsCode/content/tree/main/.claude/skills/manage-profile
Command: npx skills add https://github.com/ComplianceAsCode/content --skill manage-profile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing versioned security profiles in the ComplianceAsCode repository requires manually creating paired profile files, keeping extends references in sync, and deprecating old versions, which is error-prone when done by hand across multiple products.

Core Features & Use Cases

  • Create versioned profile pairs: Generates a versioned profile (e.g., cis-v1-7-0.profile) with selections and metadata plus an unversioned profile that extends it, for one or more products.
  • Update profile versions: Bumps an existing profile to a new version by copying selections, deprecating the previous versioned profile, and repointing the unversioned extends reference.
  • Control file validation: Checks that matching control files under controls/ list all target products before profile creation.
  • Use Case: When a new CIS benchmark version 1.8.0 is released for OpenShift, run the update action to create cis-v1-8-0.profile, deprecate cis-v1-7-0.profile, and repoint cis.profile in one guided flow.

Quick Start

Ask the assistant to create a new versioned profile, for example by saying: create a cis profile for ocp4 at version 1.7.0.

Frequently Asked Questions about manage-profile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new versioned profile in ComplianceAsCode?

Run the create action with the profile name, product, and version, such as create cis ocp4 1.7.0. This generates a versioned profile file with selections and metadata plus an unversioned profile that extends it under products/ocp4/profiles/.

How do I bump a ComplianceAsCode profile to a new version?

Use the update action with the profile name, product, and new version, such as update cis ocp4 1.8.0. It copies the current selections into a new versioned profile, marks the previous one as deprecated, and updates the unversioned profile's extends reference.

Can I create a profile for multiple products at once?

Yes, pass a comma-separated product list such as ocp4,rhcos4. Profile pairs are created or updated under each product's products/<product>/profiles/ directory, and the control file is checked to ensure it lists all target products.

What is the versioned and unversioned profile pattern?

The versioned profile (e.g., cis-v1-7-0.profile) holds the actual selections and metadata.version for a stable baseline. The unversioned profile (e.g., cis.profile) only extends the versioned one, so users referencing it always get the latest version.

What happens if the unversioned profile does not use extends?

The update action warns that the profile does not follow the versioning pattern and offers to convert it. This ensures all profiles consistently use the versioned plus unversioned extends structure.