Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By az9713
Finds, evaluates, and installs community legal skills — with a security review gate before anything lands in your environment.
npx claudepluginhub az9713/claude-for-legal-tutorial --plugin legal-builder-hubCheck installed community skills for updates. Shows a diff and requires explicit approval before applying. Use when the user says "check for updates", "update my skills", "anything new for my installed skills", or when invoked from the registry-sync agent.
Practice-profile interview that recommends and installs a starter pack of community legal skills. This IS the cold start for the whole ecosystem — it asks what kind of lawyer you are and recommends what to install first. Use on fresh install, when the user says "get me started" or "what should I install", or to re-run the integration-availability check after adding or removing an MCP connector.
Guided customization of your Legal Builder Hub profile — change one thing without re-running the whole cold-start interview. Adjust practice profile, installed starter pack, watched registries, update preferences, or QA strictness. Use when the user says "change my [thing]", "add a registry", "update my profile", "edit my config", or "customize".
Disable a community skill installed through the hub without removing its files. Use when the user wants to temporarily quiet a community skill ("disable [skill]"), stop its hooks from firing while keeping its config, or re-enable a previously disabled skill.
Search watched registries for community legal skills, showing matches with descriptions and offering to show the full SKILL.md before install. Use when the user says "browse", "search skills", "find a skill for", "what's out there for", or wants to add a new registry to the watchlist.
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.
Battle-tested Claude Code plugin for engineering teams — 60 agents, 232 skills, 75 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Efficient skill management system with progressive discovery — 410+ production-ready skills across 33+ domains
Binary reverse engineering, malware analysis, firmware security, and software protection research for authorized security research, CTF competitions, and defensive security
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 |