Compliance tracking
Skill w95/awesome-claude-corporate-skills/06-legal-compliance/compliance-tracking
Track compliance requirements and audit readiness. Trigger with "compliance", "audit prep", "SOC 2", "ISO 27001", "GDPR", "regulatory requirement", or when the user needs help tracking, preparing for, or documenting compliance activities.From its SKILL.md
npx -y skills add w95/awesome-claude-corporate-skills --skill compliance-trackingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.6 KB, 255 tokens by cl100k_base, as published. Nobody here has run it
Compliance Tracking
Help track compliance requirements, prepare for audits, and maintain regulatory readiness.
Common Frameworks
| Framework | Focus | Key Requirements |
|---|---|---|
| SOC 2 | Service organizations | Security, availability, processing integrity, confidentiality, privacy |
| ISO 27001 | Information security | Risk assessment, security controls, continuous improvement |
| GDPR | Data privacy (EU) | Consent, data rights, breach notification, DPO |
| HIPAA | Healthcare data (US) | PHI protection, access controls, audit trails |
| PCI DSS | Payment card data | Encryption, access control, vulnerability management |
Compliance Tracking Components
Control Inventory
- Map controls to framework requirements
- Document control owners and evidence
- Track control effectiveness
Audit Calendar
- Upcoming audit dates and deadlines
- Evidence collection timelines
- Remediation deadlines
Evidence Management
- What evidence is needed for each control
- Where evidence is stored
- When evidence was last collected
Gap Analysis
- Requirements vs. current state
- Prioritized remediation plan
- Timeline to compliance
Output
Produce compliance status dashboards, gap analyses, audit prep checklists, and evidence collection plans.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most regulatory compliance skills give in 255 tokens
Counted across 117 of the 175 authors here whose files we hold, read 2026-09-06
- Prefer opaque internal IDs over direct identifiersin 13 of 117, across 5 files
- Require redaction or a non-PHI event modelin 13 of 117, across 5 files
- Start with healthcare-phi-compliance for concrete implementation rulesin 13 of 117, across 5 files
- Escalate to healthcare-reviewer when patient safety or clinical workflows are affectedin 13 of 117, across 5 files
- Require authenticated access, scoped authorization, and audit trails for PHIin 13 of 117, across 5 files
- Treat third-party providers as blocked until BAA status is clearin 13 of 117, across 5 files
- Assume patient messages may contain PHIin 9 of 117, across 4 files
- Apply HIPAA decision gatesin 8 of 117, across 3 files
- Verify BAA coverage before sending PHI to any providerin 8 of 117, across 3 files
- Give users only the smallest PHI slice neededin 7 of 117, across 2 files
- Encrypt data at rest and in transitin 7 of 117
- Make PHI read, write, and export events auditablein 6 of 117, across 3 files
Said here and by no other author read
- Document control owners and evidence
- Track control effectiveness
- Track audit dates and deadlines
- Track evidence timelines and remediation deadlines
- Track evidence needs, storage, and collection dates
- Compare requirements to current state
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.