Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By az9713
Reviews vendor agreements, NDAs, and SaaS subscriptions against your sales-side or purchasing-side playbook, tracks renewals and cancel-by deadlines before they're missed, routes escalations to the right approver, and translates reviews into summaries business stakeholders will actually read.
npx claudepluginhub az9713/claude-for-legal-tutorial --plugin commercial-legalWeekly agent that surfaces recently signed agreements containing playbook deviations and prompts the attorney to log context while memory is fresh. Runs weekly by default (Monday morning). Also runs on-demand. Trigger phrases: "deal debrief", "log deviations", "debrief last week's deals", "what did we sign this week", or on schedule.
Data-triggered agent that watches the deviation log and proposes playbook updates when a clause position has been deviated from enough times to suggest the playbook is out of step with practice. Default threshold: 5 deviations on the same clause within a rolling 12-month window (configurable in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`). Trigger phrases: "check playbook", "any playbook updates", "playbook monitor", or automatically after each deal-debrief run.
Scheduled agent that checks the renewal register and posts what's coming up. Runs weekly by default. Posts to the channel named in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` → House style → Renewal alerts. Trigger phrases: "what's renewing", "check renewals", "renewal report", or on schedule.
Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.
Run the cold-start interview to learn your commercial contracts practice and write your team practice profile. Use on first use of the plugin, when `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` is missing or still contains template placeholders, or when the user says "set up the plugin", "configure commercial contracts", "onboard me", or "let's get started". This is the only skill that should run on a fresh install.
Guided customization of your commercial contracts practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, playbook positions, NDA triage preferences, house style, review preferences, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my playbook", "tune my config", or "customize".
Route a contract issue to the right approver per the escalation matrix in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`, and draft the ask. Use when the user says "who needs to approve this", "escalate this", "does this need GC sign-off", "route this for approval", or when another skill finds an issue that exceeds the reviewer's authority.
Manage matter workspaces — new, list, switch, close, or detach (practice-level). Use when a multi-client practitioner needs to create a matter, switch the active matter, list matters, archive a matter, or detach to practice-level context, or when another skill needs to know which matter it's working in.
Search your contract repository and workflows using plain language — expiring MSAs, termination clauses, vendor agreements — scoped to your permissions.
Agreement search, status tracking, and signature workflows.
Governed iManage content connected to Claude — documents stay in iManage, access is permission-bound and auditable.
Outside counsel recommendations from The L Suite — 5,000+ in-house counsel community sentiment, rankings, and expertise evidence.
Live, deterministic access to contract structure — resolve definitions, validate cross-references, map dependencies, run structural diffs.
External network access
Connects to servers outside your machine
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Memory compression system for Claude Code - persist context across sessions
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.
Intelligent prompt optimization using skill-based architecture. Enriches vague prompts with research-based clarifying questions before Claude Code executes them
Streamline people operations — recruiting, onboarding, performance reviews, compensation analysis, and policy guidance. Maintain compliance and keep your team running smoothly.
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.
Full agentic layer framework implementing the Codebase Singularity concept - enabling AI agents to operate your codebase autonomously through planning, building, reviewing, and fixing workflows. Implements Class 1-3 with orchestration capabilities.
Thread-Based Engineering examples - demonstrates Base, Parallel, Chained, Fusion, Big, Long, and Zero-Touch thread patterns for agentic coding
Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.
Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls
This is a tutorial fork of anthropics/claude-for-legal. The plugins and skills are identical to the original. This fork adds a
docs/directory with deep-dive documentation that dissects how every plugin and skill is constructed — surfacing the design patterns, best practices, and architectural decisions behind the system. If you want to understand how to build on this, extend it, or replicate the patterns in your own plugins, start with the docs.
| Doc | What it covers |
|---|---|
| Overview: what is this? | Mental model, ASCII architecture diagram, end-to-end session narrative, scope boundaries |
| Key concepts glossary | 38-term glossary — every concept used across plugins and skills defined precisely |
| Quickstart | Working in under 15 minutes — dual path for Claude Cowork and Claude Code |
| Onboarding guide | Zero-to-confident: the linter analogy, the three things you must understand, a full NDA walkthrough |
| Plugin anatomy | Every file in a plugin directory dissected — plugin.json, CLAUDE.md, skills/, agents/, hooks/, .mcp.json |
| Skill anatomy | SKILL.md structure, frontmatter fields, all 8 recurring design patterns, skill design checklist |
| Practice profile | Config path contract, shared company profile, every CLAUDE.md section and its reasoning |
| Guardrails | All 18 shared guardrails dissected — no-silent-supplement, citation hygiene, destination check, cross-skill severity floor, and more |
| Agents | Scheduled agent anatomy, how agents call skills, managed-agent cookbook deployment |
| Connectors | MCP connector config, full connector table by practice area, the four behavior requirements |
| Hooks | hooks.json format, all hook events, practical legal-context examples |
| Build a skill | Step-by-step guide to authoring a SKILL.md that follows all 9 design principles |
| Build a plugin | Full plugin creation guide — directory layout, required files, 3 mandatory skills, CLAUDE.md construction |
| Customize a plugin | Three-level customization: cold-start interview, customize skill, direct editing |
| SKILL.md frontmatter reference | Every frontmatter field with valid values, defaults, and source examples |
| plugin.json reference | plugin.json and marketplace.json fields, version bump rules, author vs. owner distinction |
| Tag vocabulary reference | All 20+ inline tags — factual accuracy, source provenance, judgment, severity, cell states |
| System design | Full ASCII architecture diagram, 5 data flows, component breakdown, scaling characteristics |
| ADR 001: Two-layer instruction architecture | Why SKILL.md + CLAUDE.md — alternatives analyzed, trade-offs, consequences |
| ADR 002: Practice profile as plain text | Why markdown over YAML/JSON/database — alternatives analyzed, trade-offs, consequences |
| commercial-legal deep-dive | Sales vs. purchasing playbook, GREEN gate, scope check, dual severity, playbook monitor |
| corporate-legal deep-dive | Modular profile, typed column schema, verbatim enforcement, fan-out pattern |
| employment-legal deep-dive | Jurisdiction-first analysis, worker classification, investigation four-skill pattern |
| privacy-legal deep-dive | Three-tier triage, DPA auto-detection, DSAR statutory timelines, policy drift monitoring |
| product-legal deep-dive | Proportionality-first is-this-a-problem, risk calibration, launch tracker integration |
| regulatory-legal deep-dive | Materiality filter, Monday digest format, policy diff, gap tracker |
| ai-governance-legal deep-dive | Per-system classification, use-case registry, red lines, intentional no-auto-derive design |
| ip-legal deep-dive | Triage vs. opinion distinction, DMCA three-way, enforcement posture, OSS license classification |
| litigation-legal deep-dive | Dual-surface pattern, FRE 408 gate, chronology builder, privilege log review |