OpenParable
Skip to content
← Back to skills

Ontology Catalog Import

Documents
ontology-catalog-import

Ontology Catalog Import is an Agent Skill for documents published in the microsoft/Ontology-Playground repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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).

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/microsoft/Ontology-Playground/blob/HEAD/.github/skills/ontology-catalog-import/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ontology-catalog-import, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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:

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