oml-text

Extract OML vocabulary and instance semantics from repository source files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dwagmuse/dw-oml-3 --skill oml-text
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oml-text
Source: https://github.com/dwagmuse/dw-oml-3/tree/main/.claude/skills/oml-text
Command: npx skills add https://github.com/dwagmuse/dw-oml-3 --skill oml-text

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The oml-text Skill helps you produce accurate answers by inspecting and reasoning over the actual OML source text (files, IRIs, declarations, and layout) instead of relying only on higher-level model views that may be incomplete or unavailable.

Core Features & Use Cases

  • Source-first OML authoring analysis: Use when the task depends on syntax-accurate details like aliases, annotations, comments, and how content is organized across repository files.
  • Repository-structured navigation: Apply heuristics to focus on likely source locations (e.g., under src/model/oml/) and avoid built artifacts.
  • Semantic preservation across text: Distinguish vocabulary definitions from description instances, and treat extends, uses, and containment relationships carefully.
  • Compare and reconcile across files: Use targeted reads to cross-check IRIs and declarations, then synthesize assumptions when facts are spread across multiple OML files.
  • Escalation path to MCP: Switch to oml-mcp when the workflow becomes primarily model navigation/validation/structured querying.

Quick Start

Use the oml-text skill to answer a question by reading the smallest relevant OML file(s) and extracting the exact declarations and semantics from the source text.

Frequently Asked Questions about oml-text

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

FAQPage Schema
How do I extract OML ontology vocabulary and instance semantics directly from repository files?

To extract OML ontology vocabulary and instance semantics from repository files, read the smallest relevant source files under likely locations like src/model/oml/ and pull exact declarations, avoiding built artifacts. This preserves accurate syntax-level details such as aliases, annotations, and comments.

What is the best way to analyze OML source text when the OML MCP is unavailable?

Analyzing OML source text when OML MCP is unavailable requires inspecting actual repository files, IRIs, and declarations directly. This approach ensures accurate answers by relying on syntax-level inspection and cross-file comparison rather than higher-level model views that may be incomplete.

How do I preserve semantics when comparing OML declarations across multiple files?

To preserve semantics when comparing OML declarations across multiple files, use targeted reads to cross-check IRIs and distinguish vocabulary definitions from description instances. Treat extends, uses, and containment relationships carefully to synthesize accurate assumptions.

When should I escalate from source-text analysis to OML MCP for model navigation?

You should escalate from source-text analysis to OML MCP when the workflow becomes primarily model navigation, validation, or structured querying. Source-text driven answers are best for syntax-accurate authoring details, while MCP handles higher-level model views.

Does source-first OML authoring analysis support inspecting annotations and comments?

Yes, source-first OML authoring analysis supports inspecting annotations, comments, and aliases by extracting precise ontology vocabulary and instance semantics directly from repository files. This ensures syntax-accurate details are preserved during repository-structured navigation.