ontologist

Produce structured ontology models defining entities, relationships, and identity criteria.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill ontologist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ontologist
Source: https://github.com/OntoLedgy/ol_ai_context_library/tree/main/skills/ontologist
Command: npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill ontologist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of inconsistent, incomplete domain understanding that leads to flawed downstream architecture and implementation. It removes guesswork about what entities exist in a domain, how they relate, and what defines their identity over time, ensuring all stakeholders share a single, coherent view of the domain.

Core Features & Use Cases

  • Domain Ontology Analysis: Identify all entities (individuals, types, relations), their identity criteria, classification hierarchies, and relationships from requirements, interviews, or existing systems.
  • Ontology Coherence Review: Audit existing ontology models or implementations for completeness, logical consistency, dependency errors, and naming clarity.
  • Use Case: For example, when building a healthcare management system, use this Skill to map core entities like Patient, Appointment, and Diagnosis, define their identity rules and relationships, and validate the model before architects design the solution or engineers implement it.

Quick Start

Use the ontologist skill to analyze the e-commerce domain and produce a complete ontology model covering all core entities, their relationships, and identity criteria for review.

Frequently Asked Questions about ontologist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a coherent domain ontology model from existing requirements?

Building a domain ontology involves identifying entities, classification hierarchies, and relationships from requirements to remove ambiguity and ensure stakeholders share a single, coherent view before architecture design.

What is ontology coherence review and when do I need it for legacy systems?

Ontology coherence review audits existing models for logical consistency, dependency errors, and naming clarity. It is needed when reviewing legacy systems or validating pre-architecture domain models to remove ambiguity.

How do I define identity criteria for entities during domain analysis?

Defining identity criteria during domain analysis involves explicitly mapping how entities are identified over time, ensuring coherent classification hierarchies and relationships for downstream implementation engineers.

Can I use domain analysis to validate entity relationships before software architecture design?

Yes, domain analysis validates entity relationships and identity criteria before architecture design, providing a standardized process that captures domain knowledge and removes downstream guesswork for solution architects.

What's the best way to structure taxonomy and entity modeling for a new business domain?

The best way to structure taxonomy and entity modeling is to produce a structured ontology that explicitly defines entities, relationships, and identity criteria, ensuring stakeholders share a single, coherent view of the domain.

Why does inconsistent domain understanding lead to flawed downstream implementation?

Inconsistent domain understanding leads to flawed implementation by introducing guesswork about entities and relationships. Explicitly defining ontology models eliminates this risk by validating identity criteria before engineers build the solution.