improve-subimage-coverage

To find missing SubImage coverage, this Skill scans your Terraform, CLI context, and git remotes to detect active cloud and SaaS providers, then compares them against enabled SubImage modules to pinpoint security coverage gaps.

Auditing security findings coverage across mixed IaC environments involves normalizing detected provider signals and comparing them with enabled modules to filter active security rules and rank the most actionable tagged findings.

Yes, SubImage coverage auditing works with repositories that mix Terraform, local CLI context, and git remotes, scanning these combined signals to accurately infer which platforms are actually in use.

To prioritize security findings after onboarding a new cloud account, this Skill groups active rules by tag, ranks the most actionable issues, and highlights representative affected resources to justify connecting providers.

You should run a SubImage coverage gap analysis during scheduled security reviews or immediately after onboarding a new cloud account to quickly identify which AWS, GCP, Azure, GitHub, or Kubernetes wiring is missing.

Your SubImage module comparison shows missing provider wiring because the Skill detects active cloud and SaaS platforms from your repository signals that have not yet been normalized and enabled within your SubImage configuration.