ontologian-analyze

Extract ontology objects, links, and actions from free-form business requirements.

3|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/swszz/ontologian --skill ontologian-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ontologian-analyze
Source: https://github.com/swszz/ontologian/tree/main/plugin/skills/analyze
Command: npx skills add https://github.com/swszz/ontologian --skill ontologian-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically deriving an ontology structure from free-form business requirements text to accelerate domain modeling, enabling faster, consistent ontology development.

Core Features & Use Cases

  • Autonomous analysis to propose Object Types, Link Types, and Action Types from requirements
  • Surface ambiguities for human review and validate against existing ontology state
  • Generate a structured plan for integrating the new ontology into repository domains

Quick Start

Paste your free-form business requirements text to trigger autonomous ontology derivation.

Frequently Asked Questions about ontologian-analyze

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

FAQPage Schema
How do I automatically derive an ontology structure from free-form business requirements?

To derive an ontology structure from requirements, paste free-form business text to trigger autonomous analysis that extracts domain modeling needs and proposes Object Types, Link Types, and Action Types.

Can I validate new ontology candidates against my existing ontology store?

Yes, validating ontology candidates against the existing ontology store surfaces conflicts and gaps, enabling seamless integration of new Object Types, Link Types, and Action Types into repository domains.

How do I extract domain modeling requirements from text with minimal input?

Autonomous analysis applies to your pasted text to extract domain modeling requirements and identify problems, proposing ontology structure candidates automatically without requiring extensive manual input.

What is the best way to identify problems and ambiguities in business requirements for domain modeling?

The best way to identify problems and ambiguities is using autonomous ontology derivation, which surfaces gaps in free-form business requirements for human review during the domain modeling process.

Does ontology derivation work for generating a structured integration plan for repository domains?

Yes, ontology derivation generates a structured plan for integrating newly proposed Object Types, Link Types, and Action Types directly into your repository domains after validating against the existing store.

When should I not use automated ontology derivation for domain modeling?

Avoid automated ontology derivation when your free-form business requirements lack sufficient detail, as the autonomous analysis requires text context to accurately extract domain modeling needs and propose candidates.