Initial commit
This commit is contained in:
31
skills/provider-scorecard/SKILL.md
Normal file
31
skills/provider-scorecard/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: provider-scorecard
|
||||
description: Use to track enrichment provider success, cost, latency, and quality
|
||||
trends.
|
||||
---
|
||||
|
||||
# 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.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user