buyer-eval-skill MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

Domain-expert question banks for common B2B categories
Structured interview mode — can converse with vendor AI agents
Evidence-based scoring with per-criterion citations
Multi-vendor comparison matrix
Shell-based tooling, open source

Live-Demo

In der Praxis

buyer-eval-skill.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "buyer-eval-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/salespeak-ai/buyer-eval-skill",
        "~/.claude/skills/buyer-eval-skill"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "buyer-eval-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/salespeak-ai/buyer-eval-skill",
        "~/.claude/skills/buyer-eval-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "buyer-eval-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/salespeak-ai/buyer-eval-skill",
        "~/.claude/skills/buyer-eval-skill"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "buyer-eval-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/salespeak-ai/buyer-eval-skill",
        "~/.claude/skills/buyer-eval-skill"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "buyer-eval-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/salespeak-ai/buyer-eval-skill",
        "~/.claude/skills/buyer-eval-skill"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "buyer-eval-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/salespeak-ai/buyer-eval-skill",
          "~/.claude/skills/buyer-eval-skill"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add buyer-eval-skill -- git clone https://github.com/salespeak-ai/buyer-eval-skill ~/.claude/skills/buyer-eval-skill

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: buyer-eval-skill

How to evaluate three SaaS vendors against your requirements

👤 Buyers, RevOps, procurement leads ⏱ ~120 min intermediate

Wann einsetzen: You've shortlisted 3 vendors and need to pick one defensibly.

Voraussetzungen

Skill cloned — git clone https://github.com/salespeak-ai/buyer-eval-skill ~/.claude/skills/buyer-eval-skill

Ablauf

Define the rubric

We're buying a customer support platform. Propose a weighted rubric (feature depth, integrations, price, security, support).✓ Kopiert

→ Weighted criteria with rationale
Interview each vendor

Use the skill's question bank to interview vendor A. Their docs / AI agent is at <url>. Record evidence per criterion.✓ Kopiert

→ Per-criterion evidence snippets with sources
Score and compare

Score all three and produce a comparison matrix with a recommendation.✓ Kopiert

→ Matrix + recommendation + named risks

Ergebnis: A defensible vendor pick with evidence, not vibes.

Fallstricke

Rubric favors the vendor you already like — Lock the rubric before seeing demos
Evidence is just vendor marketing claims — Weight third-party sources (docs, G2, case studies) over marketing

Kombinieren mit: filesystem

Compare RFP responses against your requirements

👤 Procurement teams drowning in RFP responses ⏱ ~90 min intermediate

Wann einsetzen: You sent an RFP, got 5 responses, and need to rank them.

Ablauf

Load the responses

Here are 5 RFP response PDFs in rfp/. Extract answers per requirement.✓ Kopiert

→ Per-requirement matrix
Flag gaps and fluff

Where did a vendor answer the wrong question or punt? Flag fluff.✓ Kopiert

→ Honest read of each response
Rank

Rank the responses and write a short memo for the evaluation committee.✓ Kopiert

→ Ranked memo

Ergebnis: A fair, fast RFP review.

Fallstricke

Rewarding the best-written response over the best fit — Score on substance; penalize fluff

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

buyer-eval-skill + filesystem

Read PDFs/docs from a local folder during evaluation

Read rfp/responses/ and extract answers per requirement.✓ Kopiert

buyer-eval-skill + google-ai-mode-skill

Cross-check vendor claims against public info

For each vendor claim that isn't in their docs, run a quick web check.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
rubric-design	domain + must-haves	Start of any evaluation
vendor-interview	vendor source (docs/AI agent)	Per vendor
scoring-and-matrix	evidence per vendor + rubric	After interviews
recommendation-memo	matrix	Final step

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: none beyond LLM
Tokens pro Aufruf: 10–40k per full eval
Kosten in €: free
Tipp: Interview one vendor at a time — keeps context focused and evidence clean

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: none

Datenabfluss: only if the skill calls out to vendor agents you point it at

Vendor chats may be recorded on their side — treat as a business conversation

Fehlerbehebung

Häufige Fehler und Lösungen

Evidence is shallow

Point Claude at primary docs; fallback to published case studies

Scores feel gamed

Re-lock the rubric and re-run scoring blind to vendor identity if possible

Alternativen

buyer-eval-skill vs. andere

Alternative	Wann stattdessen	Kompromiss
creative-director-skill	Evaluating creative concepts, not B2B software	Different judgment domain

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen