Agent skill · operations · borghei
vendor-management
Vendor lifecycle — weighted selection scorecards, risk tiering, renewal and notice-deadline tracking, spend concentration, and SLA credits. Use when selecting a vendor, preparing a renewal, or reviewing a vendor portfolio.
Why this skill is useful
Adds a vendor scorecard script and structured workflows for vendor selection and management that are not commonly found in public resources.
What it needs
Requires python3 installed locally. About 8k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Vendor Management Covers the vendor lifecycle from selection to exit. Two failures dominate this discipline: tiering vendors by spend rather than by blast radius, and losing every point of renewal leverage to a missed notice deadline. This skill is built around preventing both. When to use this skill Selecting a vendor and needing a scorecard that survives scrutiny A renewal is approaching and the notice deadline needs to be found before it passes Reviewing the vendor portfolio for concentration, risk tier coverage, and consolidation Preparing a business review with SLA performance and credits owed A vendor is underperforming and the case needs to be built on trend, not anecdote Planning an exit and needing the sequence right Inputs the skill expects For selection: weighted criteria, must-have requirements, and 0-10 scores per vendor with evidence For the portfolio: annual spend, category, renewal date, notice days, and auto-renew flag per vendor Risk inputs per vendor: data classification, business criticality, alternative availability, subprocessor use Internal owner per contract For SLA reporting: committed metrics with target, actual, direction, credit tiers, and prior-period history Annual contract value and the contractual credit cap Clarify First Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Is the notice deadline known, or only the renewal date? — the notice deadline is what constrains action, and missing it removes all leverage for a full term [ ] Were the scoring weights set before any vendor was scored? — weights chosen after seeing candidates produce a justification, not a decision [ ] What does this vendor actually hold or touch? — data sensitivity and criticality drive the risk tier; spend does not [ ] Which must-haves are genuinely pass/fail? — every entry on that list eliminates a candidate, so preferences belong in the weighted criteria Stop rule: ask only the 2-3 that most change the output. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/vendor-management