[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P9E07NMKWYK51SN38YC2J":3,"skill-same:01M71P9E07NMKWYK51SN38YC2J":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M71P9E07NMKWYK51SN38YC2J","vendor-review",null,"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.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fvendor-review\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fvendor-review\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"review","vendor","vendor review","replace","cost","two","use","contract","recommendation","cost analysis","risk","work","risk assessment","analysis","when","new","knowledge","assessment","procurement","proposal","2026-11-10 13:02:02",false,"---\nname: vendor-review\ndescription: \"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.\"\ntags: []\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\nsource_path: \"operations\u002Fskills\u002Fvendor-review\"\nsource_commit: 8444efcd48f7012f09797778a36a33e73d0861f4\n---\n# \u002Fvendor-review\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nEvaluate a vendor with structured analysis covering cost, risk, performance, and fit.\n\n## Usage\n\n```\n\u002Fvendor-review $ARGUMENTS\n```\n\n## What I Need From You\n\n- **Vendor name**: Who are you evaluating?\n- **Context**: New vendor evaluation, renewal decision, or comparison?\n- **Details**: Contract terms, pricing, proposal document, or current performance data\n\n## Evaluation Framework\n\n### Cost Analysis (Total Cost of Ownership)\n- Total cost of ownership (not just license fees)\n- Implementation and migration costs\n- Training and onboarding costs\n- Ongoing support and maintenance\n- Exit costs (data migration, contract termination)\n\n### Risk Assessment\n- Vendor financial stability\n- Security and compliance posture\n- Concentration risk (single vendor dependency)\n- Contract lock-in and exit terms\n- Business continuity and disaster recovery\n\n### Performance Metrics\n- SLA compliance\n- Support response times\n- Uptime and reliability\n- Feature delivery cadence\n- Customer satisfaction\n\n### Comparison Matrix\nWhen comparing vendors, produce a side-by-side matrix covering: pricing, features, integrations, security, support, contract terms, and references.\n\n## Output\n\n```markdown\n## Vendor Review: [Vendor Name]\n**Date:** [Date] | **Type:** [New \u002F Renewal \u002F Comparison]\n\n### Summary\n[2-3 sentence recommendation]\n\n### Cost Analysis\n| Component | Annual Cost | Notes |\n|-----------|-------------|-------|\n| License\u002Fsubscription | $[X] | [Per seat, flat, usage-based] |\n| Implementation | $[X] | [One-time] |\n| Support\u002Fmaintenance | $[X] | [Included or add-on] |\n| **Total Year 1** | **$[X]** | |\n| **Total 3-Year** | **$[X]** | |\n\n### Risk Assessment\n| Risk | Likelihood | Impact | Mitigation |\n|------|-----------|--------|------------|\n| [Risk] | High\u002FMed\u002FLow | High\u002FMed\u002FLow | [Mitigation] |\n\n### Strengths\n- [Strength 1]\n- [Strength 2]\n\n### Concerns\n- [Concern 1]\n- [Concern 2]\n\n### Recommendation\n[Proceed \u002F Negotiate \u002F Pass] — [Reasoning]\n\n### Negotiation Points\n- [Leverage point 1]\n- [Leverage point 2]\n```\n\n## If Connectors Available\n\nIf **~~knowledge base** is connected:\n- Search for existing vendor evaluations, contracts, and performance reviews\n- Pull procurement policies and approval thresholds\n\nIf **~~procurement** is connected:\n- Pull current contract terms, spend history, and renewal dates\n- Compare pricing against existing vendor agreements\n\n## Tips\n\n1. **Upload the proposal** — I can extract pricing, terms, and SLAs from vendor documents.\n2. **Compare vendors** — \"Compare Vendor A vs Vendor B\" gets you a side-by-side analysis.\n3. **Include current spend** — For renewals, knowing what you pay now helps evaluate price changes.\n","# \u002Fvendor-review\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nEvaluate a vendor with structured analysis covering cost, risk, performance, and fit.\n\n## Usage\n\n```\n\u002Fvendor-review $ARGUMENTS\n```\n\n## What I Need From You\n\n- **Vendor name**: Who are you evaluating?\n- **Context**: New vendor evaluation, renewal decision, or comparison?\n- **Details**: Contract terms, pricing, proposal document, or current performance data\n\n## Evaluation Framework\n\n### Cost Analysis (Total Cost of Ownership)\n- Total cost of ownership (not just license fees)\n- Implementation and migration costs\n- Training and onboarding costs\n- Ongoing support and maintenance\n- Exit costs (data migration, contract termination)\n\n### Risk Assessment\n- Vendor financial stability\n- Security and compliance posture\n- Concentration risk (single vendor dependency)\n- Contract lock-in and exit terms\n- Business continuity and disaster recovery\n\n### Performance Metrics\n- SLA compliance\n- Support response times\n- Uptime and reliability\n- Feature delivery cadence\n- Customer satisfaction\n\n### Comparison Matrix\nWhen comparing vendors, produce a side-by-side matrix covering: pricing, features, integrations, security, support, contract terms, and references.\n\n## Output\n\n```markdown\n## Vendor Review: [Vendor Name]\n**Date:** [Date] | **Type:** [New \u002F Renewal \u002F Comparison]\n\n### Summary\n[2-3 sentence recommendation]\n\n### Cost Analysis\n| Component | Annual Cost | Notes |\n|-----------|-------------|-------|\n| License\u002Fsubscription | $[X] | [Per seat, flat, usage-based] |\n| Implementation | $[X] | [One-time] |\n| Support\u002Fmaintenance | $[X] | [Included or add-on] |\n| **Total Year 1** | **$[X]** | |\n| **Total 3-Year** | **$[X]** | |\n\n### Risk Assessment\n| Risk | Likelihood | Impact | Mitigation |\n|------|-----------|--------|------------|\n| [Risk] | High\u002FMed\u002FLow | High\u002FMed\u002FLow | [Mitigation] |\n\n### Strengths\n- [Strength 1]\n- [Strength 2]\n\n### Concerns\n- [Concern 1]\n- [Concern 2]\n\n### Recommendation\n[Proceed \u002F Negotiate \u002F Pass] — [Reasoning]\n\n### Negotiation Points\n- [Leverage point 1]\n- [Leverage point 2]\n```\n\n## If Connectors Available\n\nIf **~~knowledge base** is connected:\n- Search for existing vendor evaluations, contracts, and performance reviews\n- Pull procurement policies and approval thresholds\n\nIf **~~procurement** is connected:\n- Pull current contract terms, spend history, and renewal dates\n- Compare pricing against existing vendor agreements\n\n## Tips\n\n1. **Upload the proposal** — I can extract pricing, terms, and SLAs from vendor documents.\n2. **Compare vendors** — \"Compare Vendor A vs Vendor B\" gets you a side-by-side analysis.\n3. **Include current spend** — For renewals, knowing what you pay now helps evaluate price changes.\n",{"name":5,"tags":44,"tools":45,"source":46,"license":14,"description":7,"source_path":47,"source_commit":48},[],[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","operations\u002Fskills\u002Fvendor-review","8444efcd48f7012f09797778a36a33e73d0861f4","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fvendor-review",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add monoes\u002Fmonomind --skill vendor-review",{"tool":64,"command":65},"bunx","bunx skills add monoes\u002Fmonomind --skill vendor-review",{"tool":67,"command":68},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill vendor-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fvendor-review\u002FSKILL.md",true,[72],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11607,[78,103,139,164,189,216],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":39},"01M71PB3SHWKMNJM6MD65VX8D6","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.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[85,86,87,88,89,90,91,35,92,93,94,19,95,96,97,98,99,100,101,102],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","impact","query","snark","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":107,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":121,"publishedAt":39},"01M71PB18SDG28WBKPKJNB814K","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.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[111,116],{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[122,123,124,89,125,126,33,127,93,128,129,130,131,132,133,134,135,136,137,138],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":149,"publishedAt":39},"01M71PAXFM488X9ARXK0T04TF5","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.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000031","产品经理",[132,150,151,152,153,35,154,33,155,156,30,131,157,158,159,160,161,162,25,163],"write spec","spec","user request","problem","acceptance","ask","vague","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":174,"publishedAt":39},"01M71PASSZY800C0RPEARBS918","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.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000033","数据分析师",[93,132,175,176,177,178,35,25,33,179,180,181,182,30,183,184,185,186,187,188],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":201,"publishedAt":39},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[195,198],{"categoryNo":196,"categoryName":197,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":199,"categoryName":200,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000023","Skill与智能体开发",[202,203,204,205,177,206,207,208,209,92,210,211,212,93,95,183,213,214,215,185],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":223,"publishedAt":39},"01M71PAM19Z1XTV9NPCFSE2MY8","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.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[222],{"categoryNo":199,"categoryName":200,"taxonomyType":114,"taxonomyTypeDesc":115},[204,224,225,226,227,228,229,177,230,231,128,232,233,234,95,183,235,236,185,237],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]