neo4j-ontology-skill

When to Use

• Authoring an ontology document (Neo4j Ontology Graph Specification) from a domain description
• Editing existing ontology YAML/JSON: nodes, relationships, properties, types, constraints, cardinality, extensions
• Validating an ontology document against the spec schema

When NOT to Use

• Cypher queries, or loading/applying an ontology into a database → neo4j-cypher-skill (ontology Cypher procedures do not exist yet — later work there)
• Generic graph modeling advice (node vs property vs label, anti-patterns, supernodes) → neo4j-modeling-skill

Authoring Workflow

Step 1 — Gather domain intent

Identify what is being modeled: entity types (nodes), connections (relationships + direction), properties per element, identifying keys, mandatory fields, cardinality. If the domain or required shape is unclear, ask the user what is being modeled and which questions the ontology must answer. Do NOT guess a domain.