From compliance-pilot
Displays compliance posture summary from findings JSON files: stats by status, severity, service, SOC2/HIPAA frameworks. Supports --framework filter. Use after /scan.
How this skill is triggered — by the user, by Claude, or both
Slash command
/compliance-pilot:postureThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Show a quick compliance posture summary. Read-only — does not spawn subagents.
Show a quick compliance posture summary. Read-only — does not spawn subagents.
Do NOT use the Agent tool. Handle this directly.
Use Glob to find all .compliance/findings/FINDING-*.json files, then Read each one.
If no findings exist, report:
No findings found. Run /scan first to assess your AWS account.
Count findings by:
source.servicecompliance[].frameworkCalculate compliance percentage:
compliance% = (verified + skipped) / total * 100
# Compliance Posture
Last scan: {most recent scanId from findings}
Total findings: {n}
## By Status
| Status | Count |
|--------|-------|
| Open | {n} |
| In Progress | {n} |
| Remediated | {n} |
| Verified | {n} |
| Skipped | {n} |
## By Severity
| Severity | Open | Fixed | Total |
|----------|------|-------|-------|
| Critical | {n} | {n} | {n} |
| High | {n} | {n} | {n} |
| Medium | {n} | {n} | {n} |
| Low | {n} | {n} | {n} |
## By Framework
| Framework | Controls Hit | Findings | Verified | Score |
|-----------|-------------|----------|----------|-------|
| SOC 2 | {n unique controls} | {n} | {n} | {%} |
| HIPAA | {n unique controls} | {n} | {n} | {%} |
## By Service
| Service | Open | Fixed | Total |
|---------|------|-------|-------|
| s3 | {n} | {n} | {n} |
| iam | {n} | {n} | {n} |
| ... | ... | ... | ... |
## Top Open Issues
{List top 5 open findings by severity, with finding ID, check title, and resource}
If $ARGUMENTS contains --framework soc2 or --framework hipaa:
npx claudepluginhub prajapatimehul/comp-agent --plugin compliance-pilotAnalyzes compliance gaps across frameworks (PCI DSS, SOC 2, CIS, NIST) — ranks failing controls by impact, identifies quick wins, and generates remediation plans. Use when asked about compliance status or failures.
Makes cloud accounts compliant with security/industry frameworks via iterative Prowler Cloud setup, reporting, and remediation. Handles provider configuration, framework selection, and step-by-step compliance checking.
Maps VulnScout security findings to PCI-DSS v4.0, HIPAA Security Rule, and SOC 2 requirements to assess regulatory impact and prioritize remediation.