Signal normalization, provider orchestration, and data quality governance
Installation
npx claude-plugins install @gtmagents/gtm-agents/data-signal-enrichment
Contents
Folders: agents, commands, skills
Included Skills
This plugin includes 5 skill definitions:
identity-resolution
Use to match accounts, contacts, and opportunities across enrichment
View skill definition
Identity Resolution Playbook Skill
When to Use
- Normalizing provider outputs before syncing to CRM/CDP.
- Tying intent, enrichment, and product telemetry to the same account/contact IDs.
- Diagnosing duplicate or conflicting records in downstream systems.
Framework
- Key Hierarchy – define primary/secondary keys (domain, account_id, email, person_id).
- Matching Logic – configure deterministic and fuzzy rules, tie-breakers, and confidence scoring.
- Conflict Handling – specify precedence rules, merge policies, and exception queues.
- Governance – document owners, change control, and monitoring cadence.
- Audit Trail – capture lineage metadata, before/after snapshots, and rollback steps.
Templates
- Matching rule matrix (field, rule type, weight, confidence threshold).
- Exception queue workflow with owners + SLAs.
- Audit workbook for sampling matches vs source-of-truth.
Tips
- Start with deterministic keys (domain, CRM ID) before fuzzy logic to reduce noise.
- Version rules so downstream teams know when behavior changes.
- Pair with
signal-taxonomyto keep IDs aligned with schema updates.
provider-scorecard
Use to track enrichment provider success, cost, latency, and quality
View skill definition
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
- Metric Definition – success rate, fill %, latency, credit burn, confidence.
- Data Sources – provider logs, credit usage tables, QA samples, incident tickets.
- Scoring Model – weight metrics by enrichment type and business priority.
- Visualization – dashboard or memo highlighting leaders/laggards.
- 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-blueprintupdates to reflect routing decisions.
signal-taxonomy
Use to define schemas, topic tags, and lineage metadata for enriched
View skill definition
Signal Taxonomy Skill
When to Use
- Normalizing multiple provider outputs into a unified schema.
- Rolling out new intent topics, enrichment attributes, or scoring dimensions.
- Auditing lineage + compliance requirements.
Framework
- Schema Definition – fields, datatypes, required/optional flags.
- Topic & Attribute Mapping – align provider-specific attributes to canonical names.
- Versioning – maintain change logs, effective dates, and migration steps.
- Validation Rules – min/max values, allowed lists, dependency rules.
- Documentation – publish data dictionary + lineage diagrams.
Templates
- Data dictionary sheet (field, description, source, owner).
- Topic mapping table by provider.
- Migration checklist for schema changes.
Tips
- Keep names human-readable for GTM teams but consistent with data warehouse standards.
- Tag every field with owner + refresh cadence.
- Pair with
identity-resolutionto ensure IDs and linkages stay consistent.
validation-rulebook
Use to define validation, freshness, and compliance checks for enriched
View skill definition
Validation Rulebook Skill
When to Use
- Running QA before syncing enrichment outputs to GTM systems.
- Auditing providers after schema changes or outages.
- Documenting compliance-ready validation procedures.
Framework
- Rule Catalog – list required fields, regex patterns, allowed values, and dependencies.
- Freshness Thresholds – define time-based SLAs per signal type.
- Confidence Scoring – set weighting for provider, validation method, and history.
- Exception Handling – create workflows for quarantining, reprocessing, or escalation.
- Compliance Hooks – log approvals, data residency tags, and retention policies.
Templates
- Rule table (field, check, threshold, severity, owner).
- QA runbook with pre/post sync steps.
- Compliance audit packet ready for legal/infosec reviews.
Tips
- Automate as many rules as possible but keep manual sampling for high-impact signals.
- Version rules alongside taxonomy updates.
- Pair with
data-quality-stewardoutputs for sign-off history.
waterfall-blueprint
Use to design provider sequences, throttling logic, and credit policies
View skill definition
Waterfall Blueprint Skill
When to Use
- Building contact/company enrichment workflows across multiple providers.
- Updating fallback rules after provider outages or cost shifts.
- Documenting waterfall logic for RevOps + engineering handoffs.
Framework
- Goal & Constraints – define enrichment type, data requirements, credit ceiling, SLA.
- Provider Catalog – list eligible providers with success %, latency, compliance notes.
- Routing Logic – determine sequence, branching, and retry intervals.
- Safeguards – set throttles, dedupe checks, and exception triggers.
- Versioning – log changes, approvals, and effective dates.
Templates
- Waterfall diagram (sequence, inputs, outputs, fallback paths).
- Routing table (provider, criteria, cost, notes).
- Change log with owners + rationale.
Tips
- Keep sequences short for real-time use cases; reserve long chains for batch mode.
- Use A/B tests to validate new providers before full rollout.
- Pair with
provider-scorecardto continuously optimize routing.