Vendor Check

by anthropicsae1513ea94dcNo license27K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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.

FeaturedInstructions onlyBusiness & Finance
AI-generated overview

Consolidates a vendor's agreement status across connected systems, with gap analysis and upcoming deadlines.

What it does
Searches connected systems such as CLM, CRM, email, document storage and chat for agreements involving a named vendor, then compiles each agreement's type, status, dates, auto-renewal terms and key provisions. It produces a consolidated report with a coverage gap analysis, upcoming actions and notes, and clearly states which sources were checked or unavailable. It assists with legal workflows but does not provide legal advice.
When to use it
Use when onboarding or renewing a vendor, or when you need a consolidated view of what is signed and what is missing, such as an MSA, DPA or SOW. Also useful for checking approaching expirations and surviving obligations.
Requirements
Requires an agent with MCP-connected systems such as CLM, CRM, email, document storage or chat; missing sources are reported as gaps. No scripts are shipped.

/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:

FieldDetails
Agreement TypeNDA, MSA, SOW, DPA, SLA, License Agreement, etc.
StatusActive, Expired, In Negotiation, Pending Signature
Effective DateWhen the agreement started
Expiration DateWhen it expires or renews
Auto-RenewalYes/No, with renewal term and notice period
Key TermsLiability cap, governing law, termination provisions
AmendmentsAny 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

Source and attribution

Source:anthropics/knowledge-work-pluginsinlegal/skills/vendor-checkat commitae1513e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from anthropics/knowledge-work-plugins

Ticket Deflector

anthropics

Featured

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

Awaiting classification27Kupdated today

Tax Season Organizer

anthropics

Featured

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

Awaiting classification27Kupdated today

Tax Prep

anthropics

Featured

Prepares tax materials from closed books: a quarterly estimated payment breakdown or a year-end 1099-NEC list and accountant packet.

Business & Finance27Kupdated today

Smb Onboard

anthropics

Featured

Guides a small-business owner through first-time setup: connecting tools, running a value-proof recipe, capturing business context, and setting a weekly…

Productivity & Workflow27Kupdated today

Smb Router

anthropics

Featured

Routes a small-business owner's request to the right plugin skill or command and explains what is available.

Productivity & Workflow27Kupdated today

Month End Prep

anthropics

Featured

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

Awaiting classification27Kupdated today