CSlawyer1985/legal-skillhub / skills/ai-compliance
ai-compliance
VerifiedAI compliance analysis for EU AI Act, ISO 42001, NIST AI RMF, GDPR, OECD, financial services regulations (SEC, FCA, FINRA, DORA, MiFID II), and other frameworks. Use when asked to generate a compliance checklist for an AI tool or use case, determine if a risk assessment is required, score an AI tool's risk level, identify where an AI tool or use case could run afoul of regulatory requirements, perform a gap analysis, recommend remediation steps, assess a vendor, draft an acceptable use policy, map training requirements, or review jurisdiction-specific AI rules. Triggers on phrases like "compliance checklist", "risk assessment", "risk score", "does this comply", "EU AI Act", "ISO 42001", "NIST AI RMF", "AI governance", "gap analysis", "vendor assessment", "acceptable use policy", "MNPI", "AI training requirements", or any request to evaluate an AI tool or use case for regulatory compliance or risk.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.6 KB |
| _meta.json | config | 132 B |
| references/ai-inventory.md | markdown | 2.7 KB |
| references/aup-template.md | markdown | 3.7 KB |
| references/checklist-templates.md | markdown | 4.1 KB |
| references/data-classification.md | markdown | 3.7 KB |
| references/eu-ai-act.md | markdown | 2.6 KB |
| references/finserv-regulations.md | markdown | 4.7 KB |
| references/incident-response.md | markdown | 4.9 KB |
| references/iso-42001.md | markdown | 3.4 KB |
| references/iso27001-alignment.md | markdown | 4.4 KB |
| references/jurisdiction-map.md | markdown | 4.3 KB |
| references/nist-ai-rmf.md | markdown | 4.6 KB |
| references/other-frameworks.md | markdown | 2.6 KB |
| references/remediation-playbooks.md | markdown | 6.6 KB |
| references/risk-scoring.md | markdown | 4.4 KB |
| references/training-requirements.md | markdown | 3.3 KB |
| references/vendor-assessment.md | markdown | 3.5 KB |
references/data-classification.md
View on GitHub# Data Classification × AI Tool Matrix
## Data Classification Tiers
| Tier | Definition | Examples |
|---|---|---|
| **Public** | Approved for public release | Press releases, public filings, marketing materials |
| **Internal** | For internal use only, not sensitive | General business comms, internal FAQs, org charts |
| **Confidential** | Sensitive business information | Business strategies, vendor contracts, internal financials |
| **Restricted** | Highly sensitive, strictly controlled | MNPI, client PII, credentials, source code, legal privilege |
| **Regulated** | Subject to specific legal/regulatory controls | GDPR PII, HIPAA, FINRA, attorney-client privilege |
---
## AI Tool Usage Matrix
| Data Tier | Consumer AI (ChatGPT Free, Perplexity Free, etc.) | Approved Enterprise AI (M365 Copilot, ChatGPT Enterprise, etc.) | Internal/On-Prem AI (OpenClaw, self-hosted models) |
|---|---|---|---|
| **Public** | ✅ Permitted | ✅ Permitted | ✅ Permitted |
| **Internal** | ❌ Prohibited | ✅ Permitted with care | ✅ Permitted |
| **Confidential** | ❌ Prohibited | ⚠️ Case-by-case, ISAI approval | ✅ Permitted |
| **Restricted** | ❌ Prohibited | ❌ Prohibited | ⚠️ ISAI approval required |
| **Regulated** | ❌ Prohibited | ❌ Prohibited | ⚠️ ISAI + Legal approval required |
---
## Prohibited Input Quick Reference
Always prohibited in **any** AI tool unless explicitly approved:
| Category | Examples | Why |
|---|---|---|
| MNPI | Unreleased earnings, M&A targets, trading strategies | Securities law (SEC, FCA, MAR) |
| Client PII | Names + account numbers, portfolio details | GDPR, CCPA, fiduciary duty |
| Credentials | Passwords, API keys, tokens, secrets | Credential theft, unauthorized access |
| Source code | Proprietary algorithms, trading systems | IP theft, competitive risk |
| Legal privilege | Legal advice, litigation strategy | Waives privilege |
| Audit findings | Control weaknesses, vulnerabilities | Security risk |
| Network details | IP ranges, firewall rules, architecture | Security risk |
| HR data | Salaries, performance reviews, health info | Privacy law, discrimination risk |
---
## fi.com Specific Guidance
Based on current webhook_events data, the following are **actively being entered** into Perplexity and ChatGPT and must be addressed immediately:
| Detected Input Type | Current Status | Required Action |
|---|---|---|
| Financial data / reports | 🔴 Being entered, 100% blocked | DLP working — enforce AUP, gate with training |
| Investment strategies | 🔴 Being entered, 100% blocked | Escalate to Legal/Compliance — potential MNPI |
| Investment decisions | 🔴 Being entered, 100% blocked | Escalate to Legal/Compliance — potential MNPI |
| Internal communications | 🟡 Being entered, partially blocked | Strengthen DLP rules |
| Network infrastructure | 🟡 Being entered, partially blocked | Security risk — tighten DLP |
| Source code | 🔴 New this week, not fully blocked | Update DLP rules immediately |
| Credentials/passwords | 🔴 Being entered, some blocked | Credential rotation + DLP tightening |
| GitHub tokens | 🔴 New this week | Immediate credential rotation required |
---
## Decision Tree: Can I use AI for this task?
```
Is the data Public?
→ YES: Any approved tool is fine
→ NO: Continue ↓
Is the data Internal only (no PII, no financial)?
→ YES: Use approved enterprise tools only. No consumer AI.
→ NO: Continue ↓
Is the data Confidential (strategies, contracts, internal financials)?
→ YES: Contact ISAI for approval. On-prem tools preferred.
→ NO: Continue ↓
Is it MNPI, client PII, credentials, source code, or regulated data?
→ YES: DO NOT enter into any AI tool. Contact ISAI.
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |