<< All versions
Skill v1.0.0
currentTrusted Publisher100/100microsoft/ontology-playground/ontology-catalog-import
──Details
PublishedJuly 4, 2026 at 05:46 AM
Content Hashsha256:6dac5668d0c43eb6...
Git SHA
──Files
Files (1 file, 1.7 KB)
SKILL.md1.7 KBactive
SKILL.md · 67 lines · 1.7 KB
version: "1.0.0" name: ontology-catalog-import description: "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)."
Ontology Catalog Import Skill
Goal
Turn a source .rdf / .owl file into a valid catalogue entry under:
catalogue/external/<source>/<slug>/orcatalogue/community/<author>/<slug>/
Read First
docs/authoring-guide.mdscripts/compile-catalogue.ts(validation expectations)- Existing examples:
catalogue/external/schema-org/catalogue/external/pizza-ontology/
Intake Questions
Ask user:
- Is this entry
externalorcommunity? - Desired slug and source folder?
- Desired category?
- Author display name?
- Should this be tutorialized into Ontology School too?
Required Outputs
<slug>.rdfcopied/adapted into target foldermetadata.jsonwith 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.tsnpm 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