Vendor Agreement Check

/vendor-check -- Vendor Agreement Status

Check the status of existing agreements with a vendor from the documents and records the user provides. Provides a consolidated view of the legal relationship. Ask the user to upload or paste the relevant agreements, contract tracker exports, or correspondence.

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: Review the Material the User Provides

Ask the user to upload or paste whatever they have on the vendor, then review it across these categories:

Agreements / contracts

Look across all agreements involving the vendor:

• Active agreements
• Expired agreements (last 3 years)
• Agreements in negotiation or pending signature
• Amendments and addenda

Account / relationship records

From any account or CRM export the user provides:

• Account status and relationship type
• Associated opportunities or deals
• Contact information for vendor's legal/contracts team

Correspondence

From any email or message threads the user pastes:

• Contract-related emails (last 6 months)
• NDA or agreement attachments
• Negotiation threads

Documents

From any executed files, redlines, or diligence materials the user uploads:

• Executed agreements
• Redlines and drafts
• Due diligence materials

Team discussions

From any chat/notes the user pastes:

• Contract requests involving this vendor
• Legal questions about the vendor
• Relevant team discussions

Step 3: Compile Agreement Status

For each agreement found, report:

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]

**Review Date**: [today's date]
**Material Reviewed**: [what the user provided]
**Not Provided**: [categories of material the user did not supply, 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 Material

If the user has not provided some categories of material:

• No agreements: Note that no executed agreements were provided. Ask the user to upload them, or report the gap based on what was supplied.
• No account/CRM records: Skip relationship context. Note the gap.
• No correspondence: Note that no email/message threads were provided. Suggest the user paste any relevant "[vendor name] agreement" or "[vendor name] NDA" threads.
• No supporting documents: Note that no additional documents were reviewed.

Always clearly state what material was reviewed and what was missing, so the user knows the completeness of the report.

Notes

• If no agreements are found in the material provided, report that clearly and ask the user if they have agreements stored elsewhere to upload
• 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

Zeplik output presentation

Present the final deliverable as a single polished artifact: clear headings, tables where the content is tabular, fenced code where it is code. Lead with the deliverable itself; keep process commentary to a single short line. If the skill produced multiple files or sections, end with a compact list of them with one-line purposes.