Classify and resolve conflicts detected during semantic-layer bundle ingest.
npx skills add https://github.com/Kaelio/ktx --skill ingest-triage
Please help me install this Agent Skill. Skill: ingest_triage Source: https://github.com/Kaelio/ktx/tree/main/packages/cli/src/skills/ingest_triage Command: npx skills add https://github.com/Kaelio/ktx --skill ingest-triage
When ingesting data bundles into a semantic layer, duplicate names, contradictory metric definitions, and re-ingested artifacts can silently corrupt the knowledge base. This Skill gives the agent a deterministic decision tree for classifying each collision and applying the correct resolution before any write lands.
<canonical_pins> blocks and writes unified <concept>-definitions.md wiki pages documenting every variant with provenance.churn_risk with different formulas; the agent renames them to churn_risk_engagement_based and churn_risk_billing_based, writes a unified wiki page, and flags the contradiction for human review.Ask the agent to triage the conflicts detected in the current ingest bundle and resolve each one according to the ingest triage decision tree.
High-intent search queries and answers about installing and using this skill.
Classify the duplicate first: same-content matches are skipped, structural duplicates elect one canonical artifact by inbound reference count, and definitional contradictions are renamed with domain suffixes and captured in a unified wiki page. Only contradictions and ambiguous cases are flagged for human review.
Same-ingest conflicts occur within one bundle where no user signal indicates a winner, so all variants are captured and flagged. Re-ingest conflicts occur across bundles where re-uploading signals intent, so expression-only changes replace silently while semantic breaks replace with a flag.
The canonical artifact is elected by highest inbound reference count from other sources, with ties broken by lexicographically first unit key and then source name. Losing variants are subsumed into a variants wiki page without flagging unless the election is ambiguous.
Flags are raised for definitional contradictions resolved via rename and capture, eviction retentions, override constraints conflicting with inbound references, and canonical pins referencing missing artifacts. Trivial duplicates, clear canonical elections, and expression-only re-ingests are never flagged.
Use domain suffixes derived from the containing view, table, or collection, such as churn_risk_engagement_based or churn_risk_billing_based. Numeric suffixes like churn_risk_1 are discouraged because they disclose nothing about the variant's meaning.
borgheiAutomate BI workflows by turning raw data into metrics and dashboards.
AradotsoBuild a semantic context layer for AI agents querying data warehouses.
m2ai-portfolioMigrate mixed-format legacy files into a validated SQLite database with audit trails.
GetFresh-VenturesReconcile conflicting multi-source metrics using Byzantine fault tolerance and weighted consensus.