Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or assess concentration and continuity risk.
npx skills add https://github.com/cbrock84/headcount --skill vendor-management
Written before any demo: what the vendor must do, the volume and service level required, what must
integrate with what, and the constraints that are genuinely non-negotiable.
Requirements written after seeing a product describe that product. This is the most common way
selections are decided before they are run.
Separate must-have from nice-to-have and weight them in advance. Weighting after scoring is
how a preferred vendor wins a process designed to be objective.
volume tells you nothing about whether it scales.
spikes, or an integration times out?
responsiveness, and whether you are a meaningful customer to them. Being a rounding error to your
critical supplier is a risk in itself.
ongoing effort to operate it. License cost is frequently the smaller half.
Beyond the legal review: service levels with real remedies, support response times by severity,
data export in a usable format on demand, notice periods that give you time to migrate, and price
protection at renewal. The absence of the last two is what makes exit expensive later.
reports mark their own work.
the most common and most avoidable vendor loss.
Know which vendors you could not operate without and what happens if one fails, is acquired, or
triples its price. For each, know the exit path and roughly what it costs — an exit plan that has
never been thought through is not an option, it is a hope.
Maintain your own copy of your data continuously where the vendor holds anything critical.
Take cbrock84/vendor-management from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.