vendor-check

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/vendor-check -- Vendor Agreement Status

/vendor-check -- 供应商协议状态

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.
若您看到不熟悉的占位符或需要检查已连接的工具,请查看CONNECTORS.md
跨所有关联系统检查与供应商现有协议的状态,提供法律关系的统一视图。
重要提示:本命令仅协助处理法律工作流,不提供法律建议。协议状态报告应由合格的法律专业人员对照原始文件进行核实。

Invocation

调用方式

/vendor-check [vendor name]
If no vendor name is provided, prompt the user to specify which vendor to check.
/vendor-check [供应商名称]
若未提供供应商名称,将提示用户指定要检查的供应商。

Workflow

工作流程

Step 1: Identify the Vendor

步骤1:识别供应商

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.
接收用户提供的供应商名称,处理常见变体:
  • 完整法律名称与商号(例如:"Alphabet Inc." 与 "Google")
  • 缩写(例如:"AWS" 与 "Amazon Web Services")
  • 母公司/子公司关系
若供应商名称存在歧义,请用户进行澄清。

Step 2: Search Connected Systems

步骤2:搜索关联系统

Search for the vendor across all available connected systems, in priority order:
按优先级顺序在所有可用的关联系统中搜索供应商:

CLM (Contract Lifecycle Management) -- If Connected

CLM(合同生命周期管理)-- 若已连接

Search for all contracts involving the vendor:
  • Active agreements
  • Expired agreements (last 3 years)
  • Agreements in negotiation or pending signature
  • Amendments and addenda
搜索所有涉及该供应商的合同:
  • 有效协议
  • 已过期协议(近3年)
  • 协商中或待签署的协议
  • 修订案和附加条款

CRM -- If Connected

CRM -- 若已连接

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
搜索近期相关通信:
  • 合同相关邮件(近6个月)
  • NDA或协议附件
  • 协商线程

Documents (e.g., Box, Egnyte, SharePoint) -- If Connected

文档系统(如Box、Egnyte、SharePoint)-- 若已连接

Search for:
  • Executed agreements
  • Redlines and drafts
  • Due diligence materials
搜索:
  • 已签署的协议
  • 修改稿和草稿
  • 尽职调查材料

Chat (e.g., Slack, Teams) -- If Connected

聊天工具(如Slack、Teams)-- 若已连接

Search for recent mentions:
  • Contract requests involving this vendor
  • Legal questions about the vendor
  • Relevant team discussions (last 3 months)
搜索近期提及内容:
  • 涉及该供应商的合同请求
  • 关于该供应商的法律问题
  • 相关团队讨论(近3个月)

Step 3: Compile Agreement Status

步骤3:整理协议状态

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
针对找到的每个协议,报告以下信息:
字段详情
协议类型NDA、MSA、SOW、DPA、SLA、许可协议等
状态有效、已过期、协商中、待签署
生效日期协议开始日期
到期日期协议到期或续约日期
自动续约是/否,包含续约期限和通知期
关键条款责任上限、管辖法律、终止条款
修订案存档的任何修订案或附加条款

Step 4: Gap Analysis

步骤4:差距分析

Identify what agreements exist and what might be missing:
undefined
识别已存在的协议和可能缺失的协议:
undefined

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).
[已检查] NDA -- [状态] [已检查/缺失] MSA -- [状态或“未找到”] [已检查/缺失] DPA -- [状态或“未找到”] [已检查/缺失] SOW(s) -- [状态或“未找到”] [已检查/缺失] SLA -- [状态或“未找到”] [已检查/缺失] 保险凭证 -- [状态或“未找到”]

根据关系类型标记可能需要补充的差距(例如:若存在MSA但无DPA,且供应商处理个人数据)。

Step 5: Generate Report

步骤5:生成报告

Output a consolidated report:
undefined
输出统一报告:
undefined

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]
供应商:[完整法律名称] 关系类型:[供应商/合作伙伴/客户等] CRM状态:[若可用]

Agreement Summary

协议摘要

[Agreement Type 1] -- [Status]

[协议类型1] -- [状态]

  • 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]

[协议类型2] -- [状态]

[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]
undefined
[从邮件/聊天搜索中获取的相关背景信息]
undefined

Step 6: Handle Missing Sources

步骤6:处理缺失的来源

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.
若关键系统未通过MCP连接:
  • 无CLM:备注未连接CLM,建议用户手动检查其CLM系统,报告在其他系统中找到的内容。
  • 无CRM:跳过CRM相关内容,备注该差距。
  • 无邮件:备注未搜索邮件,建议用户在邮件中搜索“[供应商名称] 协议”或“[供应商名称] NDA”。
  • 无文档系统:备注未搜索文档存储系统。
需明确说明已检查哪些来源和未检查哪些来源,以便用户了解报告的完整性。

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
  • 若在所有关联系统中均未找到协议,请明确报告此情况,并询问用户是否在其他位置存储了协议
  • 对于供应商集团(例如:拥有多个子公司的供应商),询问用户是否要检查特定实体或整个集团
  • 标记已过期但仍有存续义务(保密、赔偿等)的协议
  • 若协议即将到期(90天内),请突出显示该信息