agentsclimarketplace
Sign in

Compliance audit

Skill opsera-agents/opsera-devsecops/skills/compliance-audit

Evidence-based compliance auditing for SOC2, HIPAA, PCI-DSS, and ISO 27001 frameworks. Use when the user asks about compliance readiness, audit preparation, control gap analysis, certification requirements, or framework-specific compliance assessments.From its SKILL.md

Install
npx -y skills add opsera-agents/opsera-devsecops --skill compliance-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, as published. Nobody here has run it

Compliance Audit

Perform an evidence-based compliance audit using the mcp__opsera__compliance-audit tool.

When to Trigger

  • User asks for "SOC2 audit", "HIPAA compliance", "PCI-DSS assessment", or "ISO 27001 certification"
  • User asks "are we compliant?" or "what do we need for [framework]?"
  • User needs audit readiness assessment or compliance gap analysis
  • User wants to map security controls to compliance frameworks

Execution Steps

  1. Collect inputs: Determine the compliance framework and scope:
    • framework: soc2, hipaa, pci-dss, iso27001, or all (ask if not specified)
    • scope: infrastructure, application, or full (default: full)
    • output_format: executive, detailed, audit-ready, or html (recommend html for rich visualization)
    • evidence_collection: automated, manual, or hybrid (default: hybrid)
  2. Execute Pass 1 (Compliance Scan): Call mcp__opsera__compliance-audit with inputs. Collects evidence, inventories controls, identifies gap signals.
  3. Execute Pass 2 (Control Deep Dive): Continue phased execution with _execution_id and _phase_result. AI investigates gaps and maps to frameworks.
  4. Execute Pass 3 (Compliance Report): Generate the audit-ready report with scores, findings, and remediation roadmap.
  5. Report telemetry: Call mcp__opsera__report-telemetry with:
    • toolName: compliance-audit
    • status: success/partial/failed
    • target: the repository or infrastructure audited
    • score: the compliance score (0-100)
    • scoreLabel: Elite/High/Medium/Low
    • Finding counts by severity
  6. Present results: Lead with the compliance score, then critical gaps, then the remediation roadmap. Highlight quick wins vs. long-term fixes.

Important

  • ALWAYS report telemetry after audit completion
  • Recommend HTML format for stakeholder-friendly reports
  • Suggest follow-up security scan if technical vulnerabilities are found

Keep looking

Skills are one crate of 626,474. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.