Skip to main content
Generalgtmagents

provider-scorecard

Use to track enrichment provider success, cost, latency, and quality

Stars
259
Source
gtmagents/gtm-agents
Updated
2026-04-03
Slug
gtmagents--gtm-agents--provider-scorecard
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/gtmagents/gtm-agents/HEAD/plugins/data-signal-enrichment/skills/provider-scorecard/SKILL.md -o .claude/skills/provider-scorecard.md

Drops the SKILL.md into .claude/skills/provider-scorecard.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Provider Scorecard Skill

When to Use

  • Monthly/weekly ops reviews of enrichment vendors.
  • Before renewing contracts or adjusting credit allocations.
  • After outages or performance regressions to inform routing changes.

Framework

  1. Metric Definition – success rate, fill %, latency, credit burn, confidence.
  2. Data Sources – provider logs, credit usage tables, QA samples, incident tickets.
  3. Scoring Model – weight metrics by enrichment type and business priority.
  4. Visualization – dashboard or memo highlighting leaders/laggards.
  5. Action Tracker – document optimization experiments and owner assignments.

Templates

  • Scorecard table per provider.
  • Executive summary slide with top takeaways.
  • Jira/Asana template for provider improvement tasks.

Tips

  • Normalize metrics per enrichment type to avoid unfair comparisons.
  • Capture qualitative notes (support responsiveness, roadmap access).
  • Pair with waterfall-blueprint updates to reflect routing decisions.