AGENT SKILL

vendor-review

Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.

License 许可
Apache-2.0
所属仓库
monoes/monomind
最近更新
2026-11-10
Stars
★ 23
Forks
2

01 前言 Front Matter

name
vendor-review
tags
[]
tools
[]
source
https://github.com/anthropics/knowledge-work-plugins
license
Apache-2.0
description
Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.
source_path
operations/skills/vendor-review
source_commit
8444efcd48f7012f09797778a36a33e73d0861f4

02 资源文件 1

03 SKILL.md 正文

/vendor-review

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Evaluate a vendor with structured analysis covering cost, risk, performance, and fit.

Usage

/vendor-review $ARGUMENTS

What I Need From You

  • Vendor name: Who are you evaluating?
  • Context: New vendor evaluation, renewal decision, or comparison?
  • Details: Contract terms, pricing, proposal document, or current performance data

Evaluation Framework

Cost Analysis (Total Cost of Ownership)

  • Total cost of ownership (not just license fees)
  • Implementation and migration costs
  • Training and onboarding costs
  • Ongoing support and maintenance
  • Exit costs (data migration, contract termination)

Risk Assessment

  • Vendor financial stability
  • Security and compliance posture
  • Concentration risk (single vendor dependency)
  • Contract lock-in and exit terms
  • Business continuity and disaster recovery

Performance Metrics

  • SLA compliance
  • Support response times
  • Uptime and reliability
  • Feature delivery cadence
  • Customer satisfaction

Comparison Matrix

When comparing vendors, produce a side-by-side matrix covering: pricing, features, integrations, security, support, contract terms, and references.

Output

## Vendor Review: [Vendor Name]
**Date:** [Date] | **Type:** [New / Renewal / Comparison]

### Summary
[2-3 sentence recommendation]

### Cost Analysis
| Component | Annual Cost | Notes |
|-----------|-------------|-------|
| License/subscription | $[X] | [Per seat, flat, usage-based] |
| Implementation | $[X] | [One-time] |
| Support/maintenance | $[X] | [Included or add-on] |
| **Total Year 1** | **$[X]** | |
| **Total 3-Year** | **$[X]** | |

### Risk Assessment
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|------------|
| [Risk] | High/Med/Low | High/Med/Low | [Mitigation] |

### Strengths
- [Strength 1]
- [Strength 2]

### Concerns
- [Concern 1]
- [Concern 2]

### Recommendation
[Proceed / Negotiate / Pass] — [Reasoning]

### Negotiation Points
- [Leverage point 1]
- [Leverage point 2]

If Connectors Available

If ~~knowledge base is connected:

  • Search for existing vendor evaluations, contracts, and performance reviews
  • Pull procurement policies and approval thresholds

If ~~procurement is connected:

  • Pull current contract terms, spend history, and renewal dates
  • Compare pricing against existing vendor agreements

Tips

  1. Upload the proposal — I can extract pricing, terms, and SLAs from vendor documents.
  2. Compare vendors — "Compare Vendor A vs Vendor B" gets you a side-by-side analysis.
  3. Include current spend — For renewals, knowing what you pay now helps evaluate price changes.

04 同仓库更多 Skills

monoes
monoes/monomind

zk-steward

Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.

★ 23
monoes
monoes/monomind

writing-plans

Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.

内容创作者写作与文案
★ 23
monoes
monoes/monomind

write-spec

Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.

产品经理
★ 23
monoes
monoes/monomind

write-query

Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.

数据分析师
★ 23
monoes
monoes/monomind

workflow-automation

Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.

运维与部署Skill与智能体开发
★ 23
monoes
monoes/monomind

workflow-architect

Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.

Skill与智能体开发
★ 23