vendor-selection
Skill1 starsChanged 3 months agoMITView on GitHub
Run RFI/RFP, scoring matrices, contract negotiation and vendor performance tracking. Use when evaluating RFP proposals, scoring vendors, or procurement.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Nomanriaz786/claude-consulting-teamtheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Nomanriaz786/claude-consulting-team★ 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 repository51 other files it gives its agents.
- ai-governance-architectSkill
- alliancesSkill
- board-deck-builderSkill
- board-reportingSkill
- business-plan-outlinerSkill
- business-planSkill
- business-strategySkill
- change-management-leaderSkill
- change-managementSkill
- chief-of-staffSkill
- client-proposal-writerSkill
- contract-clause-explainerSkill
- decision-frameworkSkill
- decision-makingSkill
- experiment-trackerSkill
- feedback-giverSkill
- fundraisingSkill
- hiringSkill
- internal-reportingSkill
- investor-deckSkill
- investor-pitch-deck-writerSkill
- jira-workflow-stewardSkill
- job-description-writerSkill
- market-trendsSkill
- meeting-summariserSkill
- negotiationSkill
- negotiation-strategistSkill
- notion-database-architectSkill
- okr-designerSkill
- okrsSkill
- operationsSkill
- portfolio-opsSkill
- process-redesignSkill
- productivity-auditSkill
- product-managementSkill
- product-managerSkill
- project-managerSkill
- project-planningSkill
- project-shepherdSkill
- sop-writerSkill
- sprint-planningSkill
- sprint-prioritizerSkill
- studio-operationsSkill
- studio-producerSkill
- supply-chainSkill
- team-dynamicsSkill
- trend-researcherSkill
- upwork-proposalSkill
- upworkSkill
- vendor-procurement-managerSkill
- workflow-redesign-consultantSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 28
Don't recommend selecting purely on lowest price without surfacing the tradeoffs on quality, reliability, and contract terms — that's a …
- Distinctive: line 29
Don't draft contract legal language yourself (indemnification clauses, liability caps, specific legal terms) — that needs a lawyer's review.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Vendor Selection
Vendor decisions are usually made on price alone by default, but price is only one of several factors that determine whether a vendor relationship actually works out — get the evaluation criteria right before comparing quotes, or the comparison itself will mislead.
Workflow
- Define evaluation criteria before soliciting or comparing proposals. A reasonable default weighting to adapt: price/total cost of ownership, quality/reliability track record, delivery/SLA terms, contract flexibility (exit clauses, scaling terms), and vendor financial stability (a cheap vendor that goes under mid-contract creates far more cost than it saved). Ask which matter most for this specific decision rather than assuming price dominates.
- Structure the RFP around outcomes, not just specs — describe what the business needs to achieve, and let vendors propose how, rather than over-specifying a solution that might not be the best approach. Over-specified RFPs tend to just get the incumbent's existing approach re-quoted.
- Build a comparison scorecard, not just a price table — score each vendor against the weighted criteria from step 1, so the comparison reflects total value, not just headline cost.
- Identify negotiation leverage before the conversation, not during it:
- Multiple qualified alternatives (real leverage, only if the alternatives are genuinely viable, not just for show)
- Contract timing (end of vendor's fiscal quarter/year often creates urgency on their side)
- Volume/commitment length (longer terms or higher volume in exchange for better pricing)
- Reference/case-study value (a notable client name can be leverage in the other direction — the vendor wants you as a reference)
- For renewals specifically, don't assume the incumbent's renewal price is fair just because switching has friction — check current market rates, and use switching cost as a negotiating fact, not a reason to skip negotiating.
Anti-Patterns & Constraints
- Don't recommend selecting purely on lowest price without surfacing the tradeoffs on quality, reliability, and contract terms — that's a legitimate choice, but it should be a conscious one, not a default.
- Don't draft contract legal language yourself (indemnification clauses, liability caps, specific legal terms) — that needs a lawyer's review; you can flag what commercial terms to negotiate for, but not draft binding legal clauses.
Output format
## Vendor evaluation: <category>
**Criteria & weights:**
| Criterion | Weight | Notes |
**Vendor comparison:**
| Vendor | Price | [criterion 2] | [criterion 3] | Weighted score |
**Negotiation leverage available:** [specific to this situation]
**Recommendation:** [with reasoning tied to the weighted criteria, not just price]Verification & Quality Checklist
- Each step has a named owner, not a team-shaped placeholder.
- Inputs and outputs defined for every step, including their format.
- Failure and escalation path defined for the steps that can block.
- Completion is measurable - someone can tell whether it is done.
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.

