About signal-taxonomy
A skill for defining consistent schemas across outputs from multiple providers. It supports attribute mapping, version control, validation, and documentation for data teams.
Key features
- 01Define fields and data types
- 02Map provider attributes to canonical names
- 03Track schema versions and migrations
- 04Specify validation rules
- 05Document data lineage
Use cases
- 01Normalizing provider data outputs
- 02Introducing new intent topics or attributes
- 03Reviewing lineage and compliance needs
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/signal-taxonomyin Claude Code to confirm it loaded.
Details
From the project READMESignal 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.
Comments
Markdown supported