signal-taxonomy
Use to define schemas, topic tags, and lineage metadata for enriched signals.
When & Why to Use This Skill
The Signal Taxonomy skill empowers users to architect structured data environments by defining precise schemas, topic tags, and lineage metadata. It streamlines the process of normalizing multi-provider data streams into a unified canonical model, significantly enhancing data discoverability, regulatory compliance, and integration readiness for modern data stacks.
Use Cases
- Data Normalization: Standardize inconsistent outputs from multiple third-party data providers into a single, unified schema for seamless downstream analysis.
- Metadata & Lineage Tracking: Maintain a clear audit trail and data dictionary, documenting field ownership, source origins, and transformation logic to meet compliance requirements.
- Schema Governance: Manage versioned updates to intent topics and enrichment attributes, ensuring consistency across data warehouses and Go-To-Market (GTM) platforms.
- Validation & Quality Control: Implement rigorous validation rules and dependency checks to ensure high-quality signals for lead scoring and behavioral analysis.
| name | signal-taxonomy |
|---|---|
| description | Use to define schemas, topic tags, and lineage metadata for enriched |
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.