General
lex - Claude MCP Skill
Centralized 'Truth Engine' for cross-jurisdictional legal context (US, EU, CA) and contract scaffolding.
SEO Guide: Enhance your AI agent with the lex tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to centralized 'truth engine' for cross-jurisdictional legal context (us, eu, ca) and contract scaffold... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.md# 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 ```bash # Get the workforce template to compare US vs EU notice periods lex get templates/02_employment_workforce.md ``` ### Example 2: Drafting a Czech Contract ```bash # 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.
Signals
Information
- Repository
- arlenagreer/claude_configuration_docs
- Author
- arlenagreer
- Last Sync
- 6/18/2026
- Repo Updated
- 6/14/2026
- Created
- 4/10/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
firecrawl-build-search
Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.
firecrawl-build-onboarding
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
firecrawl-build
Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.
firecrawl-build-interact
Integrate Firecrawl `/interact` into product code for dynamic pages and browser actions after scraping. Use when a feature needs clicks, form fills, pagination, authentication-aware flows, or other multi-step interactions that plain `/scrape` cannot complete.
Related Guides
Mastering the Oracle CLI: A Complete Guide to the Claude Skill for Database Professionals
Learn how to use the oracle Claude skill. Complete guide with installation instructions and examples.
Python Django Best Practices: A Comprehensive Guide to the Claude Skill
Learn how to use the python django best practices Claude skill. Complete guide with installation instructions and examples.
Building Full-Stack Applications with Claude: The Node.js MongoDB JWT Express React Skill Guide
Learn how to use the nodejs mongodb jwt express react Claude skill. Complete guide with installation instructions and examples.