The rich practice context from setup — jurisdiction footprint, risk posture, playbook positions — was only accessible through structured skills. A lawyer asking a quick question in the plugin's domain got a generalist answer. Now the plugin CLAUDE.md instructs Claude to read the practice profile and apply the plugin's guardrails for ANY question in the domain, not just skill invocations. A configured plugin feels like a colleague who already knows your practice, not a form you fill out. The skills are the structured workflows; this is everything in between.
8 lines
No EOL
411 B
JSON
8 lines
No EOL
411 B
JSON
{
|
|
"name": "commercial-legal",
|
|
"version": "0.4.3",
|
|
"description": "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.",
|
|
"author": {
|
|
"name": "Anthropic"
|
|
}
|
|
} |