Resolve parent company assignments via code-based joins and enrichment.
npx skills add https://github.com/Soria-Inc/soria-stack --skill parent-map
Please help me install this Agent Skill. Skill: parent-map Source: https://github.com/Soria-Inc/soria-stack/tree/main/parent-map Command: npx skills add https://github.com/Soria-Inc/soria-stack --skill parent-map
Consolidates disparate company identifiers and messy name variants into a single, code-driven parent company reference so downstream dives and gold models join consistently and market metrics remain accurate.
Ask parent-map to identify unmapped codes from the target source, run parallel.ai enrichment, reconcile canonical parents and produce a reconciled CSV ready for soria scraper upload and warehouse publish.
High-intent search queries and answers about installing and using this skill.
Parent company assignments are resolved by joining source entities using identifiers like NAIC group_code, MA contract_number, and CMS provider_ccn, then enriching unmapped codes to produce a canonical parent table with verified ownership timelines.
Canonical parent mapping consolidates disparate company identifiers and name variants into a single code-driven reference table. It batches unmapped codes through enrichment, collapses failures to self-named entities, and canonicalizes parent names for deterministic downstream joins.
To ensure a 100% match rate, you batch unmapped codes through enrichment, reconcile canonical parents, produce a reconciled CSV, and enforce a strict match verification gate before uploading via scraper flow and wiring mappings into gold models.
Yes, parallel.ai enrichment is used to batch process unmapped codes, collapse resolution failures to self-named entities, canonicalize parent names, and tag network affiliations such as BCBS, Delta Dental, and Kaiser.
No, code-based entity resolution uses code and code_type joins rather than fuzzy name matching to ensure deterministic joins. This approach guarantees consistent mapping across dives and gold models with historical name variant support.
Code-based joins require a verified 100% match rate after reconciliation and upload. Unmapped codes must be batched through enrichment, and resolution failures are collapsed to self-named entities rather than being matched through fuzzy logic.
bahayonghangCompile markdown captures into draft knowledge with summaries and indices.
dchukCreate and register custom scraper adapters inheriting from SourceMonitor::Scrapers::Base.
matt-fell-aiAnalyze JSONL system logs to identify root causes of repeated failures.
xfs96192Match fuzzy account names and evaluate open-day rules by date.
