vendor-review
Skill1 starsChanged 7 months agoMITView on GitHub
Evaluate a vendor with cost analysis, risk assessment, TCO breakdown, negotiation points, and recommendation. Use when reviewing a new vendor proposal, deciding to renew or replace, comparing vendors side-by-side, or building a negotiation strategy. Trigger with "vendor review", "evaluate this vendor", "vendor comparison", "should we renew with", or "TCO analysis".
3 other projects use a version of this.
Adopted by
Most recently taken up by
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- njt2810/claude-code-frameworktheir own version, first seen Sep 10, 2026
- gregjonesio/family-office-ai-skillstheir own version, first seen Aug 10, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- anthropics/knowledge-work-plugins★ 36ksame name
- gregjonesio/family-office-ai-skills★ 10same name
- njt2810/claude-code-framework★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 91
Always calculate TCO, not just sticker price.
- Distinctive: line 94
Start renewal evaluations 120-180 days before expiration for negotiation leverage.
- Distinctive: line 95
Document assumptions in the TCO model (growth rates, usage volumes, discounts).
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Vendor Evaluation
Evaluate vendors through structured analysis: cost, capability, risk, TCO, and negotiation strategy.
Workflow
Step 1: Define Criteria
Functional fit, cost/TCO, risk (financial, security, compliance), support (SLA, responsiveness), scalability, integration, and track record. Weight by organizational priorities.
Step 2: Analyze TCO
Direct costs (licenses, implementation), indirect costs (internal labor, integration), hidden costs (overage charges, egress fees, premium support, training), switching costs (migration, termination fees), and opportunity cost. Calculate over 1, 3, and 5-year horizons.
Step 3: Assess Risk
Financial (health, funding), security (SOC 2, ISO, breach history), concentration (single-function dependency), lock-in (portability, API openness), compliance (GDPR, HIPAA), and continuity (DR, redundancy).
Step 4: Negotiation Strategy
Market alternatives, switching feasibility, volume leverage, contract terms (multi-year for pricing, cap on increases), negotiable items (SLA, support tier, training), and walk-away point.
Step 5: Recommend
APPROVE, APPROVE WITH CONDITIONS, REJECT, or COMPARE FURTHER -- with justification.
Output Format
## Vendor Evaluation
**Vendor**: [Name(s)] | **Category**: [Type] | **Date**: [YYYY-MM-DD]
**Recommendation**: [APPROVE / APPROVE WITH CONDITIONS / REJECT]
### Scoring
| Criterion | Weight | Vendor A | Vendor B | Notes |
|-----------|--------|----------|----------|-------|
| Functional fit | 30% | 4/5 | 3/5 | A has feature X |
| Cost/TCO | 25% | 3/5 | 4/5 | B is 20% lower |
| **Weighted Total** | | **3.65** | **3.55** | |
### TCO (3-Year)
| Component | Year 1 | Year 2 | Year 3 | Total |
|-----------|--------|--------|--------|-------|
| License | $[X] | $[X] | $[X] | $[X] |
| Implementation | $[X] | -- | -- | $[X] |
| **Total** | **$[X]** | **$[X]** | **$[X]** | **$[X]** |
### Risk Assessment
| Category | Rating | Details |
|----------|--------|---------|
| Security | MEDIUM | SOC 2 pending |
### Negotiation Strategy
- Target price: [$X] (proposal: [$Y])
- Key asks: [List]
- Walk-away: [Conditions]Examples
User: "Should we renew with our current CRM or switch to Competitor?" Action: Score both on fit, cost, risk, support, scalability. Build TCO comparison. Assess switching costs and migration risk. Recommend with negotiation points.
User: "What's the TCO for CloudCo versus on-premise?" Action: Build side-by-side TCO including infrastructure, licensing, labor, support, scaling. Account for CapEx vs OpEx and present break-even analysis.
Best Practices
- Always calculate TCO, not just sticker price.
- Include internal labor costs -- implementation, integration, training, and management.
- Assess risk independently from cost.
- Start renewal evaluations 120-180 days before expiration for negotiation leverage.
- Document assumptions in the TCO model (growth rates, usage volumes, discounts).
- Weight criteria before scoring to avoid one dimension dominating.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

