mcpbeat

Ontology Catalog Import

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

538 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
2320
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/microsoft/Ontology-Playground --skill ontology-catalog-import

What comes with it

415 bytes besides the instruction
README.md

The instruction itself

8 sections, as written by the author

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

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

Intake Questions

Ask user:

  • Is this entry external or community?
  • Desired slug and source folder?
  • Desired category?
  • Author display name?
  • 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

How to use it

Copy the folder

Take microsoft/ontology-catalog-import from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npx. Without those the skill loads but fails at the first command.