vendor-check
Skill1 starsChanged 7 months agoMITView on GitHub
Check the status of existing agreements with a vendor across CLM, CRM, email, and document storage -- with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, or when checking for expiring contracts and missing documents. Trigger with "vendor check", "check vendor status", "what agreements do we have with", or "vendor due diligence".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- alebgl77/claude-inctheir own version, first seen Jul 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- anthropics/knowledge-work-plugins★ 36ksame name
- alebgl77/claude-inc★ 21same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Search connected systems to build a consolidated view of the agreement relationship with a vendor.
- Distinctive: line 71
Action: Search all systems for CloudCorp agreements.
- Distinctive: line 78
Search by multiple identifiers: vendor name, domain, entity name, and aliases.
- Distinctive: line 79
Always check for a DPA when the vendor processes any personal data -- most commonly missing agreement.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Vendor Agreement Check
Search connected systems to build a consolidated view of the agreement relationship with a vendor. Identify active agreements, coverage gaps, and upcoming deadlines.
Workflow
Step 1: Search Connected Systems
Query CLM (all agreement types by vendor name/domain/entity), CRM (vendor records, contacts, deal history), email (recent contract correspondence), document storage (filed agreements, certificates), and procurement (POs, approved vendor list, spend data).
Step 2: Inventory Existing Agreements
Catalog each agreement: type (MSA, NDA, SOW, DPA, SLA, Order Form, Amendment, BAA), status, key dates (effective, expiration, renewal, notice deadline), auto-renewal terms, financial terms, and key contacts.
Step 3: Gap Analysis
Identify: missing DPA when personal data is processed, expired insurance certificates or SOC 2 reports, unsigned agreements, MSA/SOW term mismatches, missing vendor security questionnaire.
Step 4: Deadline and Renewal Analysis
Map: agreements expiring within 90 days, auto-renewal opt-out deadlines, rate review windows, compliance attestation refresh dates.
Output Format
## Vendor Agreement Status
**Vendor**: [Name] | **Date**: [YYYY-MM-DD]
**Overall Status**: [CURRENT / GAPS IDENTIFIED / CRITICAL GAPS]
### Agreement Inventory
| # | Type | Title | Status | Effective | Expires | Auto-Renew | Owner |
|---|------|-------|--------|-----------|---------|------------|-------|
| 1 | MSA | Master Services | Active | 2023-01-15 | 2025-01-14 | Yes-60d | [Name] |
| 4 | DPA | Data Processing | MISSING | -- | -- | -- | -- |
### Gap Analysis
| # | Gap | Severity | Action |
|---|-----|----------|--------|
| 1 | No DPA despite processing PII | HIGH | Execute immediately |
### Upcoming Deadlines
| Date | Item | Action Required |
|------|------|----------------|
| 2024-11-15 | MSA opt-out deadline | Decide: renew or renegotiate |Examples
User: "What agreements do we have with CloudCorp?" Action: Search all systems for CloudCorp agreements. Produce inventory showing MSA, SOWs, NDA, and missing DPA. Flag the DPA gap and MSA renewal deadline.
User: "We're renewing with DataVendor -- what's the current state?" Action: Pull full inventory, check for expired compliance documents, identify renewal notice deadline, flag gaps to address during negotiation.
Best Practices
- Search by multiple identifiers: vendor name, domain, entity name, and aliases.
- Always check for a DPA when the vendor processes any personal data -- most commonly missing agreement.
- Flag auto-renewal deadlines at least 90 days out for negotiation leverage.
- Note the difference between "not found" and "does not exist" -- agreements may exist outside searched systems.
- Prioritize gaps by legal risk: a missing DPA with an active data processor is higher priority than an expired insurance certificate.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

