Ontology build team
Hierarchical agent skills for domain ontology planning, research, construction, and validation with saved research artifacts and eval-ready workflows.
npx -y skills add Mokee04/ontology_research --skill ontology-build-teamAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Turn research outputs into a domain ontology draft using layered modeling, SKOS-first conceptualization, selective OWL formalization, and explicit modeling decisions tied back to evidence.
SKILL.md
1.9 KB, 392 tokens by cl100k_base, as published. Nobody here has run it
Ontology Build Team
Read:
../refs/Total Guide.md../shared/references/skill-family-architecture.md../shared/references/templates.md
Use this skill after research artifacts exist.
Build Segments
| Segment | Goal | Required user feedback |
|---|---|---|
| B1 Concept backbone | settle core entities and boundaries | yes |
| B2 Relation and constraint draft | connect concepts and note unresolved choices | yes |
| B3 Machine-readable spec | express stable structure in ontology spec files | yes |
| B4 Review packaging | prepare outline, mapping notes, and modeling decisions | yes |
Team Composition
Route build work through:
ontology-ontology-architect
Tasks
- Start from evidence and competency questions, not from guesswork.
- Separate
Core,Domain, andApplicationconcerns when possible. - Build a stable glossary or SKOS concept layer first.
- Pause and confirm the conceptual backbone with the user before adding more detail.
- Add OWL constructs only where richer semantics are justified.
- Record every important modeling choice and unresolved ambiguity.
- Prepare a validation-ready ontology outline and mapping notes.
- Pause after the outline/spec draft and ask the user what feels wrong, missing, or over-modeled.
Outputs
Write or update:
../exe/<run-id>/build/glossary.md../exe/<run-id>/build/modeling-decisions.md../exe/<run-id>/build/ontology-outline.md../exe/<run-id>/build/mapping-notes.md
Exit Criteria
Do not hand off to validation until:
- the glossary or concept layer exists
- key relations are modeled
- mapping assumptions are explicit
- unresolved issues are clearly listed
- a build checkpoint has been reviewed with the user
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.