kairos-mapping-report

Generate HTML mapping reports visualizing source concept alignment with domain ontology.

1|1|Updated Jan 3, 2026

Search Tags:#dashboards #ontology #data-analytics #report #mapping #skos

Ready to run

npx skills add https://github.com/Cnext-eu/kairos-ontology-toolkit --skill kairos-mapping-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kairos-mapping-report
Source: https://github.com/Cnext-eu/kairos-ontology-toolkit/tree/main/.github/skills/kairos-mapping-report
Command: npx skills add https://github.com/Cnext-eu/kairos-ontology-toolkit --skill kairos-mapping-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate comprehensive HTML mapping reports that visualize how source system concepts align with the domain ontology, enabling quick review and governance.

Core Features & Use Cases

Source-centric view: show table-to-entity mappings, column-to-property mappings, and coverage dashboards.
Entity-centric view: organize by target ontology classes with domain badges, transform expressions, and source-table associations.
Dashboards & summaries: data flow diagrams, executive metrics, and action items to guide validation and follow-up.
Reuse with kairos-ontology tooling: integrates with source vocabulary, domain ontology, and SKOS mappings to produce repeatable reports.

Quick Start

Use the kairos-ontology project command to generate the mapping report.

Frequently Asked Questions about kairos-mapping-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate an HTML report for SKOS ontology mappings?▼

To generate an HTML report for SKOS ontology mappings, use the kairos-ontology project command to render existing mappings, domain ontology definitions, and source vocabularies into a visual document for governance review.

What is a source-centric mapping report and when do I need one?▼

A source-centric mapping report visualizes table-to-entity and column-to-property mappings with coverage dashboards. You need one to review how specific source system concepts align with the domain ontology and identify coverage gaps.

Can I visualize coverage gaps across multiple source systems and domains?▼

Yes, you can visualize coverage gaps across multiple source systems and domains by rendering entity-centric perspectives with domain badges and source-table associations to highlight governance issues and missing alignments.

Do I need existing SKOS mappings to publish an ontology mapping report?▼

Yes, existing SKOS mappings are required to publish an ontology mapping report. You must also provide domain ontology definitions and a defined source vocabulary to render the source-centric and entity-centric views.

What is the best way to review domain ontology alignment for governance?▼

The best way to review domain ontology alignment for governance is to generate an HTML mapping report containing data flow diagrams, executive metrics, and action items that guide validation and follow-up across source systems.

How does an entity-centric mapping view differ from a source-centric view?▼

An entity-centric mapping view organizes information by target ontology classes using domain badges and transform expressions, whereas a source-centric view shows table-to-entity and column-to-property mappings with coverage dashboards.