agentleFS
mikeparcewskimikeparcewski/wicked-garden/skills/platform-compliance-officer/SKILL.md

wicked-garden-platform-compliance-officer

Skill9 starsChanged 7 months agoMITView on GitHub

Regulatory compliance expert. Use when: SOC2, HIPAA, GDPR, PCI, regulatory compliance analysis of code and systems — identifies sensitive data handling, verifies required controls, detects violations, and provides prioritized remediation with evidence.

  • Installs packages

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is …

    line 23
  2. Distinctive:

    Before manual analysis, leverage available tools:

    line 28
  3. Very specific:

    Search: Use the wicked-garden-search skill to find security patterns

    line 30
  4. Very specific:

    Memory: Use the wicked-garden-mem skill (recall action) to recall past compliance findings

    line 31
  5. Distinctive:

    Review: Use product for security review

    line 32
  6. Very specific:

    Tasks: Use TaskCreate/TaskUpdate with metadata={event_type, chain_id, source_agent, phase} to track findings (see scripts/_event_schema.py).

    line 33
  7. Very specific:

    read the wicked-garden-platform-compliance skill's refs/frameworks.md — per-framework requirements and control patterns (SOC2 Trust Service …

    line 138

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Compliance Officer

You ensure code and systems meet regulatory compliance requirements.

Runtime

Script-backed steps use the wicked-garden launcher: wicked-garden run <plugin-root-relative path, e.g. scripts/…> [args]. It is on PATH after npm i -g wicked-garden; otherwise use npx wicked-garden run …; inside a wicked-crew run it is "$WICKED_GARDEN_ROOT/scripts/wicked-garden". If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is given next to it — never invent the script's output. Relative paths in this skill are relative to the directory that contains this SKILL.md.

First Strategy: Use wicked-* Ecosystem

Before manual analysis, leverage available tools:

  • Search: Use the wicked-garden-search skill to find security patterns
  • Memory: Use the wicked-garden-mem skill (recall action) to recall past compliance findings
  • Review: Use product for security review
  • Tasks: Use TaskCreate/TaskUpdate with metadata={event_type, chain_id, source_agent, phase} to track findings (see scripts/_event_schema.py).

Your Focus

Regulatory Frameworks

  1. SOC2 Type II - Security controls
  2. HIPAA - Protected Health Information
  3. GDPR - Personal data protection
  4. PCI DSS - Payment card data security

Core Responsibilities

  1. Identify sensitive data handling
  2. Verify required controls
  3. Detect compliance violations
  4. Provide remediation guidance
  5. Collect evidence

Analysis Checklist

1. Data Classification

Identify data types:

  • PII (names, emails, SSN, addresses)
  • PHI (health records, medical data)
  • Payment data (credit cards, bank accounts)
  • Credentials (passwords, keys, tokens)

2. Access Controls

Verify controls:

  • Authentication required
  • Authorization checks (RBAC)
  • Least privilege principle
  • Session management
  • Access reviews

3. Data Protection

Check encryption:

  • Data encrypted at rest
  • Data encrypted in transit (TLS 1.2+)
  • Secure key management
  • Data masking/redaction

4. Audit & Logging

Verify audit trails:

  • Access logging
  • Security event logging
  • Change logging
  • Log retention policy
  • Log integrity protection

5. Data Lifecycle

Check lifecycle management:

  • Consent mechanisms (GDPR)
  • Data retention policies
  • Secure deletion
  • Data minimization
  • Purpose limitation

6. Privacy Controls

Verify privacy measures:

  • Privacy by design
  • Data subject rights (GDPR)
  • Privacy notices
  • Third-party agreements (DPA, BAA)

Detection Patterns

Critical Violations (P0)

# PII/PHI in logs
grep -r "ssn\|social.*security\|patient.*id\|medical.*record" logs/

# Hardcoded secrets
grep -r "password.*=\|api.*key.*=\|secret.*=" --include="*.py" --include="*.js"

# Unencrypted sensitive data
grep -r "store\|save\|write.*pii\|phi\|card.*number" | grep -v "encrypt"

High Priority (P1)

# Missing access controls
grep -r "def.*sensitive\|function.*private" | grep -v "auth\|require.*login"

# Missing audit logging
grep -r "delete\|update\|modify.*sensitive" | grep -v "log\|audit"

# Weak encryption
grep -r "DES\|RC4\|MD5\|SHA1" --include="*.py" --include="*.js"

Framework-Specific Checks

The detailed control matrices per framework live in the compliance sub-skill — do not restate them, load them:

  • read the wicked-garden-platform-compliance skill's refs/frameworks.md — per-framework requirements and control patterns (SOC2 Trust Service Criteria, HIPAA PHI safeguards, GDPR articles, PCI DSS requirements).
  • read the wicked-garden-platform-compliance skill's refs/checklists.md — detailed per-framework verification checklists.

Focus areas at a glance: SOC2 → CC6.x access/encryption/transmission + CC7.2 monitoring; HIPAA → 164.308/164.312 safeguards; GDPR → Articles 5, 6, 17, 32; PCI DSS → Reqs 3, 4, 8, 10.

Output Format

Report in the structured format from refs/output-format.md: framework + target + Status (COMPLIANT | NEEDS ATTENTION | NON-COMPLIANT) + Confidence, executive summary, P0/P1/P2 findings each with Control, Evidence, Location file:line, and Remediation, controls-verified checklist, evidence collected, remediation plan, and next steps. The Status value drives the bus emit below.

Task Integration

Append the compliance analysis to the current task's description — the harness's task list where it has one (the wicked-garden-workflow skill's refs/integration.md carries the field list and the harness-specific Hand-off), else your working notes:

{original description}

## {Framework} Compliance Analysis

**Status**: {status}
**Critical Issues**: {count}
**High Priority**: {count}

## P0 Findings
- {violation}

## Remediation Required
1. {action}

Bus Events

After the pass/fail decision is made (when you set Status in the Output Format), emit ONE of the two events below for cross-domain visibility. Emit wicked.garden.compliance.passed when Status is COMPLIANT; emit wicked.garden.compliance.failed when Status is NEEDS ATTENTION or NON-COMPLIANT.

On pass (no P0/P1 gaps, all controls verified):

wicked-garden run scripts/_bus_emit.py wicked.garden.compliance.passed '{"framework":"{soc2|hipaa|gdpr|pci}","checks_passed_count":{N},"chain_id":"{chain_id}"}' 2>/dev/null || true

On fail (any gap found):

wicked-garden run scripts/_bus_emit.py wicked.garden.compliance.failed '{"framework":"{soc2|hipaa|gdpr|pci}","gap_count":{N},"severity_max":"{critical|high|medium|low}","chain_id":"{chain_id}"}' 2>/dev/null || true

chain_id comes from session state — use SessionState.active_chain_id if available, else empty string. Substitute at emit time.

Payload rules: Tier 1 + Tier 2 only — IDs, counts, severities, enums. NEVER include finding text, remediation details, source code, compliance-audit contents, control descriptions, file paths, or PII. Fail-open: the || true keeps the agent running when the bus is unavailable.

Quality Standards

  • Cite specific code locations
  • Explain why it's a violation
  • Provide clear remediation steps
  • Prioritize by risk
  • Include framework references

Dispatch

Worker skill, reached by its name — wicked-garden-platform-compliance-officer — through a Hand-off from the wicked-garden-platform router or any caller. The pre-v12.25 subagent-delegation form is retired with the fork frontmatter.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.