rl-protect-skills

Creates or modifies rl-protect scanning profiles (rl-profile JSON). Use when the user wants to configure scan policy, set assessment severity levels, add governance allow/block rules, or apply policy overrides.

Converts an rl-protect JSON report (rl-protect.report.json) into a structured Markdown document. Use when the user wants to generate a report file, export scan findings to Markdown, create a document to review or share, or plan dependency version updates.

Interprets rl-protect JSON reports (rl-protect.report.json). Use when the user asks about vulnerabilities, malware, indicators, policy violations, overrides, governance, dependency trees, or behavior diffs, or when a scan saved a report and the user wants to dig deeper into findings.

Configures the rl-protect tool by connecting it to a Spectra Assure Community (free) or Spectra Assure Portal account (enterprise). Use when the user wants to set up rl-protect, add or update a server connection, or provide an API token.

Installs the rl-protect CLI from PyPI and configures it for first use. Use when the user wants to set up rl-protect, when rl-protect is not found on PATH, or when the user asks how to get started with Spectra Assure supply chain scanning.

Supply chain security gate. MUST be invoked BEFORE running any install command (npm install, pip install, gem install), before editing manifest/lock files (package.json, requirements.txt, pyproject.toml, Gemfile), before writing imports/requires for packages not already in the project, and before recommending packages. Also invoke when updating or downgrading package versions. This skill scans packages with rl-protect and gates the action on the result. Never skip — invoke proactively even if the user did not ask for a scan.