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

wicked-garden-platform-compliance

Skill9 starsChanged 7 months agoMITView on GitHub

Use when checking code or architecture against a regulatory framework (SOC2, HIPAA, GDPR, PCI) or translating a policy document into actionable controls — detects violations and provides prioritized remediation guidance. NOT for gathering audit evidence artifacts (use platform/audit).

  • Installs packages

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    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. Very specific:

    Read refs/compliance.md (relative to this skill's base directory) — data-classification scan commands, per-framework control matrix …

    line 49

≈ “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 Skill

Analyze code and systems for regulatory compliance.

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.

When to Use

  • Code handles sensitive data (PII, PHI, payment data)
  • Pre-deployment compliance verification
  • User mentions regulatory frameworks
  • User says "is this compliant", "compliance check", "regulatory requirements"

Supported Frameworks

FrameworkFocusKey Requirements
SOC2Security, AvailabilityAccess controls, encryption, logging, monitoring
HIPAAProtected Health InfoPHI safeguards, access logs, encryption, BAA
GDPRPersonal DataConsent, minimization, deletion, DPO
PCI DSSPayment Card DataEncryption, network segmentation, access control

See refs/frameworks.md for detailed framework requirements.

Run it inline (no dispatch)

Invoked as <framework> [path]:

  1. Parse args: <framework> [path] (framework = soc2|hipaa|gdpr|pci).
  2. Read refs/compliance.md (relative to this skill's base directory) — data-classification scan commands, per-framework control matrix (SOC2/HIPAA/GDPR/PCI), gap checklist, bus emit, output format.
  3. For detailed per-framework checklists: Read refs/checklists.md. For framework-specific patterns: refs/frameworks.md.
  4. Apply the rubric directly: scan for sensitive data, verify each control, classify gaps P0/P1/P2, emit the bus event, and produce the compliance assessment report.

Analysis Process

1. Identify Sensitive Data

Scan for:

  • PII: Names, emails, SSN, addresses
  • PHI: Medical records, health data
  • Payment: Credit cards, bank accounts
  • Credentials: Passwords, API keys

2. Verify Controls

Access Control:

  • Authentication required
  • Authorization checks (RBAC)
  • Least privilege

Data Protection:

  • Encryption at rest (AES-256)
  • Encryption in transit (TLS 1.2+)
  • Secure key management

Logging & Monitoring:

  • Access logs
  • Audit trails
  • Security events
  • Log retention

Data Lifecycle:

  • Consent mechanisms (GDPR)
  • Retention policies
  • Secure deletion
  • Data minimization

3. Detect Violations

Common issues:

  • PII/PHI in logs or errors
  • Hardcoded secrets
  • Missing encryption
  • Insufficient access controls
  • Missing audit trails

See refs/checklists.md for detailed verification checklists.

4. Generate Report

Output:

  • Status: COMPLIANT / NEEDS ATTENTION / NON-COMPLIANT
  • Findings: Violations by priority (P0, P1, P2)
  • Evidence: Code references
  • Remediation: Required fixes

Integration

With wicked-crew

Auto-triggered at phase gates

With the harness's task list

Append [compliance] {framework}: {status} to the task 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.

With the memory layer (wicked-estate)

Hand-off — open the wicked-garden-mem skill and run its recall action with compliance {framework} as the query; on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog and carry it out inline, then continue here.

With the platform domain skill

For an ad hoc vulnerability scan of the same target, run the security action of skills/platform/SKILL.md (real scanners + triage).

Output Format

## Compliance Analysis: {Framework}

**Target**: {scope}
**Status**: {COMPLIANT|NEEDS ATTENTION|NON-COMPLIANT}
**Framework**: {SOC2|HIPAA|GDPR|PCI}

### Critical (P0)
- {violation} - {file}:{line}
  Remediation: {fix}

### High Priority (P1)
- {gap} - {file}:{line}
  Recommendation: {guidance}

### Medium Priority (P2)
- {improvement} - {suggestion}

### Controls Verified
- [x] Encryption at rest
- [ ] Data retention policy

### Next Steps
{Recommended actions}

External Integration Discovery

Compliance checking can leverage available integrations by capability:

CapabilityDiscovery PatternsProvides
Security scanningsnyk, semgrep, sastVulnerability detection
Secretsvault, secretsCredential management audit
SBOMtrivy, sbom, cyclonedxSupply chain compliance

Discover available integrations via capability detection. When none are available, fall back to manual analysis against the control checklist above.

Quality Standards

Good analysis:

  • Specific code references
  • Clear violation descriptions
  • Actionable remediation
  • Prioritized by risk

Bad analysis:

  • Generic checklists
  • No code evidence
  • Vague recommendations

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.