vendor-check by anthropics/knowledge-work-plugins
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill vendor-check如果您看到不熟悉的占位符或需要检查连接了哪些工具,请参阅 CONNECTORS.md。
检查与某个供应商在所有已连接系统中现有协议的状态。提供法律关系的综合视图。
重要提示:此命令协助法律工作流程,但不提供法律建议。协议状态报告应由合格的法律专业人员根据原始文件进行核实。
/vendor-check [供应商名称]
如果未提供供应商名称,则提示用户指定要检查的供应商。
接受用户提供的供应商名称。处理常见变体:
如果供应商名称不明确,请要求用户澄清。
按优先级顺序在所有可用的已连接系统中搜索该供应商:
搜索涉及该供应商的所有合同:
搜索供应商/账户记录:
搜索最近的相关通信:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
搜索:
搜索最近的提及:
对于找到的每个协议,报告:
| 字段 | 详情 |
|---|---|
| 协议类型 | NDA、MSA、SOW、DPA、SLA、许可协议等。 |
| 状态 | 有效、已过期、谈判中、待签署 |
| 生效日期 | 协议开始日期 |
| 到期日期 | 协议到期或续订日期 |
| 自动续订 | 是/否,包含续订期限和通知期 |
| 关键条款 | 责任上限、管辖法律、终止条款 |
| 修正案 | 存档的任何修正案或附录 |
识别存在哪些协议以及可能缺少哪些协议:
## 协议覆盖情况
[CHECK] NDA -- [状态]
[CHECK/MISSING] MSA -- [状态 或 "未找到"]
[CHECK/MISSING] DPA -- [状态 或 "未找到"]
[CHECK/MISSING] SOW(s) -- [状态 或 "未找到"]
[CHECK/MISSING] SLA -- [状态 或 "未找到"]
[CHECK/MISSING] 保险证书 -- [状态 或 "未找到"]
根据关系类型标记任何可能需要的缺口(例如,如果有 MSA 但没有 DPA,而供应商处理个人数据)。
输出综合报告:
## 供应商协议状态:[供应商名称]
**搜索日期**:[今天的日期]
**已检查的来源**:[已搜索的系统列表]
**不可用的来源**:[未连接的系统列表,如果有]
## 关系概览
**供应商**:[完整法定名称]
**关系类型**:[供应商/合作伙伴/客户等]
**CRM 状态**:[如果可用]
## 协议摘要
### [协议类型 1] -- [状态]
- **生效日期**:[日期]
- **到期日期**:[日期]([自动续订 / 不自动续订])
- **关键条款**:[重要条款摘要]
- **位置**:[已签署副本的存储位置]
### [协议类型 2] -- [状态]
[等等。]
## 差距分析
[已到位的协议与可能需要的协议对比]
## 即将采取的行动
- [任何即将到期的协议或续订截止日期]
- [尚未到位的必需协议]
- [可能需要的修正案或更新]
## 备注
[来自电子邮件/聊天搜索的任何相关上下文]
如果关键系统未通过 MCP 连接:
始终清楚说明检查了哪些来源以及未检查哪些来源,以便用户了解报告的完整性。
每周安装量
192
代码仓库
GitHub Stars
10.3K
首次出现
11 天前
安全审计
安装于
gemini-cli185
opencode184
codex184
cursor184
kimi-cli183
amp183
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.
/vendor-check [vendor name]
If no vendor name is provided, prompt the user to specify which vendor to check.
Accept the vendor name from the user. Handle common variations:
Ask the user to clarify if the vendor name is ambiguous.
Search for the vendor across all available connected systems, in priority order:
Search for all contracts involving the vendor:
Search for the vendor/account record:
Search for recent relevant correspondence:
Search for:
Search for recent mentions:
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 |
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).
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]
If key systems are not connected via MCP:
Always clearly state which sources were checked and which were not, so the user knows the completeness of the report.
Weekly Installs
192
Repository
GitHub Stars
10.3K
First Seen
11 days ago
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
gemini-cli185
opencode184
codex184
cursor184
kimi-cli183
amp183
通过 LiteLLM 代理让 Claude Code 对接 GitHub Copilot 运行 | 高级变通方案指南
31,600 周安装
Spring Boot Saga模式:微服务分布式事务解决方案与实现指南
398 周安装
CI/CD 最佳实践指南:自动化流水线、部署策略与DevOps核心原则
407 周安装
3D网页体验开发指南:Three.js、React Three Fiber与WebGL优化实战
400 周安装
WPS表格智能助手:Excel公式生成、数据清洗与错误诊断全攻略
410 周安装
Awwwards作品集首页模板 - Next.js + GSAP + Locomotive Scroll 流畅滚动动画实现
402 周安装
病毒式传播框架:STEPPS原则设计口碑传播与产品传染性 | 营销方法论
425 周安装