vendor-check SKILL.md skillA
vendor-check from alebgl77/claude-inc is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add alebgl77/claude-inc/vendor-check@git:20260711.13c718dPins git:20260711.13c718d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- alebgl77/claude-inc
- Path
skills/vendor-check/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260711.13c718d, committed Jul 11, 2026
- Size
- 4,799 bytes
- Repository stars
- 22
- License
- MIT
Vendor agreement status check — inventories what exists versus what is needed (MSA, DPA, SOW, SLA, insurance certs, security review), builds a gap analysis table, runs an expiration and renewal radar with dates and notice windows, notes surviving obligations, and delivers an onboarding go/no-go checklist. Use when the user says 'are we set up with this vendor', 'what do we have signed with them', 'can we onboard them', or ahead of a renewal or offboarding.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Vendor Check — Vendor Vetter > "Vet a vendor" Answers one question fast: can we safely start (or keep) working with this vendor, and what paper is missing? Works from provided documents, pasted excerpts, or the user's answers. ## When to use - "Do we have paper with Acme?" — inventory before new spend - "Can we onboard this vendor by Monday?" — the go/no-go call - "What renews with them this quarter?" — expiration radar - "We're dropping this vendor — what survives termination?" — offboarding read - A found agreement with ugly clauses goes deeper via `review-contract` ## Workflow 1. Profile the engagement: what the vendor does, what data or systems they touch, annual spend, business criticality, jurisdictions. 2. Derive the "needed" list from that profile: MSA always; DPA whenever personal data flows; SOW per work package; SLA when availability matters; insurance certificates (types and minimums) proportional to risk; security review when they touch systems or data. 3. Inventory what exists from attached files, pasted excerpts, and the user's answers: document, status (signed / draft / expired / missing), signature date, term. …
Read the whole file at its exact version.
How to install
mdr add alebgl77/claude-inc/vendor-check@sha256:f4b1f947c0605a5aThe line at the top of this page pins the label git:20260711.13c718d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_d5ariv6t24n5clur)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 11, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4799 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
alebgl77/claude-inc · 22 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_d5ariv6t24n5clur GET https://markdownregistry.com/api/v1/resolve?ref=alebgl77/claude-inc/vendor-check GET https://markdownregistry.com/api/v1/blob/f4b1f947c0605a5a0827e6be85afbe47e1fdc084c23474a91145fc86fd3d1f34
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.