# Ontology Catalog Import

> Import customer or external RDF/OWL into this repo's catalogue format. Use when user drops an RDF/OWL file and wants it catalogue-ready (metadata, category, validation, compile).

- Skill: `microsoft/ontology-catalog-import` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add microsoft/ontology-catalog-import`
- Raw SKILL.md: https://api.skillmd.com/api/skills/microsoft/ontology-catalog-import/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Microsoft (https://skillmd.com/u/microsoft)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/microsoft/ontology-catalog-import

---


# Ontology Catalog Import Skill

## Goal

Turn a source `.rdf` / `.owl` file into a valid catalogue entry under:

- `catalogue/external/<source>/<slug>/` or
- `catalogue/community/<author>/<slug>/`

## Read First

1. `docs/authoring-guide.md`
2. `scripts/compile-catalogue.ts` (validation expectations)
3. Existing examples:
- `catalogue/external/schema-org/`
- `catalogue/external/pizza-ontology/`

## Intake Questions

Ask user:

1. Is this entry `external` or `community`?
2. Desired slug and source folder?
3. Desired category?
4. Author display name?
5. Should this be tutorialized into Ontology School too?

## Required Outputs

- `<slug>.rdf` copied/adapted into target folder
- `metadata.json` with required fields
- Valid category value for catalogue compiler

## Person Names

If import cleanup, metadata examples, sample instances, generated RDF/OWL, docs,
or optional Ontology School content need person names, first use the
`name-generator` skill. Do not invent customer, employee, patient, student,
instructor, reviewer, or other human names.

All new person names must come from the `FullName` column in:

```text
data/reference/FNF-2026-06-01-01002-0268.csv
```

## Validate

Run:

- `npx tsx scripts/compile-catalogue.ts`
- `npm run validate`

## Done Criteria

- Entry appears in `public/catalogue.json`
- No compile or validation errors
- Metadata is complete and user-readable
- Any new person names introduced during import came from the `name-generator`
  skill / approved CSV fixture