Localized reading guide
vendor-checkPurpose, usage and source
Check the status of existing agreements with a vendor across all connected systems — CLM, CRM, email, and document storage — with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, when you need a consolidated view of what's signed and what's missing (MSA, DPA, SOW), or when checking for approaching expirations and surviving obligations.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
legal/skills/vendor-check/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Documents
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Check the status of existing agreements with a vendor across all connected systems — CLM, CRM, email, and document storage — with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, when you need a consolidated view of what's signed and what's missing (MSA, DPA, SOW), or when checking for approaching expirations and surviving obligations.
How the upstream workflow works
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") Ask the user to clarify if the vendor name is ambiguous.
Upstream passage · L25 ↗Step 2: Search Connected Systems
Search for the vendor across all available connected systems, in priority order:
Upstream passage · L34 ↗/vendor-check [vendor name]Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- /vendor-check -- Vendor Agreement Status
- Invocation
- Step 1: Identify the Vendor
- Step 2: Search Connected Systems
- CLM (Contract Lifecycle Management) -- If Connected
- CRM -- If Connected
- Email -- If Connected
- Documents (e.g., Box, Egnyte, SharePoint) -- If Connected
- Chat (e.g., Slack, Teams) -- If Connected
- Step 3: Compile Agreement Status
- Step 4: Gap Analysis
- Step 5: Generate Report
- Step 6: Handle Missing Sources
- Notes
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
38be57a5e9e959874d2cb78e8493211664bc452e6225cb5bdbb8b12e6f444d2e