Skip to content
cccskills
FreePublished on GitHub

vendor-check

Review a vendor’s agreements across connected contract systems, customer records, email, document storage, and chat. Consolidate signing status, key terms, missing agreements, renewal deadlines, and obligations that may continue after expiration into one report.

OriginalShow the original 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.

Works withAWS
See how to install

Good for

  • Check agreement coverage before onboarding a vendor
  • Review contracts before a vendor renewal
  • Identify missing master, data processing, or work agreements
  • Check expirations and obligations that survive contract end

Files included (1)

  • SKILL.md5.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

/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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Review a design or web page against WCAG 2.1 AA, an accessibility standard. Organize findings on contrast, keyboard access, forms, and screen reader behavior, with severity levels and practical recommendations for fixes.

  • Review accessibility before design handoff
  • Check text and interface color contrast
  • Review keyboard navigation and focus behavior
anthropics/knowledge-work-plugins30.4KUpdated Oct 19, 2026

account-context

FreeSummary

Build a single brief on an existing customer using available sales records, emails, documents, call notes, and internal chat. Understand the current situation, key contacts, recent discussions, and gaps that may need attention.

  • Preparing for a meeting with an existing customer
  • Catching up on an account during a handover
  • Reviewing recent discussions and stalled opportunities
anthropics/knowledge-work-plugins30.4KUpdated Oct 19, 2026

account-plan

FreeSummary

Build or refresh a strategic customer account plan from sales records, emails, and meeting transcripts. Organize goals, stakeholders, growth opportunities, risks, and dated actions into a document, then sync approved highlights to the customer relationship management system.

  • Creating a quarterly plan for a key customer
  • Refreshing an existing account plan
  • Reviewing stakeholder coverage and growth opportunities
anthropics/knowledge-work-plugins30.4KUpdated Oct 19, 2026

account-research

FreeSummary

Research prospective companies and contacts, check existing customer records, and assess fit against your ideal customer profile. Receive a sourced brief covering recent developments, likely priorities, outreach talking points, and a suggested next step.

  • Researching a company before a sales approach
  • Checking existing account records and ownership
  • Assessing fit against your ideal customer profile
anthropics/knowledge-work-plugins30.4KUpdated Oct 19, 2026

account-research

FreeSummary

Research sales accounts using Common Room data to summarize company details, buying signals, ownership, and key contacts. Answer specific questions directly or prepare a broader briefing with evidence-based next steps, clearly identifying missing information.

  • Prepare a company briefing before a sales conversation
  • Check buying signals and recent account activity
  • Find account owners and key contacts
anthropics/knowledge-work-plugins30.4KUpdated Oct 19, 2026

account-tiering

FreeSummary

Score and group accounts by customer fit and engagement, such as recent contact and open sales opportunities. Identify where to focus sales effort, choose next actions, and spot promising accounts with neglected outreach or missing information.

  • Prioritize a portfolio of assigned accounts
  • Find strong-fit accounts that need outreach
  • Identify promising accounts with no recent activity
anthropics/knowledge-work-plugins30.4KUpdated Oct 19, 2026

See all skills by anthropics

Report a problem with this skill