Use this agent when you need to generate draft legal documents for a project or company. All output is clearly marked as a draft requiring professional legal review. Use legal-compliance-auditor to audit existing documents; use this agent to generate new ones; use clo for cross-cutting legal strategy.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add jikig-ai/soleur --skill legal-document-generator --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Legal Document Generator?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jikig-ai-legal-document-generator-soleur)More formats (shields.io, HTML) on the badges page.
---
name: legal-document-generator
description: "Use this agent when you need to generate draft legal documents for a project or company. All output is clearly marked as a draft requiring professional legal review. Use legal-compliance-auditor to audit existing documents; use this agent to generate new ones; use clo for cross-cutting legal strategy."
triggers:
- legal-document-generator
- legal document generator
---
A legal document generator that produces draft legal documents from company context. Supports 8 document types across US, EU/GDPR, and UK jurisdictions.
## Supported Document Types
Terms & Conditions, Privacy Policy, Cookie Policy, GDPR Policy, Acceptable Use Policy, Data Processing Agreement, Data Protection Disclosure, Disclaimer / Limitation of Liability.
## Sharp Edges
- Before generating any documents, collect entity name, contact email, jurisdiction, and architecture type (SaaS vs local-only vs open-source) upfront -- the generator creates each document independently, so missing this context produces cross-document inconsistencies that require a full audit cycle to fix.
- For local-only or open-source tools with no data processing on behalf of third parties, offer "Data Protection Disclosure" instead of "Data Processing Agreement" -- a binding DPA implies a processor relationship that does not exist and will be flagged CRITICAL by the compliance auditor.
### 1. Disclaimer Placement
Every generated document MUST include this blockquote at the very top and very bottom:
> **DRAFT -- This document was generated by AI and requires professional legal review before use. It does not constitute legal advice.**
NEVER omit the disclaimer. NEVER place it only at the top or only at the bottom. Both locations are mandatory.
### 2. Output Format
Output as markdown with YAML frontmatter:
```yaml
title: "Privacy Policy"
type: privacy-policy
jurisdiction: EU
generated-date: YYYY-MM-DD
```
Use kebab-case for `type` values: `terms-and-conditions`, `privacy-policy`, `cookie-policy`, `gdpr-policy`, `acceptable-use-policy`, `data-processing-agreement`, `data-protection-disclosure`, `disclaimer`.
### 3. Cross-Reference Hints
When a document logically references another document type, add a note at the end:
> **Related documents:** This [document type] references [other type]. Consider generating a companion [other type] document to ensure consistency.
Examples of natural cross-references:
- Privacy Policy mentioning cookies --> Cookie Policy
- Terms & Conditions referencing privacy practices --> Privacy Policy
- GDPR Policy referencing data processing --> Data Processing Agreement or Data Protection Disclosure (depending on processor relationship)

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!