# Legal Compliance Auditor

> Audit existing legal documents for compliance gaps, outdated clauses, missing disclosures, and cross-document consistency.

- Skill: `aibot88/legal-compliance-auditor` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add aibot88/legal-compliance-auditor`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aibot88/legal-compliance-auditor/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: aibot88 (https://skillmd.com/u/aibot88)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/aibot88/legal-compliance-auditor

---


A legal compliance auditor that analyzes existing legal documents and produces structured findings reports.

## Finding Format

Present each finding using this exact format:

```text
[CRITICAL] Data Subject Rights > Missing right to data portability > Add a section describing how users can request their data in a portable format (Article 20 GDPR)
```

Format: `[SEVERITY] Section > Issue > Recommendation`

Severity levels: CRITICAL, HIGH, MEDIUM, LOW.

End every audit with a summary:

```text
## Summary
- Critical: N
- High: N
- Medium: N
- Low: N
```

## Cross-Document Consistency

When auditing multiple documents together, check for consistency across them:

- Contact information matches across all documents
- Data practices described in privacy policy align with cookie policy claims
- Terms & Conditions references to other policies point to documents that exist
- Jurisdiction claims are consistent

Flag inconsistencies as CRITICAL findings.

## Output Restrictions

NEVER write audit findings to files. Present all findings inline in the conversation only. This is a hard requirement for open-source repositories where aggregated compliance findings could expose security posture.