kairos-medallion-staging

Generate bronze vocabulary TTL files from source system documentation.

1|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/Cnext-eu/kairos-ontology-toolkit --skill kairos-medallion-staging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kairos-medallion-staging
Source: https://github.com/Cnext-eu/kairos-ontology-toolkit/tree/main/.github/skills/kairos-medallion-staging
Command: npx skills add https://github.com/Cnext-eu/kairos-ontology-toolkit --skill kairos-medallion-staging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expert guide for creating bronze vocabulary descriptions from source system reference documentation. Reads API specs, SQL DDL, sample data from the sources/ folder and generates kairos-bronze: TTL files alongside the source docs.

Core Features & Use Cases

  • Phase-driven workflow that ingests system documentation from ontology-hub/integration/sources/{system-name} and outputs {system-name}.vocabulary.ttl
  • Provides a structured 5-phase pipeline (Verify source documentation, Extract schema, Generate TTL, Validate artifacts, and Next steps) for reliable bronze vocabulary creation
  • Supports the kairos-bronze vocabulary TTL generation and downstream mapping to domains

Quick Start

Place your source documentation under ontology-hub/integration/sources/{system-name}, then run the medallion workflow to generate the TTL.

Frequently Asked Questions about kairos-medallion-staging

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

FAQPage Schema
How do I generate a bronze vocabulary TTL from SQL DDL and API specs?

To generate a bronze vocabulary TTL, place your SQL DDL, API specs, and sample data under the ontology-hub/integration/sources folder, then run the workflow to extract schemas and produce a validated vocabulary TTL file.

What is a bronze vocabulary TTL used for in ontology integration?

A bronze vocabulary TTL defines source-system schemas as RDF triples for downstream ontology integration. It standardizes extracted SQL DDL and API spec data into the kairos-bronze vocabulary format for domain mapping.

Do I need a specific folder structure to generate source vocabulary TTLs?

Yes, generating source vocabulary TTLs requires a fixed folder structure under ontology-hub/integration/sources/{system-name}. This path organizes the input documentation needed for the five-phase extraction pipeline.

What are the steps to validate bronze vocabulary artifacts before domain mapping?

Validating bronze vocabulary artifacts occurs in the fourth phase of the workflow. It checks the generated {system-name}.vocabulary.ttl files against kairos-bronze definitions to ensure correctness before downstream mapping.

Can I extract sample data alongside SQL DDL to build a source vocabulary?

Yes, the workflow ingests sample data alongside SQL DDL and API specs from your sources folder. It processes all three input types during the extraction phase to populate the bronze vocabulary TTL generation.

Why does my ontology integration workflow require a fixed five-phase TTL generation process?

The fixed five-phase process ensures reliable TTL generation by sequentially verifying source documentation, extracting schemas, generating TTLs, validating artifacts, and defining next steps for downstream ontology integration.