omh-legal-compliance-review

# Legal Compliance Review This is a Hermes-native `legal-compliance-review` workflow skill. ## Why This Exists `legal-compliance-review` surfaces scoped legal and compliance issues before a human legal decision without pretending Hermes is counsel or an external filing surface. ## Do Not Use When - The user needs a final jurisdiction-specific legal opinion, legal representation, or authoritative filing decision; prepare the issue and counsel brief instead. - The review is about code, secrets, permissions, prompt injection, dependencies, or unsafe tool behavior; use `security-safety-review`. - The request is a plain-language rewrite without a legal-risk review objective; use `content-operator`. - The user asks to sign, accept, submit, file, publish, or change a policy or contract in an external system; use `connector-operator` only after explicit authority. ## Examples Good example: - Prompt: Review this vendor DPA for data-processing obligations, risky clauses, and questions for counsel. - Expected behavior: Prepare an authority-bound issue matrix, ranked risks, and counsel questions. - Why: The request needs a prepared review and escalation aid before a legal decision. Bad example: - Prompt: Audit this OAuth integration for secret and permission risks. - Expected behavior: Route to `security-safety-review`, not `legal-compliance-review`. - Why: The target is technical security risk rather than contract or compliance analysis. ## Completion Checklist - Findings or...