comply-scan

Scan individual HIPAA/NIST 800-53 controls and record PASS/FAIL results in SQLite.

10|5|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/aanishs/em-dash --skill comply-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comply-scan
Source: https://github.com/aanishs/em-dash/tree/main/skills/comply-scan
Command: npx skills add https://github.com/aanishs/em-dash --skill comply-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated HIPAA/NIST 800-53 control verification by scanning one control at a time and recording results for audit readiness.

Core Features & Use Cases

  • One-control-at-a-time automated scanning against NIST 800-53 controls using multiple tools
  • Runs em-dash checks, Prowler, and Checkov when available and stores results in SQLite for traceability
  • Generates an actionable audit trail and assists remediation by surfacing PASS/FAIL status per control

Quick Start

Run the comply-scan workflow to start scanning the next pending control.

Frequently Asked Questions about comply-scan

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

FAQPage Schema
How do I automate HIPAA control scanning and generate audit-ready evidence?

Automated HIPAA control scanning verifies NIST 800-53 controls one at a time using available tools like Prowler and Checkov, storing PASS/FAIL results in SQLite to generate audit-ready evidence and remediation guidance.

Does HIPAA compliance scanning work without Prowler or Checkov installed?

HIPAA compliance scanning handles missing tools gracefully by running em-dash checks and any available tools, still producing per-control reports even if Prowler or Checkov are not installed in the environment.

What is the best way to track NIST 800-53 audit trail results over time?

Tracking NIST 800-53 audit trail results is handled by recording deterministic per-control PASS/FAIL outcomes in a SQLite database, ensuring traceability and audit readiness across multiple scanning sessions.

Can I use automated compliance scanning for infrastructure and code simultaneously?

Automated compliance scanning applies to both infrastructure and code, coordinating tools like Checkov and Prowler to surface NIST 800-53 control verification results for cloud configurations and source code repositories.

How do I get guided remediation actions after a failed HIPAA control scan?

Guided remediation actions are delivered alongside per-control PASS/FAIL reports after a HIPAA control scan, providing actionable steps to address failed NIST 800-53 controls and improve audit readiness.

What are the limitations of running one-control-at-a-time compliance scans?

One-control-at-a-time compliance scanning produces deterministic per-control results but requires sequential execution, meaning full NIST 800-53 audit readiness requires running the workflow across all pending controls individually.