Agent Skills › microsoft/Ontology-Playground › ontology-catalog-import

ontology-catalog-import

GitHub

将RDF/OWL本体文件导入并转换为仓库目录格式，包含元数据生成、分类验证及编译检查。

.github/skills/ontology-catalog-import/SKILL.md microsoft/Ontology-Playground

Trigger Scenarios

用户需要导入外部或社区本体文件到目录需要将RDF/OWL文件转换为符合规范的目录条目

Install

npx skills add microsoft/Ontology-Playground --skill ontology-catalog-import -g -y

More Options

Non-standard path

npx skills add https://github.com/microsoft/Ontology-Playground/tree/main/.github/skills/ontology-catalog-import -g -y

Use without installing

npx skills use microsoft/Ontology-Playground@ontology-catalog-import

指定 Agent (Claude Code)

npx skills add microsoft/Ontology-Playground --skill ontology-catalog-import -a claude-code -g -y

安装 repo 全部 skill

npx skills add microsoft/Ontology-Playground --all -g -y

预览 repo 内 skill

npx skills add microsoft/Ontology-Playground --list

SKILL.md

Frontmatter

{
    "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>/ 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