LEX: Legal-Entity-X-ref
Overview
LEX is a structured truth engine designed to eliminate legal hallucinations by grounding agents in verified government references and legislation across 29+ jurisdictions. It provides deterministic context for business formation, employment, and contract drafting.
When to Use This Skill
- Use when you need to cross-reference or compare legal requirements between different territories, such as verifying the compliance gap between an EU SARL and a US LLC.
- Use when working with foundational business or employment documents that require specific, jurisdiction-compliant clauses to be inserted into a professional scaffold.
- Use when the user asks about the specific regulatory nuances, formation steps, or "truth-based" definitions of legal entities within the 29 supported jurisdictions (USA, Canada, and the EU).
How It Works
Step 1: Identify Jurisdiction
Before drafting, determine if the user's entity or contract target is in the USA, Canada, or the EU.
Step 2: Search & Fetch Context
Use the CLI shortcuts to find the relevant legal patterns and templates.
- Run
lex search <query> to find matching templates.
- Run
lex get <path> to read the granular metadata and requirements.
Step 3: Scaffold Drafting
Generate foundation-level documents using lex draft <description>. This ensures that all drafts include the mandatory AI-generated content disclaimer.
Step 4: Verify Authority
Always include a "Verified Sources" section in your output by running lex verify, which fetches official government links for the retrieved context.
Examples
Example 1: Comparing Employment Laws
# Get the workforce template to compare US vs EU notice periods
lex get templates/02_employment_workforce.md
Example 2: Drafting a Czech Contract
# Create a house sale contract scaffold in Czech language
lex draft "Czech house sale contract"
Best Practices
- ✅ Trust but Verify: Always include the links provided by
lex verify in your output.
- ✅ Table Formatting: Use tables when comparing results across multiple jurisdictions.
- ❌ No Guessing: If a jurisdiction is outside the US/EU/CA scope, state that it is outside the LEX "Truth Engine" coverage.
- ❌ No Anecdotal Advice: Stick strictly to the findings in the templates or verified government domains.
Common Pitfalls
- Problem: Legal hallucination regarding specific EU notice periods.
Solution: Run
lex get templates/02_employment_workforce.md to see the restrictive covenant comparison table.
Related Skills
@employment-contract-templates - For more specific HR policy phrasing.
@legal-advisor - For general legal framework architecture.
@security-auditor - For reviewing the final repository security.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: lex3description: "Centralized 'Truth Engine' for cross-jurisdictional legal context (US, EU, CA) and contract scaffolding."4category: business5risk: safe6source: community7date_added: "2026-03-10"8author: Svobikl9tags: [legal, context, cross-jurisdictional, compliance, scaffolding]10tools: [claude, cursor, gemini]11metadata:12 source: https://skillmd.com/skills/antigravity/lex13---1415# LEX: Legal-Entity-X-ref1617## Overview1819LEX is a structured truth engine designed to eliminate legal hallucinations by grounding agents in verified government references and legislation across 29+ jurisdictions. It provides deterministic context for business formation, employment, and contract drafting.2021## When to Use This Skill2223- Use when you need to cross-reference or compare legal requirements between different territories, such as verifying the compliance gap between an **EU SARL** and a **US LLC**.24- Use when working with foundational business or employment documents that require specific, jurisdiction-compliant clauses to be inserted into a professional scaffold.25- Use when the user asks about the specific regulatory nuances, formation steps, or "truth-based" definitions of legal entities within the **29 supported jurisdictions** (USA, Canada, and the EU).2627## How It Works2829### Step 1: Identify Jurisdiction30Before drafting, determine if the user's entity or contract target is in the **USA, Canada, or the EU**.3132### Step 2: Search & Fetch Context33Use the CLI shortcuts to find the relevant legal patterns and templates.34- Run `lex search <query>` to find matching templates.35- Run `lex get <path>` to read the granular metadata and requirements.3637### Step 3: Scaffold Drafting38Generate foundation-level documents using `lex draft <description>`. This ensures that all drafts include the mandatory AI-generated content disclaimer.3940### Step 4: Verify Authority41Always include a "Verified Sources" section in your output by running `lex verify`, which fetches official government links for the retrieved context.4243## Examples4445### Example 1: Comparing Employment Laws46```bash47# Get the workforce template to compare US vs EU notice periods48lex get templates/02_employment_workforce.md49```5051### Example 2: Drafting a Czech Contract52```bash53# Create a house sale contract scaffold in Czech language54lex draft "Czech house sale contract"55```5657## Best Practices5859- ✅ **Trust but Verify**: Always include the links provided by `lex verify` in your output.60- ✅ **Table Formatting**: Use tables when comparing results across multiple jurisdictions.61- ❌ **No Guessing**: If a jurisdiction is outside the US/EU/CA scope, state that it is outside the LEX "Truth Engine" coverage.62- ❌ **No Anecdotal Advice**: Stick strictly to the findings in the templates or verified government domains.6364## Common Pitfalls6566- **Problem:** Legal hallucination regarding specific EU notice periods.67 **Solution:** Run `lex get templates/02_employment_workforce.md` to see the restrictive covenant comparison table.6869## Related Skills7071- `@employment-contract-templates` - For more specific HR policy phrasing.72- `@legal-advisor` - For general legal framework architecture.73- `@security-auditor` - For reviewing the final repository security.7475## Limitations76- Use this skill only when the task clearly matches the scope described above.77- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.78- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.