What problem does it solve? Designing OWL ontologies and SKOS controlled vocabularies involves many subtle rules — inverse properties, disjoint classes, label cardinality, hierarchy cycles — that are easy to get wrong. This Skill walks an agent through a structured workflow from domain clarification to validated Turtle output, preventing common modelling mistakes. ## Core Features & Use Cases - Structured Design Workflow: Clarify the domain, draft the ontology header, declare classes and properties top-down, then add individuals or concepts. - OWL and SKOS Guidance: Covers class axioms, property types and characteristics, concept schemes, labels, hierarchies, and cross-vocabulary mappings, with rules for combining both vocabularies. - Mistake Prevention: Enforces key rules such as one skos:prefLabel per language, bidirectional owl:inverseOf, mandatory skos:inScheme, and no skos:broader cycles. - Use Case: A knowledge engineer needs to model an organisational domain. The Skill guides them to declare an owl:Ontology header, build an Employee/Organisation class hierarchy with inverse object properties, and attach a SKOS concept scheme for job titles — all written as valid Turtle via rdf_write and checked with sparql_query_files. ## Quick Start Ask the agent to design an OWL ontology or SKOS vocabulary for your domain, stating the main entities, relationships, and base URI.
