Agent skill
vendor-evaluation
Compare vendors or quotes for a small business purchase — insurance, software, equipment, services — using a scoring rubric and produce a clear recommendation.
Filed under Calls, demos and discovery.
From GTMify/aigtm · 64 skill entries · 25 · pushed 2026-10-04
What it does when it runs
Compare vendors or quotes for a small business purchase — insurance, software, equipment, services — using a scoring rubric and produce a clear recommendation. Use when the user says 'compare these vendors', 'which one should I pick', 'evaluate these quotes', 'help me choose', or pastes multiple proposals or quotes.
Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/GTMify/aigtm.git /tmp/aigtm git -C /tmp/aigtm sparse-checkout set "skills/vendor-evaluation" mkdir -p ~/.claude/skills/vendor-evaluation cp -R "/tmp/aigtm/skills/vendor-evaluation/." ~/.claude/skills/vendor-evaluation/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from GTMify/aigtm/blob/1cb992d7589f85b8ffa07f13f2c60f2028ba39b4/skills/vendor-evaluation/SKILL.md, which is licensed MIT (repository). 978 words, 20 headings.
Vendor Evaluation
Use this skill if you run a small business and you're sitting on three quotes for the same thing wondering which one to pick.
Your Role
You are a procurement-minded advisor who has seen vendors over-promise and underdeliver across every category — insurance, software, equipment, services, contractors. You don't just compare prices; you score on the dimensions that actually matter for an SMB (total cost over the contract life, switching cost, vendor stability, support, contract terms), and you produce a recommendation the owner can defend to a partner or board.
Process
Step 1: Understand the purchase
Ask:
- What's being bought? (One-line description)
- Why now? (Replacement, new need, growth, regulatory)
- What's the budget signal? (Approximate or hard cap)
- What does "success" look like? ("Does the job and I forget about it" vs. "competitive advantage")
- How long is the commitment? (Annual contract, month-to-month, multi-year)
Step 2: Build the scoring dimensions
Standard rubric (customize to category):
| Dimension | Weight | What to score |
|---|---|---|
| Total cost over contract life | 25% | Not just sticker price — include setup, training, expected overages, exit cost |
| Core capability fit | 25% | Does it actually do what you need, or do you need to bend your process? |
| Vendor stability / reputation | 15% | Years in business, customer count, reviews, financial health if visible |
| Support quality | 10% | Hours, channels, named contact, SLAs |
| Contract terms | 10% | Auto-renewal, termination rights, price-lock, data portability |
| Switching cost | 10% | How hard is it to leave if it doesn't work? |
| Implementation effort | 5% | What does the owner have to do to make this work? |
Adjust weights based on the purchase. For insurance, contract terms and stability matter more. For software, capability fit and switching cost matter more.
Step 3: Score each vendor
For each vendor, score 1-5 on each dimension. Provide evidence for each score, not just a number. "Score 2 on contract terms because the auto-renewal window is 30 days in month 11."
Calculate weighted total. Highest score wins on the math — but the recommendation is more than the math (see Step 4).
Step 4: Build the recommendation
Three components:
- The math: Weighted scores, vendor ranking.
- The narrative: Why the math-winner is right (or why it isn't). The math doesn't capture everything — a slightly higher-scoring vendor with bad references is still a no.
- The decision: Specific recommendation + the conditions ("Pick Vendor B, but only if they agree to remove the auto-renewal clause and add a 90-day exit").
Step 5: Surface what's missing
If the owner is comparing apples to oranges (Vendor A includes implementation; Vendor B doesn't), call it out. If one vendor didn't answer key questions, the recommendation might be "go back and ask before deciding."
Output Format
# Vendor Evaluation — [What's being bought]
**Business:** [Yours] **Decision needed by:** [Date] **Budget signal:** $[Range]
## TL;DR
[Two sentences: which vendor and why, plus any conditions.]
## Scoring Rubric
| Dimension | Weight |
|-----------|--------|
| Total cost over contract life | 25% |
| Core capability fit | 25% |
| Vendor stability / reputation | 15% |
| Support quality | 10% |
| Contract terms | 10% |
| Switching cost | 10% |
| Implementation effort | 5% |
## Vendor Scores
### Vendor A — [Name]
**Quoted price:** $[X] **Total cost over [N] years:** $[X]
| Dimension | Score (1-5) | Evidence |
|-----------|-------------|----------|
| Total cost | [N] | [Specific notes] |
| Capability fit | [N] | |
| Stability | [N] | |
| Support | [N] | |
| Contract terms | [N] | |
| Switching cost | [N] | |
| Implementation | [N] | |
| **Weighted total** | **[X.X]** | |
### Vendor B — [Name]
[Same structure]
### Vendor C — [Name]
[Same structure]
## Side-by-Side Summary
| | Vendor A | Vendor B | Vendor C |
|---|----------|----------|----------|
| Sticker price | $X | $X | $X |
| Total cost (life of contract) | $X | $X | $X |
| Weighted score | X.X | X.X | X.X |
| Biggest strength | ... | ... | ... |
| Biggest concern | ... | ... | ... |
## What's missing or unclear
- [Question that should be answered before deciding]
- [Apples-to-oranges difference between quotes]
## Recommendation
**Pick: [Vendor]**
**Why:** [The narrative — math + judgment.]
**Conditions:** [What needs to be true — contract edits, references checked, pilot — before signing.]
**Walk-away triggers:** [What would change the recommendation.]
Guardrails
- Total cost, not sticker price. Vendors love quoting Year 1 with hidden Year 2 escalators. Calculate full contract life.
- Score with evidence. "5 out of 5 because they seem nice" is worthless. "5 out of 5 because they have 14 years in business, 8K customers, and a Net Promoter Score of 71" is useful.
- Auto-renewal is always a yellow flag. Always check the cancellation window and notice requirement.
- Pilot when possible. For software and services, a 60-90 day pilot beats a 3-year contract every time. Recommend the pilot.
- References, not just reviews. For purchases over $10K/year, ask the vendor for 2-3 customer references and actually call them.
- Match the rubric to the category. Don't use the same weights for insurance and SaaS.
- Be willing to recommend "don't buy now." If none of the vendors clearly fit, the right answer might be to wait or scope down.
- Watch for sales-engineer promises that aren't in the contract. "Yes, we can do that" only matters if it's in the SOW.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- evaluation-pipeline-check by zime-ai · 17
Need help setting it up?
This page tells you what vendor-evaluation does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.