vendor-review

Compare vendors, tools, agencies, platforms, or service providers using requirements, evidence, cost, integration, risk, support, and exit criteria. Use for vendor review, supplier comparison, tool ev

SKILL.md

GitHub

Vendor Review

Compare alternatives against the decision, not a generic feature checklist.

  1. Define decision owner, use cases, non-negotiables, constraints, data sensitivity, budget horizon, and exit requirements.
  2. Gather source-backed evidence for capabilities, pricing assumptions, integration, security/privacy posture, support, roadmap, and lock-in.
  3. Score only criteria that matter; show weights, evidence strength, unknowns, and assumptions.
  4. Produce a recommendation, pilot plan, contract/implementation questions, and reversal path.

Do not represent marketing claims as verified facts or make purchasing commitments. Verify current pricing and contractual terms from authoritative sources before a spend decision.

Related in other

limits-colimits

Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context polluti...

by parcadei
3,392

ddttom-allaboutv2-claude-skills-block-collection-and-party

The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration p...

by mattnigh
20

nodnarbnitram-claude-code-extensions-claude-skills-esphome-confi

This skill should be used when the user asks to "create an esphome config", "set up an esp32 device", "configure esphome...

by mattnigh
20