Token导航 LogoToken导航

Agent Skill · 研究检索

vendor-check(供应商检查)

vendor-check 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

vendor-check 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为调用外部服务;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 7,484。

总安装 18,864周安装 786GitHub Stars 11,688下载 6,288核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:vendor-check(供应商检查)
来源仓库:https://github.com/anthropics/knowledge-work-plugins
仓库路径:skills/vendor-check
安装命令:
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill vendor-check
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill vendor-check

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

查找、检索和筛选相关信息,快速定位候选结果。适用于在 Codex、Claude、Cursor、Gemini CLI 中根据关键词或任务场景进行信息筛选的场景。通过 GitHub 安装,结合来源仓库和原始 README 核验具体用法。安装前需确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

vendor-check 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/vendor-check

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/anthropics/knowledge-work-plugins --skill vend…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

vendor-check 怎么安装?

在终端执行 npx skills add https://github.com/anthropics/knowledge-work-plugins --skill vendor-check。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

vendor-check 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

vendor-check 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

vendor-check 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

vendor-check 用的人多吗?

公开数据是累计安装 18,864 次,近一周安装 786 次,下载 6,288 次,GitHub 11,688 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

vendor-check 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 来源仓库有 11,688 星,维护活跃度相对可查。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
vendor-check

供应商检查 · 本页

18,86411,688调用外部服务未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

/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

平台分布

Codex

36.91%
按下载量换算2,321

Claude

27.07%
按下载量换算1,702

Cursor

19.11%
按下载量换算1,202

Gemini CLI

9.6%
按下载量换算604

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills