Merge pull request #4 from anthropics/tobin/add-cocounsel-legal
Add CoCounsel Legal partner plugin under external_plugins/
This commit is contained in:
Tobin South
GitHub
commit
993f6619fc
6 changed files with 223 additions and 0 deletions
|
|
@ -99,6 +99,14 @@
|
|||
"author": {
|
||||
"name": "Anthropic"
|
||||
}
|
||||
},
|
||||
{
|
||||
"name": "cocounsel-legal",
|
||||
"source": "./external_plugins/cocounsel-legal",
|
||||
"description": "CoCounsel Legal delivers comprehensive Westlaw Deep Research reports with inline, linked citations to Westlaw and Practical Law sources.",
|
||||
"author": {
|
||||
"name": "Thomson Reuters"
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
|
|
|
|||
17
README.md
17
README.md
|
|
@ -142,6 +142,8 @@ litigation-legal/ # portfolio, matters, holds, demands, depo prep, claim
|
|||
legal-clinic/ # clinic setup, student ramp, intake, deadlines, memos, handoffs
|
||||
law-student/ # Socratic drilling, outlining, IRAC, bar prep, flashcards
|
||||
legal-builder-hub/ # community skill discovery and install with a trust gate
|
||||
external_plugins/ # partner-built plugins maintained by their vendors
|
||||
cocounsel-legal/ # Thomson Reuters — Westlaw Deep Research via the CoCounsel Legal MCP
|
||||
managed-agent-cookbooks/ # Claude Managed Agent cookbooks — one dir per scheduled agent
|
||||
diligence-grid/
|
||||
docket-watcher/
|
||||
|
|
@ -267,6 +269,14 @@ Grouped by where the work sits. Each plugin's cold-start interview is what tailo
|
|||
|---|---|
|
||||
| **[legal-builder-hub](./legal-builder-hub)** | Community skill discovery and install with a real trust layer — watched registries, a QA framework (`/legal-builder-hub:skills-qa`), SHA-pinned updates, and a mandatory trust check before anything lands in your environment. |
|
||||
|
||||
### External / partner-built
|
||||
|
||||
Plugins under [`external_plugins/`](./external_plugins) are built and maintained by their vendors. They install from this marketplace like any other plugin, but the vendor owns the code, the connector, and the support channel.
|
||||
|
||||
| Plugin | Built by | What it adds |
|
||||
|---|---|---|
|
||||
| **[cocounsel-legal](./external_plugins/cocounsel-legal)** | Thomson Reuters | Westlaw Deep Research with fully cited reports — caselaw, statutes, regulations, Practical Law, and secondary sources across up to three U.S. jurisdictions per run. Requires a CoCounsel Legal subscription with the MCP connector enabled. Support: cocounselsupport@tr.com. |
|
||||
|
||||
## The trust layer for community legal skills
|
||||
|
||||
The community is building legal skills fast — registries like LegalOps Consulting's `lpm-skills` and Lawvable already list dozens. But nobody certifies community skills, and a lawyer installing a random skill from GitHub is installing code that runs with access to their matter files, their practice profile, and their research connectors.
|
||||
|
|
@ -296,6 +306,7 @@ These plugins ship connectors for the systems legal teams live in. A connector g
|
|||
| **Slack** | Read channels, search, send messages and canvases | all plugins | Your workspace |
|
||||
| **Google Drive** | Read docs, sheets, slides; fetch by link | all plugins | Your account |
|
||||
| **Lexis+ Protégé** | Research, citations, shepardizing | `ai-governance-legal`, `legal-clinic`, `commercial-legal`, `employment-legal`, `ip-legal`, `litigation-legal`, `privacy-legal`, `product-legal`, `regulatory-legal`, `law-student` | Customer subscription |
|
||||
| **CoCounsel Legal (Thomson Reuters)** | Westlaw Deep Research — cited reports across caselaw, statutes, regulations, Practical Law | `cocounsel-legal` | Customer subscription; OAuth |
|
||||
| **Box** | Read files and folders in VDRs and matter rooms | `corporate-legal` | Your tenant |
|
||||
| **Ironclad** | Read the contract register, renewal dates, clauses | `commercial-legal` | Customer subscription |
|
||||
| **DocuSign / DocuSign CLM** | Envelope status, executed contracts, CLM metadata | `commercial-legal` | Customer subscription |
|
||||
|
|
@ -543,6 +554,12 @@ The full map across all plugins. The cold-start interview is the first thing to
|
|||
| `/law-student:study-plan` | study-plan | Build or update a long-term study plan |
|
||||
| `/law-student:session` | study-plan | Run a focused N-question session; update the plan |
|
||||
|
||||
### cocounsel-legal (Thomson Reuters)
|
||||
|
||||
| Command | Skill | What it does |
|
||||
|---|---|---|
|
||||
| `/cocounsel-legal:deep-research` | deep-research | Run Westlaw Deep Research — start, poll, and present a fully cited report |
|
||||
|
||||
## Contributing
|
||||
|
||||
Everything here is markdown and JSON. Fork, edit, PR.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,9 @@
|
|||
{
|
||||
"name": "cocounsel-legal",
|
||||
"version": "0.1.0",
|
||||
"description": "CoCounsel Legal delivers comprehensive Westlaw Deep Research reports with inline, linked citations to Westlaw and Practical Law sources.",
|
||||
"author": {
|
||||
"name": "Thomson Reuters",
|
||||
"email": "cocounselsupport@tr.com"
|
||||
}
|
||||
}
|
||||
11
external_plugins/cocounsel-legal/.mcp.json
Normal file
11
external_plugins/cocounsel-legal/.mcp.json
Normal file
|
|
@ -0,0 +1,11 @@
|
|||
{
|
||||
"mcpServers": {
|
||||
"cocounsel-legal": {
|
||||
"type": "http",
|
||||
"url": "https://legal-mcp.thomsonreuters.com/mcp",
|
||||
"oauth": {
|
||||
"clientId": "QCgP4IGN5JiLqXRHxiAVr3wu1ySo2nQx"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
46
external_plugins/cocounsel-legal/README.md
Normal file
46
external_plugins/cocounsel-legal/README.md
Normal file
|
|
@ -0,0 +1,46 @@
|
|||
# CoCounsel Legal
|
||||
|
||||
CoCounsel Legal brings Westlaw Deep Research into Claude for CoCounsel Legal subscribers. Run jurisdiction-specific legal research across U.S. federal and state law and receive fully cited reports with Westlaw and Practical Law source links. Deep Research reports cite case law, statutes, regulations, administrative materials, Practical Law, secondary sources, and current awareness content. Ask follow-up questions in the same conversation. The connector launches with Westlaw Deep Research and will expand to additional CoCounsel Legal capabilities over time.
|
||||
|
||||
- Use CoCounsel Legal to run Westlaw Deep Research with fully cited reports including linked citations to Westlaw and Practical Law sources.
|
||||
- Ask about legal research in up to three U.S. jurisdictions in a single research run.
|
||||
- Return to a completed CoCounsel Legal research conversation and retrieve the report later.
|
||||
- Ask follow-up questions in the same conversation without restarting research.
|
||||
|
||||
## Example use cases
|
||||
|
||||
1. Research how California courts have treated non-compete agreements for executive employees since 2020.
|
||||
2. I asked you to research California non-competes earlier. Can you now retrieve the full report?
|
||||
3. Follow up on that research: how does Texas law differ on executive non-competes for the same period?
|
||||
|
||||
## When to Use
|
||||
|
||||
Any questions answerable from caselaw, statutes, regulations, administrative materials, secondary sources, Practical Law documents and current awareness, including JD Supra. Examples include:
|
||||
|
||||
- How courts have ruled on an issue or what authority supports or challenges a position
|
||||
- The elements or defenses of a claim, or the governing standard for an issue in a particular jurisdiction
|
||||
- How a statute, regulation, or doctrine is being interpreted and applied
|
||||
- The arguments on both sides of an unsettled question
|
||||
|
||||
## When Not to Use
|
||||
|
||||
- Retrieving the full text of a specific document
|
||||
- Summarizing what a specific statute, regulation, or treatise says on its own (e.g., "what does the California Evidence Code say about hearsay?" or "what does Wright & Miller say about Rule 11?")
|
||||
- Analytics requests ("How often has Justice Scalia ruled in favor of...?")
|
||||
- Calculations ("What is the last possible filing date if...?")
|
||||
- Outcome predictions ("How likely is plaintiff to prevail on summary judgment?")
|
||||
- Identifying causes of action a client could bring (the skill researches what the law says, not whether a given set of facts states a claim)
|
||||
- Applying law to a specific fact pattern or scenario (the skill researches legal questions in the abstract, not how the law would resolve your facts)
|
||||
- Drafting legal documents, forms, or templates
|
||||
- Information about specific judges, attorneys, or parties
|
||||
- Foreign or non-U.S. law
|
||||
- Commands to execute tasks ("Send me an email about X case")
|
||||
- General legal definitions that don't require current authority
|
||||
- Comparisons across more than three jurisdictions
|
||||
- Boolean search queries (the tool expects natural language)
|
||||
|
||||
|
||||
### Links
|
||||
|
||||
- **Documentation:** https://legal-mcp.thomsonreuters.com/docs/connector-guide
|
||||
- **Support:** cocounselsupport@tr.com
|
||||
132
external_plugins/cocounsel-legal/skills/deep-research/SKILL.md
Normal file
132
external_plugins/cocounsel-legal/skills/deep-research/SKILL.md
Normal file
|
|
@ -0,0 +1,132 @@
|
|||
---
|
||||
name: cocounsel-legal:deep-research
|
||||
version: 0.1.0
|
||||
description: >
|
||||
Use this skill whenever a user specifically requests legal research or Westlaw Deep Research, asks for CoCounsel Legal or cocounsel legal support, or asks a question that requires explaining, analyzing, or synthesizing U.S. law.
|
||||
allowed-tools:
|
||||
- mcp
|
||||
- Bash
|
||||
---
|
||||
|
||||
# Westlaw Deep Research
|
||||
|
||||
Westlaw Deep Research searches Westlaw's database of caselaw, statutes, and administrative decisions and returns a written research report that explains, analyzes, or synthesizes relevant authority.
|
||||
|
||||
Deep Research employs an agentic process that mirrors the methodology of human researchers, utilizing Westlaw's proprietary tools to systematically analyze the trusted content available on Westlaw and Practical Law.
|
||||
|
||||
This skill will autonomously run the full research cycle: start, poll, report.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
The `cocounsel-legal` MCP server must be connected. Verify it is available before starting research. If the server is not connected, inform the user and stop.
|
||||
|
||||
## When to Use
|
||||
|
||||
- Use for any questions answerable from caselaw, statutes, regulations, administrative materials, secondary sources, Practical Law documents and Current Awareness materials, including JD Supra. Examples include:
|
||||
- How courts have ruled on an issue or what authority supports or challenges a position
|
||||
- The elements or defenses of a claim, or the governing standard for an issue in a particular jurisdiction
|
||||
- How a statute, regulation, or doctrine is being interpreted and applied
|
||||
- The arguments on both sides of an unsettled question
|
||||
|
||||
## When Not to Use
|
||||
|
||||
- If the request falls into one of the categories below, briefly explain that this skill isn't the right fit and point the user to the suggested alternative.
|
||||
- **Retrieving the full text of a specific document**
|
||||
- _Instead:_ Suggest the traditional search box on Westlaw.
|
||||
- **Summarizing what a specific statute, regulation, or treatise says on its own** (e.g., "what does the California Evidence Code say about hearsay?")
|
||||
- _Instead:_ Suggest the traditional search box on Westlaw.
|
||||
- **Analytics requests** ("How often has Justice Scalia ruled in favor of…?")
|
||||
- _Instead:_ Suggest Litigation Analytics on Westlaw.
|
||||
- **Calculations** ("What is the last possible filing date if…?")
|
||||
- _Instead:_ This request is out of scope of Westlaw Deep Research
|
||||
- **Outcome predictions**
|
||||
- _Instead:_ This request is out of scope of Westlaw Deep Research
|
||||
- **Drafting legal documents, forms, or templates**
|
||||
- _Instead:_ Suggest CoCounsel
|
||||
- **Information about specific judges, attorneys, or parties**
|
||||
- _Instead:_ Suggest Litigation Analytics on Westlaw
|
||||
- **Foreign or non-U.S. law**
|
||||
- _Instead:_ Suggest country-specific version of Westlaw, such as Westlaw UK or Westlaw Canada, or use Westlaw International
|
||||
- **Comparisons across more than three jurisdictions**
|
||||
- _Instead:_ Suggest AI Jurisdictional Surveys on Westlaw
|
||||
- **Terms and Connectors (boolean) search queries**
|
||||
- _Instead:_ Suggest the traditional search box on Westlaw
|
||||
- **Commands for execution of tasks**
|
||||
- _Instead:_ Suggest CoCounsel
|
||||
- **Obtaining an exhaustive list of results**
|
||||
- _Instead:_ Suggest Boolean search or Precision Research on Westlaw
|
||||
- **Identifying potential causes of action**
|
||||
- _Instead:_ Suggest Claims Explorer on Westlaw.
|
||||
- **An exhaustive review of fact patterns** (e.g., "Find all cases discussing...")
|
||||
- _Instead:_ Suggest Precision Research on Westlaw.
|
||||
- If you suggest an alternative, do not attempt to use the Deep Research skill further for that task.
|
||||
|
||||
## Communication Rules
|
||||
|
||||
- Never mention tool calls, tool-call budgets, polling, status checks, internal limits, conversation IDs, percent_complete, or any other implementation details to the user. Always speak about the research itself, not the mechanics of how you are tracking it.
|
||||
- If you need to pause before the research completes (for any internal reason), do NOT explain why.
|
||||
- Let the user know that research is ongoing and that a report will be completed soon.
|
||||
|
||||
## Research Workflow
|
||||
|
||||
### 1. Frame the query
|
||||
|
||||
- Extract the legal research question from the user's query using clear, natural language.
|
||||
- Use up to three jurisdictions if the user names them.
|
||||
- If no jurisdictions are mentioned, ask the user which jurisdiction(s) to use.
|
||||
|
||||
### 2. Start Research
|
||||
|
||||
- Call the MCP tool to initiate the research: `legal_research_start_deep_research(query, jurisdictions)`
|
||||
- Parameters:
|
||||
- `query` (string, required): The legal research question
|
||||
- `jurisdictions` (list of strings, optional): Up to 3 jurisdictions (e.g., ["California", "New York"])
|
||||
- This returns a `conversation_id` and initial `status`. Save the `conversation_id` for subsequent calls.
|
||||
- Next step: call check_deep_research_status with the conversation_id.
|
||||
- Before the first status check, wait ~10 seconds (the server is still setting up).
|
||||
|
||||
#### Rendering
|
||||
|
||||
- Inform the user that deep research is underway, briefly restating the legal question in natural, professional language.
|
||||
- Do not show the conversation_id to the user.
|
||||
|
||||
### 3. Poll for Completion
|
||||
|
||||
- Poll `legal_research_check_deep_research_status(conversation_id)`.
|
||||
- Always run a Bash `sleep` between polls. Never call check_deep_research_status back-to-back without sleeping.
|
||||
- Continue until `is_terminal` is true.
|
||||
- Decide the next action based on the response:
|
||||
- (1) If is_terminal is true and status is 'complete', call get_deep_research_report with the conversation_id.
|
||||
- (2) If status is 'failed', stop and report the error_type and failure_reason to the user in plain language, without exposing field names.
|
||||
- (3) Otherwise, sleep for the duration in the response's `next_action_poll_backoff_ms` field (milliseconds), then poll again.
|
||||
- If percent_complete has not changed across two consecutive checks, add 5 seconds to the sleep.
|
||||
|
||||
#### Rendering
|
||||
|
||||
- Communicate in plain language as if narrating the research process.
|
||||
- Render research_plan as a markdown unordered list (one item per line, each line prefixed with '- '), so the steps display with clear visual separation.
|
||||
- Insert a blank line before and after the list so it renders cleanly.
|
||||
- Only update the user when there is something new to say (a step completed, or a new step started). Do not repeat the same status.
|
||||
|
||||
### 4. Retrieve and Present Report **Verbatim**
|
||||
|
||||
- Once status is "complete", fetch the final report: `legal_research_get_deep_research_report(conversation_id)`
|
||||
- The report is the `answer_text` field
|
||||
- This is the final output of the research lifecycle. No further tool calls are required.
|
||||
- If the user asks a follow-up question on the same topic, use follow_up_deep_research with the same conversation_id rather than starting a fresh research session.
|
||||
|
||||
#### Rendering
|
||||
|
||||
- Paste the contents of `answer_text` into your response with no edits, additions, removals, or restructuring. The payload contains markdown, HTML anchors, inline anchor citations, blockquoted source excerpts, and horizontal rules — every element is intentional and must remain.
|
||||
|
||||
## Helpful information
|
||||
|
||||
If the system fails or the user has questions about access, share the following:
|
||||
|
||||
- Support email: cocounselsupport@tr.com
|
||||
- Subscription required: CoCounsel Legal subscription with the MCP connector enabled for the user's account. Direct entitlement or access questions to cocounselsupport@tr.com.
|
||||
- Provider: Thomson Reuters
|
||||
- Relevant policies:
|
||||
- Privacy: https://www.thomsonreuters.com/en/privacy-statement.html
|
||||
- Terms: https://www.thomsonreuters.com/en/terms-of-use.html
|
||||
- Accessibility: https://www.thomsonreuters.com/en/policies/accessibility.html
|
||||
Loading…
Add table
Add a link
Reference in a new issue