Contract
- Input: system description, applicable frameworks, existing policies and evidence.
- Output: gap analysis + evidence pack + remediation roadmap + control matrix.
- Scope: assesses readiness and documents evidence; does not perform certification or legal attestation.
- Rule: assesses readiness and documents evidence; does not perform certification or legal attestation.
- Rule: documented standards override defaults; explicit project rules take precedence.
- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.
Provenance
| Question |
Answer |
| What is the source of truth? |
The user's request, originating spec/issue, and the skill's declared outputs |
| What is in scope? |
Work covered by the skill's acceptance criteria and completion rules |
| What is explicitly out of scope? |
Files, behaviors, and decisions outside the skill's declared boundary |
| Who or what consumes this artifact afterward? |
The next skill in the workflow or the user |
| What evidence proves it is done? |
Completion criteria met, artifact saved, validation passed |
| What risk remains? |
Subjective judgment calls, missing context, or external dependency failures |
Artifact
Emit ComplianceArtifact as both:
- JSON:
.agents/skills/platform/artifacts/compliance/{identifier}.json
- Markdown view: same filename with
.md extension
Compliance
Assess compliance posture across SOC2, ISO27001, GDPR, HIPAA, and PCI DSS — with explicit control mapping, evidence collection, gap analysis, and remediation planning.
Process
1. Frameworks and scope
- Which frameworks apply? (SOC2 Type I/II, ISO27001:2022, GDPR, HIPAA, PCI DSS v4.0)
- What is in scope? (systems, data types, cloud regions, subsidiaries, vendors)
- What is out of scope? (non-regulated products, legacy systems being decommissioned)
Completion criterion: scope and framework list saved.
2. Control mapping
Map each framework's required controls to current controls:
- SOC2: CC1–CC7 (Control Environment through Encryption, Incident Response)
- ISO27001: Annex A controls (A.5–A.8: organisational, people, physical, technological)
- GDPR: Art. 5 (principles), Art. 24 (responsibility), Art. 32 (security of processing), Art. 33–34 (breach notification)
- HIPAA: Administrative (Security Rule), Physical, Technical safeguards
- PCI DSS: 12 requirements (build/maintain secure network, protect cardholder data, vulnerability management, access control, monitoring, testing)
Completion criterion: control matrix (framework control → current control → status) saved.
3. Evidence collection
For each control, collect evidence:
- Policies and procedures (approved, reviewed, versioned)
- Configuration snapshots (encryption settings, access controls, network segmentation)
- Logs (access, authentication, change, audit)
- Process records (onboarding/offboarding, vendor reviews, risk assessments, training)
- Test results (vulnerability scans, penetration tests, DR drills)
- Third-party attestations (vendor SOC2, BAA, DPA)
Completion criterion: evidence indexed by control; gaps in evidence flagged.
4. Gap analysis
For each control:
- Present: control exists, evidence is sufficient → pass.
- Partial: control exists but evidence is incomplete or implementation is inconsistent → partial.
- Missing: no control or no evidence → gap.
For each gap: root cause (no policy, no enforcement, no evidence), risk (likelihood × impact), and regulatory consequence (fine, certification loss, audit finding).
Completion criterion: gap register with severity and regulatory impact saved.
5. Remediation planning
For each gap:
- Remediation action (policy, tool, process, training)
- Owner (team or individual)
- Effort (low / medium / high)
- Timeline (sprint, quarter)
- Verification method (re-audit, scan, attestation, self-assessment)
- Dependencies (budget, vendor, legal review)
Prioritise by: regulatory deadline × risk × effort. Quick wins first (high impact, low effort).
Completion criterion: remediation roadmap with owners and milestones saved.
6. Continuous compliance
Design ongoing monitoring:
- Automated checks (configuration drift, policy violations, unpatched CVEs)
- Periodic evidence refresh (quarterly access reviews, annual policy review)
- Change management (new services assessed before production)
- Incident response integration (breach timelines aligned with notification requirements)
- Training and awareness cadence
Completion criterion: continuous compliance plan saved.
7. Audit readiness package
Assemble final package:
- Executive summary (posture, critical gaps, timeline to readiness)
- Control matrix with evidence links
- Gap register with remediation status
- Policies and procedures repository
- Evidence pack (organised by framework and control)
- Open items and escalation paths
Completion criterion: audit-ready package saved and reviewed.
Rules
- Rule: map every control to a specific piece of evidence; do not accept verbal assurances as evidence.
- Rule: treat evidence as immutable once collected; version and timestamp all artifacts.
- Rule: classify gaps by regulatory severity (reportable vs. internal) and timeline (immediate vs. planned).
- Rule: assign a single owner to every remediation item; no unowned items in the roadmap.
- Rule: separate "control exists but undocumented" from "control does not exist" — they require different remediation.
- Rule: verify remediation effectiveness with objective evidence (re-scan, re-test, re-attest), not self-declaration alone.
Completion
- the skill's completion criteria are explicitly checked
- the artifact is saved and validated
- any blockers or skipped validations are documented
- the next consumer is identified or the work is handed off
@include .agents/skills/platform/contract-base.xml
1---2name: "compliance"3category: "sec"4maturity: "stable"5version: "1"6description: "Compliance (SOC2, ISO27001, GDPR, HIPAA, PCI DSS, audits, evidence, remediation)"7license: "MIT"8capabilities:9 - apply compliance methods within explicit sec boundaries10 - analyze compliance (soc2, iso27001, gdpr, hipaa, pci dss, audits, evidence, remediation) with assumptions, constraints, and failure modes11 - produce and validate a sec artifact with evidence, decisions, and next steps12outputs: "gap analysis + evidence pack + remediation roadmap + control matrix."13sideEffects: []14dependencies: []15stopCondition: "Gap analysis complete; evidence pack assembled; remediation roadmap accepted."16risk: "medium"17trustTier: "3"18maxIterations: "6"19promptVersion: "2.0"20artifactType: "sec"21modelTier: "reasoning"22evaluators: ["behavioral", "regression"]23fixturesPath: .agents/skills/platform/fixtures/behavioral/compliance.json24diataxis: "how-to"25tags: ["sec"]26compatibility: []27approvalRequired: "true"28approvalFor: []29metadata:30 source: https://skillmd.com/skills/quantumquirkxyz/compliance31---3233## Contract3435- Input: system description, applicable frameworks, existing policies and evidence.36- Output: gap analysis + evidence pack + remediation roadmap + control matrix.37- Scope: assesses readiness and documents evidence; does not perform certification or legal attestation.38- Rule: assesses readiness and documents evidence; does not perform certification or legal attestation.39- Rule: documented standards override defaults; explicit project rules take precedence.40- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.4142## Provenance4344| Question | Answer |45|---|---|46| What is the source of truth? | The user's request, originating spec/issue, and the skill's declared outputs |47| What is in scope? | Work covered by the skill's acceptance criteria and completion rules |48| What is explicitly out of scope? | Files, behaviors, and decisions outside the skill's declared boundary |49| Who or what consumes this artifact afterward? | The next skill in the workflow or the user |50| What evidence proves it is done? | Completion criteria met, artifact saved, validation passed |51| What risk remains? | Subjective judgment calls, missing context, or external dependency failures525354## Artifact5556Emit `ComplianceArtifact` as both:57- JSON: `.agents/skills/platform/artifacts/compliance/{identifier}.json`58- Markdown view: same filename with `.md` extension596061# 62# 63# Compliance6465Assess **compliance posture** across SOC2, ISO27001, GDPR, HIPAA, and PCI DSS — with explicit control mapping, evidence collection, gap analysis, and remediation planning.6667## Process6869### 1. Frameworks and scope70- Which frameworks apply? (SOC2 Type I/II, ISO27001:2022, GDPR, HIPAA, PCI DSS v4.0)71- What is in scope? (systems, data types, cloud regions, subsidiaries, vendors)72- What is out of scope? (non-regulated products, legacy systems being decommissioned)7374**Completion criterion:** scope and framework list saved.7576### 2. Control mapping77Map each framework's required controls to current controls:78- SOC2: CC1–CC7 (Control Environment through Encryption, Incident Response)79- ISO27001: Annex A controls (A.5–A.8: organisational, people, physical, technological)80- GDPR: Art. 5 (principles), Art. 24 (responsibility), Art. 32 (security of processing), Art. 33–34 (breach notification)81- HIPAA: Administrative (Security Rule), Physical, Technical safeguards82- PCI DSS: 12 requirements (build/maintain secure network, protect cardholder data, vulnerability management, access control, monitoring, testing)8384**Completion criterion:** control matrix (framework control → current control → status) saved.8586### 3. Evidence collection87For each control, collect evidence:88- Policies and procedures (approved, reviewed, versioned)89- Configuration snapshots (encryption settings, access controls, network segmentation)90- Logs (access, authentication, change, audit)91- Process records (onboarding/offboarding, vendor reviews, risk assessments, training)92- Test results (vulnerability scans, penetration tests, DR drills)93- Third-party attestations (vendor SOC2, BAA, DPA)9495**Completion criterion:** evidence indexed by control; gaps in evidence flagged.9697### 4. Gap analysis98For each control:99- **Present:** control exists, evidence is sufficient → pass.100- **Partial:** control exists but evidence is incomplete or implementation is inconsistent → partial.101- **Missing:** no control or no evidence → gap.102103For each gap: root cause (no policy, no enforcement, no evidence), risk (likelihood × impact), and regulatory consequence (fine, certification loss, audit finding).104105**Completion criterion:** gap register with severity and regulatory impact saved.106107### 5. Remediation planning108For each gap:109- Remediation action (policy, tool, process, training)110- Owner (team or individual)111- Effort (low / medium / high)112- Timeline (sprint, quarter)113- Verification method (re-audit, scan, attestation, self-assessment)114- Dependencies (budget, vendor, legal review)115116Prioritise by: regulatory deadline × risk × effort. Quick wins first (high impact, low effort).117118**Completion criterion:** remediation roadmap with owners and milestones saved.119120### 6. Continuous compliance121Design ongoing monitoring:122- Automated checks (configuration drift, policy violations, unpatched CVEs)123- Periodic evidence refresh (quarterly access reviews, annual policy review)124- Change management (new services assessed before production)125- Incident response integration (breach timelines aligned with notification requirements)126- Training and awareness cadence127128**Completion criterion:** continuous compliance plan saved.129130### 7. Audit readiness package131Assemble final package:132- Executive summary (posture, critical gaps, timeline to readiness)133- Control matrix with evidence links134- Gap register with remediation status135- Policies and procedures repository136- Evidence pack (organised by framework and control)137- Open items and escalation paths138139**Completion criterion:** audit-ready package saved and reviewed.140141## Rules142143- Rule: map every control to a specific piece of evidence; do not accept verbal assurances as evidence.144- Rule: treat evidence as immutable once collected; version and timestamp all artifacts.145- Rule: classify gaps by regulatory severity (reportable vs. internal) and timeline (immediate vs. planned).146- Rule: assign a single owner to every remediation item; no unowned items in the roadmap.147- Rule: separate "control exists but undocumented" from "control does not exist" — they require different remediation.148- Rule: verify remediation effectiveness with objective evidence (re-scan, re-test, re-attest), not self-declaration alone.149150## Completion151152- the skill's completion criteria are explicitly checked153- the artifact is saved and validated154- any blockers or skipped validations are documented155- the next consumer is identified or the work is handed off156---157@include .agents/skills/platform/contract-base.xml