microsoft/ontology-playground · Archived

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

First seen Jun 21, 2026

Installation

$ npx skills add microsoft/ontology-playground --skill ontology-catalog-import

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from microsoft/ontology-playground.

npx skills add microsoft/ontology-playground

Browse all from microsoft/ontology-playground

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2.5K
License LICENSE
Default branch main
Open issues 5
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,740 B
  • docs README.md 415 B
  • docs SUMMARY.md 209 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 7 installs

SKILL.md

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