vendor-check
anthropics/knowledge-work-plugins
Consolidate vendor agreements across CLM, CRM, email, and documents with gap analysis and deadline alerts.
What is vendor-check?
Searches connected systems (CLM, CRM, email, document storage, chat) to compile a complete view of all agreements with a vendor, identifies missing documents, and flags upcoming expirations. Use when onboarding or renewing a vendor, or when you need to verify what's signed and what's still needed.
- Search CLM, CRM, email, documents, and chat systems for vendor agreements
- Compile agreement status (active, expired, in negotiation, pending signature)
- Identify gaps in required agreements (MSA, DPA, SOW, NDA, SLA, insurance certificates)
- Flag agreements expiring within 90 days and auto-renewal terms
- Report surviving obligations in expired agreements
- Handle vendor name variations and parent/subsidiary relationships
How to install vendor-check
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill vendor-check- At least one connected system (CLM, CRM, email, documents, or chat) configured via MCP connectors
How to use vendor-check
- 1.Run /vendor-check [vendor name] with the vendor's legal name or common trade name
- 2.Clarify the vendor if the name is ambiguous (e.g., parent vs. subsidiary)
- 3.Review the consolidated report showing all agreements found across systems
- 4.Check the gap analysis section to identify missing required agreements
- 5.Note any agreements expiring within 90 days in the Upcoming Actions section
- 6.Verify findings against original documents with qualified legal professionals
Use cases
- Onboarding a new vendor and verifying all required agreements are in place
- Renewing an existing vendor relationship and checking expiration dates
- Consolidating scattered agreements before a contract review or audit
- Identifying missing Data Processing Agreements (DPA) for vendors handling personal data
- Checking for approaching renewal deadlines and auto-renewal notice periods
- Legal and contracts teams
- Procurement and vendor management professionals
- Compliance officers
- Business operations managers overseeing vendor relationships
vendor-check FAQ
The skill searches all connected systems (CLM, CRM, email, documents, chat) in priority order and consolidates results into one report. If a system is not connected, it will be noted so you know what was and wasn't searched.
No. The skill assists with legal workflows by organizing and reporting agreement status, but does not provide legal advice. Always verify results against original documents with qualified legal professionals.
The skill will report that clearly and ask if you have agreements stored elsewhere. You can then manually check your systems or provide additional context.
The skill recognizes common variations like full legal names vs. trade names (e.g., 'Alphabet Inc.' vs. 'Google') and abbreviations (e.g., 'AWS' vs. 'Amazon Web Services'). It will ask you to clarify if the name is ambiguous.
It lists standard agreement types (NDA, MSA, DPA, SOW, SLA, insurance certificates) and flags which are found versus missing, helping you identify what still needs to be executed or obtained.
Full instructions (SKILL.md)
Source of truth, from anthropics/knowledge-work-plugins.
name: vendor-check description: Check the status of existing agreements with a vendor across all connected systems — CLM, CRM, email, and document storage — with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, when you need a consolidated view of what's signed and what's missing (MSA, DPA, SOW), or when checking for approaching expirations and surviving obligations. argument-hint: "[vendor name]"
/vendor-check -- Vendor Agreement Status
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Check the status of existing agreements with a vendor across all connected systems. Provides a consolidated view of the legal relationship.
Important: This command assists with legal workflows but does not provide legal advice. Agreement status reports should be verified against original documents by qualified legal professionals.
Invocation
/vendor-check [vendor name]
If no vendor name is provided, prompt the user to specify which vendor to check.
Workflow
Step 1: Identify the Vendor
Accept the vendor name from the user. Handle common variations:
- Full legal name vs. trade name (e.g., "Alphabet Inc." vs. "Google")
- Abbreviations (e.g., "AWS" vs. "Amazon Web Services")
- Parent/subsidiary relationships
Ask the user to clarify if the vendor name is ambiguous.
Step 2: Search Connected Systems
Search for the vendor across all available connected systems, in priority order:
CLM (Contract Lifecycle Management) -- If Connected
Search for all contracts involving the vendor:
- Active agreements
- Expired agreements (last 3 years)
- Agreements in negotiation or pending signature
- Amendments and addenda
CRM -- If Connected
Search for the vendor/account record:
- Account status and relationship type
- Associated opportunities or deals
- Contact information for vendor's legal/contracts team
Email -- If Connected
Search for recent relevant correspondence:
- Contract-related emails (last 6 months)
- NDA or agreement attachments
- Negotiation threads
Documents (e.g., Box, Egnyte, SharePoint) -- If Connected
Search for:
- Executed agreements
- Redlines and drafts
- Due diligence materials
Chat (e.g., Slack, Teams) -- If Connected
Search for recent mentions:
- Contract requests involving this vendor
- Legal questions about the vendor
- Relevant team discussions (last 3 months)
Step 3: Compile Agreement Status
For each agreement found, report:
| Field | Details |
|---|---|
| Agreement Type | NDA, MSA, SOW, DPA, SLA, License Agreement, etc. |
| Status | Active, Expired, In Negotiation, Pending Signature |
| Effective Date | When the agreement started |
| Expiration Date | When it expires or renews |
| Auto-Renewal | Yes/No, with renewal term and notice period |
| Key Terms | Liability cap, governing law, termination provisions |
| Amendments | Any amendments or addenda on file |
Step 4: Gap Analysis
Identify what agreements exist and what might be missing:
## Agreement Coverage
[CHECK] NDA -- [status]
[CHECK/MISSING] MSA -- [status or "Not found"]
[CHECK/MISSING] DPA -- [status or "Not found"]
[CHECK/MISSING] SOW(s) -- [status or "Not found"]
[CHECK/MISSING] SLA -- [status or "Not found"]
[CHECK/MISSING] Insurance Certificate -- [status or "Not found"]
Flag any gaps that may be needed based on the relationship type (e.g., if there is an MSA but no DPA and the vendor handles personal data).
Step 5: Generate Report
Output a consolidated report:
## Vendor Agreement Status: [Vendor Name]
**Search Date**: [today's date]
**Sources Checked**: [list of systems searched]
**Sources Unavailable**: [list of systems not connected, if any]
## Relationship Overview
**Vendor**: [full legal name]
**Relationship Type**: [vendor/partner/customer/etc.]
**CRM Status**: [if available]
## Agreement Summary
### [Agreement Type 1] -- [Status]
- **Effective**: [date]
- **Expires**: [date] ([auto-renews / does not auto-renew])
- **Key Terms**: [summary of material terms]
- **Location**: [where the executed copy is stored]
### [Agreement Type 2] -- [Status]
[etc.]
## Gap Analysis
[What's in place vs. what may be needed]
## Upcoming Actions
- [Any approaching expirations or renewal deadlines]
- [Required agreements not yet in place]
- [Amendments or updates that may be needed]
## Notes
[Any relevant context from email/chat searches]
Step 6: Handle Missing Sources
If key systems are not connected via MCP:
- No CLM: Note that no CLM is connected. Suggest the user check their CLM manually. Report what was found in other systems.
- No CRM: Skip CRM context. Note the gap.
- No Email: Note that email was not searched. Suggest the user search their email for "[vendor name] agreement" or "[vendor name] NDA".
- No Documents: Note that document storage was not searched.
Always clearly state which sources were checked and which were not, so the user knows the completeness of the report.
Notes
- If no agreements are found in any connected system, report that clearly and ask the user if they have agreements stored elsewhere
- For vendor groups (e.g., a vendor with multiple subsidiaries), ask whether the user wants to check a specific entity or the entire group
- Flag any agreements that are expired but may still have surviving obligations (confidentiality, indemnification, etc.)
- If an agreement is approaching expiration (within 90 days), highlight this prominently
Related skills
More from anthropics/knowledge-work-plugins and the wider catalog.

vendor-review
Structured vendor evaluation covering cost, risk, and recommendation for procurement decisions.

view-pdf
Interactive PDF viewer for visual collaboration—annotate, highlight, fill forms, and place signatures in real-time.

weekly-prep-brief
Generate a comprehensive weekly briefing for all external calls in the next 7 days with account and contact research.

write-query
Write optimized SQL queries for your dialect with best practices and performance tuning.

write-spec
Transform vague ideas into structured feature specs and PRDs with goals, requirements, and success metrics.

zoom-apps-sdk
Reference skill for Zoom Apps SDK. Use after routing to an in-client app workflow when building web apps that run inside Zoom meetings, webinars, the main client, or Zoom Phone.