Vendor Check
Get one consolidated report of a vendor’s signed agreements, gaps, and renewal deadlines across CLM, CRM, email, and document storage before you onboard or renew.
Overview
Vendor-check is an agent skill most often used in Operate (also Validate, Build) that consolidates a vendor’s agreement status, document gaps, and renewal deadlines across CLM, CRM, email, and file storage.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill vendor-checkWhat is this skill?
- Runs /vendor-check for a named vendor with optional argument-hint for vendor name
- Searches CLM, CRM, email, and document storage for agreement artifacts and correspondence
- Gap analysis for standard agreement types: MSA, DPA, and SOW
- Surfaces approaching expirations and surviving obligations in one consolidated view
- Resolves legal vs trade names and parent/subsidiary ambiguity before searching
- Covers four connected system classes: CLM, CRM, email, and document storage
- Standard gap checklist includes MSA, DPA, and SOW agreement types
Adoption & trust: 1.5k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know you work with a vendor but cannot quickly see which MSAs, DPAs, or SOWs are signed, which are missing, or what expires next across disconnected systems.
Who is it for?
Indie operators and tiny teams with CLM, CRM, email, or doc connectors who need a repeatable pre-renewal or pre-onboarding contract snapshot.
Skip if: Builders without connected business systems, one-person hacks with no formal vendor stack, or anyone treating the output as binding legal advice without attorney review.
When should I use this skill?
Onboarding or renewing a vendor, when you need a consolidated view of what is signed versus missing (MSA, DPA, SOW), or when checking approaching expirations and surviving obligations.
What do I get? / Deliverables
You receive a consolidated vendor agreement status report with gap analysis and upcoming deadlines to verify against source documents before onboarding, renewal, or legal review.
- Consolidated vendor agreement status report across connected systems
- Gap analysis for missing or incomplete MSA, DPA, and SOW coverage
- List of upcoming expirations and noted surviving obligations for verification
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Vendor agreement hygiene is ongoing business operations—renewals, missing DPAs, and expiring MSAs surface after you are already running with suppliers, not only at first purchase. Iterate fits recurring contract reviews, gap fixes, and deadline-driven renewals rather than a one-off build or launch task.
Where it fits
Before committing to a new SaaS vendor, run vendor-check to see whether an MSA or DPA already exists or must be negotiated.
After connecting CLM and CRM, use vendor-check to prove cross-system search returns the same agreement set your ops team expects.
At renewal season, pull expirations and surviving obligations for a key supplier without opening four separate tools.
How it compares
Use instead of manually searching CLM, CRM, inboxes, and drives separately when you need one vendor-wide agreement picture.
Common Questions / FAQ
Who is vendor-check for?
Solo builders and small teams managing real vendor relationships who already use or plan to connect CLM, CRM, email, and document storage and want a single agreement-status pass before renewals or onboarding.
When should I use vendor-check?
Use it when onboarding or renewing a vendor in Validate, when wiring integrations in Build to search connected stores, or during Operate when you need MSA/DPA/SOW gap analysis and expiration checks across systems.
Is vendor-check safe to install?
Treat it as a workflow that may read sensitive contract and CRM data via your connectors; review the Security Audits panel on this Prism page and limit permissions to systems you trust before running it on production tenants.
SKILL.md
READMESKILL.md - Vendor Check
# /vendor-check -- Vendor Agreement Status > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../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