Agent skill

Vendor Management

by cbrock84 in cbrock84/headcount

Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit.

MITAuto-check passedBusiness, Finance & HR

Install Vendor Management

skills CLI
$ npx skills add cbrock84/headcount --skill vendor-management -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cbrock84/headcount vendor-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/operations/skills/vendor-management .claude/skills/vendor-management && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vendor-management
GitHub stars
2k
Token cost
~889 tokens
SKILL.md length
482 words
Files
2 (incl. references)
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit.

  • Tasks that involve Vendor and procurement management
  • SKILL.md covers Define requirements before…, Evaluating, Terms that matter operationally and Managing, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vendor Management is an agent skill from cbrock84/headcount. 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.

Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

It sits in Business, Finance & HR, covering Vendor and procurement management. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

When your agent uses it

  • Tasks that involve Vendor and procurement management

Example prompts

  • “/vendor-management”

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vendor Management loads about 889 tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 95 tokens; SKILL.md has 482 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~95
When it runs · the whole SKILL.md, loaded when a task matches
~889
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 482 words, ~889 tokens.

Download SKILL.mdSave it as .claude/skills/vendor-management/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
vendor-management
description
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.

Vendor management

Define requirements before looking at options

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.

Evaluating

  • Reference checks with customers of your size and use case. A reference running a tenth of your volume tells you nothing about whether it scales.
  • Test the actual failure modes, not the demo path. What happens when data is malformed, volume spikes, or an integration times out?
  • Assess the vendor, not just the product — financial stability, roadmap direction, support responsiveness, and whether you are a meaningful customer to them. Being a rounding error to your critical supplier is a risk in itself.
  • Total cost including your side: implementation, integration, migration, training, and the ongoing effort to operate it. License cost is frequently the smaller half.

Terms that matter operationally

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.

Managing

  • One named owner on your side. Vendors without an internal owner drift and renew automatically.
  • Review on a schedule against the service levels, with evidence. Vendor-supplied performance reports mark their own work.
  • Log issues. At renewal, a documented pattern is leverage; a recollection is not.
  • Diarize renewals well before the notice deadline. Auto-renewal past an unnoticed deadline is the most common and most avoidable vendor loss.
Show full SKILL.md (177 more words)Show less

Concentration and exit

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.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Sign before you know what leaving costs — data export, notice period, transition support.
  • Let the vendor write the requirements you evaluate them against.
  • Reach a renewal date without having started the renewal. The auto-renew clause is their leverage.
  • Concentrate a critical dependency on one vendor without saying so out loud and pricing the risk.

© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/operations/skills/vendor-management of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Vendor Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vendor Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vendor Management this skillcbrock84/headcount2k—~889Automated safety check: PassMIT
Serenity Alphahaskaomni/serenity-skill633—~2.6kAutomated safety check: PassMIT
Scorecard Matrixpnp/sharepoint-skills133—~1.9kAutomated safety check: PassMIT
Oma Imagefirst-fluke/oh-my-agent1.3k—~2kAutomated safety check: PassMIT
Buyer Job Intent Analysiselvisun/newsjack1.5k—~1.4kAutomated safety check: PassMIT
Master Builderibuilder/massing122—~2.6kAutomated safety check: PassMIT

Similar skills

  • Serenity Alpha

    haskaomni/serenity-skill

    Translate market-moving news into investable alpha hypotheses by mapping observed demand changes to revenue lines, supply chains, small-cap financial elasticity, market misclassification, validation…

    633 GitHub stars~2.6k tokensUpdated 2 mo ago
    Business, Finance & HRAuto-check passed
  • Scorecard Matrix

    pnp/sharepoint-skills

    Generates a polished, self-contained HTML heatmap scorecard — a weighted comparison matrix where entities (rows) are scored across dimensions (columns), with computed totals, rank badges, and a…

    133 GitHub stars~1.9k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed
  • Oma Image

    first-fluke/oh-my-agent

    Generate raster images or reference-guided variations through the OMA image CLI.

    1.3k GitHub stars~2k tokensUpdated today
    Business, Finance & HRAuto-check passed
  • Recover source-bound buyer jobs, struggling moments, desired progress, forces, workarounds, information acts, journey states, criteria, constraints, roles, locales, and authentic language.

    1.5k GitHub stars~1.4k tokensUpdated 4 days ago
    Business, Finance & HRAuto-check passed
  • Master Builder

    ibuilder/massing

    Reason like a master builder — one mind holding an entire built-asset project from raw land through design, construction, handover, operations, and disposition, anywhere in the world.

    122 GitHub stars~2.6k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed
  • Energy Procurement

    affaan-m/ECC

    Procure electricity and natural gas for commercial and industrial facilities: tariff and rate-schedule optimization, demand-charge mitigation, supplier RFPs, fixed/index/block-and-index hedging…

    276k GitHub starsUsed in 4 repos~7.4k tokens
    Business, Finance & HRAuto-check passed

More from cbrock84/headcount

All 178 skills in this repo
  • Agent Hierarchy

    cbrock84/headcount

    Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…

    2k GitHub stars~1.2k tokensUpdated 23 days ago
    Auto-check passed
  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 23 days ago
    Auto-check passed
  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 23 days ago
    Auto-check passed
  • Activation

    cbrock84/headcount

    Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.

    2k GitHub stars~865 tokensUpdated 23 days ago
    Auto-check passed
  • AI ML Governance

    cbrock84/headcount

    Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.

    2k GitHub stars~1k tokensUpdated 23 days ago
    Auto-check passed
  • AI Research Analyst

    cbrock84/headcount

    Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.

    2k GitHub stars~916 tokensUpdated 23 days ago
    Auto-check passed

Questions about Vendor Management

What does Vendor Management do?

Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Vendor Management is an agent skill from cbrock84/headcount. Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit.

When should I use Vendor Management?

Vendor Management fits situations like: tasks that involve Vendor and procurement management.

How do I install Vendor Management in Claude Code?

Run `npx skills add cbrock84/headcount --skill vendor-management -a claude-code`. Or copy the skill folder (plugins/operations/skills/vendor-management in cbrock84/headcount) into .claude/skills/vendor-management in your project. Claude Code loads it when a task matches its description.

How do I install Vendor Management in Codex?

Run `npx skills add cbrock84/headcount --skill vendor-management -a codex`. Or copy the skill folder (plugins/operations/skills/vendor-management in cbrock84/headcount) into .agents/skills/vendor-management in your project. Codex loads it when a task matches its description.

Can I use Vendor Management in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill vendor-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vendor-management, .gemini/skills/vendor-management, .github/skills/vendor-management and .opencode/skills/vendor-management in your project.

What does Vendor Management need to run?

SKILL.md names no scripts, command-line tools or credentials: Vendor Management is instructions for the agent only.

Does Vendor Management access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vendor Management safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Vendor Management use?

Vendor Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vendor Management use?

About 889 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 473 tokens, read only when the agent opens those files.

What are the alternatives to Vendor Management?

Skills that share tags, products or a category with Vendor Management: Serenity Alpha (haskaomni/serenity-skill, 633 stars), Scorecard Matrix (pnp/sharepoint-skills, 133 stars), Oma Image (first-fluke/oh-my-agent, 1.3k stars) and Buyer Job Intent Analysis (elvisun/newsjack, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vendor Management?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.

Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.