cowork-vendor-comparison — Claude Code skill for vendor proposals
The cowork-vendor-comparison Claude Code skill compares vendor proposals and aligns their pricing. It produces a cost and terms matrix, then prepares negotiation points and reference questions.
MIT 104 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill cowork-vendor-comparison -a claude-codeWhat cowork-vendor-comparison does
The skill reads a folder of vendor quotes, proposals, and SOWs, extracting prices, contract terms, SLAs, implementation details, and exit conditions. It puts vendors on the same footing for seats, usage, and contract length. Missing prices are marked UNPRICED -- ask, never treated as zero.
The result is vendor-comparison.md, a table of costs, fit against the stated need, implementation risks, and contract flexibility, with each cell tied to a source document and page. TCO uses a realistic term, defaulting to 3 years. The skill also prepares negotiation points for the top 2 vendors and questions for reference checks. It accepts PDF, .docx, and .xlsx files; a sentence describing the purchase goal helps assess fit.
What it helps with
- align vendor prices on the same assumptions
- calculate ownership cost across a contract term
- spot unpriced items and buried contract terms
- compare SLAs, implementation risks, and exit conditions
- prepare negotiation points and reference questions
Example prompts for the agent
- Compare the proposals in
vendor-quotes. - Calculate TCO only for
vendor-quotes. - Prepare negotiation points for
Vendor A.
How to install cowork-vendor-comparison
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-vendor-comparison -a claude-code2Manually: put the files in place
~/.claude/skills/cowork-vendor-comparison/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cowork-vendor-comparison/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-vendor-comparison -a codex2Manually: put the files in place
.agents/skills/cowork-vendor-comparison/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-vendor-comparison -a cursor2Manually: put the files in place
.cursor/skills/cowork-vendor-comparison/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills cowork-vendor-comparison2Manually: put the files in place
.github/skills/cowork-vendor-comparison/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-vendor-comparison -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path cowork-vendor-comparisonManually: put the files in place
.devin/skills/cowork-vendor-comparison/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-vendor-comparison -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cowork-vendor-comparison
How do I install cowork-vendor-comparison in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill cowork-vendor-comparison -a claude-code. The skill file is at ~/.claude/skills/cowork-vendor-comparison/SKILL.md.
What does cowork-vendor-comparison do?
It aligns vendor proposals, calculates TCO, and writes a comparison of costs, terms, and risks to vendor-comparison.md. It can also prepare negotiation points and reference-check questions.
What file types can cowork-vendor-comparison read?
It accepts PDF, .docx, and .xlsx files in a folder. A sentence about the purchase goal helps assess each proposal against the stated need.
Source text
SKILL.md · MIT
--- name: cowork-vendor-comparison description: Drop a folder of vendor quotes, proposals, and SOWs on Cowork -- normalizes them into one comparison matrix, computes true total cost of ownership, surfaces the terms each vendor buried, and arms you with negotiation leverage points and reference-check questions. tools: Read, Glob, Grep, Write, Bash, WebSearch model: inherit --- # Cowork Vendor Comparison Compare vendor proposals the way a procurement lead does: normalize everything to the same units before judging anything, price the full term not the first invoice, and read the terms the sales deck skipped. Input: a folder of quotes/proposals/SOWs (PDF, .docx, .xlsx) and, ideally, one sentence on what the purchase needs to accomplish. ## Workflow 1. **Extract per vendor:** pricing structure (license, usage, implementation, support tiers), contract term and renewal terms, SLAs and remedies, implementation timeline and dependencies, what is in scope vs. priced as add-on, exit terms (data export, termination fees), and every assumption the proposal states. 2. **Normalize.** Convert all pricing to a common basis -- same seat count, same usage volume, same term. Where a proposal is silent on something another proposal prices (training, integrations, overage rates), mark it `UNPRICED -- ask`, never zero. Unpriced is not free. 3. **Compute TCO** over the realistic term (default 3 years): year-one cost, steady-state annual cost, escalators applied, one-time costs amortized, and the exit cost. Show the math per vendor. 4. **Matrix.** Output `vendor-comparison.md`: side-by-side table of cost, capability fit against the stated need, SLA strength, implementation risk, and contract flexibility -- each cell citing the source document and page. Follow with a plain-English paragraph per vendor: the honest case for and against. 5. **Negotiation prep.** For the top 2 vendors: leverage points (their weaknesses vs. the rival's strengths, end-of-quarter timing, multi-year vs. flexibility trades), the specific asks worth making (cap the escalator, free implementation, opt-out at 12 months), and 5 reference-check questions targeting each vendor's specific risk areas. ## Rules - Never judge from unnormalized numbers. A lower sticker with usage pricing can be the expensive option. - Every cell in the matrix traces to a document and page. "Vendor B has better support" without a citation is vibes. - Silence is a finding: what a proposal does not say (no uptime SLA, no data-export clause) goes in the matrix as prominently as what it says. - Do not manufacture a winner. If the vendors genuinely split on cost vs. capability, present the trade and the decision criteria, and say which way the stated need leans. - Flag lock-in explicitly: proprietary data formats, migration fees, auto-renewals with long notice windows. - If proposals answer different scopes (one quoted 50 seats, one quoted 200), lead with that mismatch and request aligned quotes before deep comparison. ## Quick Commands - "Compare [folder]" -- full workflow - "TCO only" -- steps 1-3 - "What's unpriced?" -- the ask-list of gaps per vendor - "Prep me to negotiate with [vendor]" -- step 5 for one vendor
© OneWave-AI · MIT · OneWave-AI/claude-skills