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/aup-template.md
View on GitHub# AI Acceptable Use Policy Template
> Customize sections marked [FIRM], [DATE], [TEAM] before publishing.
---
# [FIRM] Artificial Intelligence Acceptable Use Policy
**Version:** 1.0
**Effective Date:** [DATE]
**Owner:** [TEAM] — Information Security AI (ISAI)
**Review Cycle:** Annual
---
## 1. Purpose
This policy establishes the rules for acceptable use of artificial intelligence (AI) tools and services at [FIRM]. It protects the firm, its clients, and employees from risks associated with AI use including data leakage, regulatory violations, and reputational harm.
## 2. Scope
This policy applies to all employees, contractors, and third parties who use AI tools in connection with [FIRM] business, on any device, in any location.
## 3. Approved AI Tools
Only AI tools approved by ISAI may be used for firm business. The current approved list is maintained at [LINK].
Using non-approved AI tools with firm data is prohibited.
## 4. Mandatory Training
All employees must complete **Responsible AI Usage Training** before accessing approved AI tools. Access will be blocked until training is confirmed complete. Training must be renewed annually.
## 5. Prohibited Inputs
The following categories of data must **never** be entered into any AI tool, including approved tools, unless specifically authorized in writing by ISAI:
### 5.1 Financial & Regulatory
- Material non-public information (MNPI)
- Investment strategies, recommendations, or decisions under active consideration
- Client portfolio information
- Unannounced financial results, M&A activity, or transactions
- Trading positions or strategies
- Regulatory filings not yet public
### 5.2 Client & Personal Data
- Client names, account numbers, or identifying information
- Employee personal data (SSNs, DOB, salary, health information)
- Any data subject to GDPR, CCPA, or other privacy regulation
- Biometric data
### 5.3 Firm Confidential
- Source code (proprietary or licensed)
- Internal passwords, API keys, credentials, or secrets
- Unreleased product plans, roadmaps, or strategies
- Legal advice, litigation strategy, or privileged communications
- Internal audit findings or risk assessments
- Merger, acquisition, or restructuring information
### 5.4 Operational Security
- Network architecture, IP addresses, or infrastructure details
- Security controls, vulnerabilities, or pen test results
- Incident details or active investigations
## 6. Required Behaviors
- **Verify outputs:** AI-generated content must be reviewed and verified by a qualified human before being acted upon, published, or shared
- **Disclose AI use:** Clearly identify AI-generated content when sharing internally or externally
- **Use enterprise tiers only:** Consumer/free tiers of AI tools do not provide data protection guarantees and are prohibited for firm data
- **Report incidents:** Any suspected data leakage to an AI tool must be reported to ISAI immediately at [CONTACT]
## 7. Monitoring
[FIRM] monitors AI tool usage including prompts and outputs for policy compliance. By using firm-approved AI tools, employees consent to this monitoring. Monitoring is conducted by the ISAI team using automated DLP controls.
## 8. Enforcement
Violations of this policy may result in:
- Immediate suspension of AI tool access
- Disciplinary action up to and including termination
- Regulatory reporting where required by law
- Personal liability for regulatory violations (e.g., MNPI misuse)
## 9. Exceptions
Exceptions to this policy require written approval from ISAI and the CISO. Submit exception requests to [CONTACT].
## 10. Acknowledgment
All employees must sign acknowledgment of this policy before AI tool access is granted. Records of acknowledgment are maintained by [TEAM].
---
**Questions?** Contact ISAI at [CONTACT]
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 |