oml-descriptions

Create OML description instances across vocabulary, SHACL, and description files.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/hamadah10/OML-Skills-Testing --skill oml-descriptions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oml-descriptions
Source: https://github.com/hamadah10/OML-Skills-Testing/tree/main/.github/oml-descriptions
Command: npx skills add https://github.com/hamadah10/OML-Skills-Testing --skill oml-descriptions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill automates the creation of OML description instances by coordinating vocabulary definitions, SHACL tables, and description files.

Core Features & Use Cases

  • Ensures cross-file consistency by referencing the correct vocabulary, SHACL, and description files during instance creation.
  • Validates required SHACL constraints and optional properties, and supports reverse/forward relation directions as defined in vocabularies.
  • Applies an append-only editing pattern to safely add new instances without resurrecting deleted content.
  • Uses category inference rules to assign conventional categories based on instance naming and context.

Quick Start

Provide the instance details (name, domain, target classes, and any relations) to have the system generate a compliant OML description instance across build/oml, src/md, and src/oml files.

Frequently Asked Questions about oml-descriptions

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

FAQPage Schema
How do I create OML description instances that pass SHACL validation?

OML description instances require coordinating vocabulary definitions, SHACL tables, and description files across a three-file workflow to validate references and enforce required SHACL constraints.

What is the append-only editing pattern for OML description files?

The append-only editing pattern for OML descriptions safely adds new instances without resurrecting deleted content, ensuring well-formed and traceable descriptions across the three-file workflow.

How do I assign categories to Stakeholder and Entity instances in OML?

You assign categories to Stakeholder and Entity instances in OML by applying category inference rules that assign conventional categories based on instance naming and context-analysis domains.

Can I create OML descriptions for both context-analysis and operational-analysis domains?

Yes, you can create OML descriptions for both domains. The workflow applies when creating Stakeholder, Concern, or Entity instances across context-analysis and operational-analysis domains while validating cross-file consistency.

Why do my OML description instances fail cross-file consistency checks?

OML description instances fail cross-file consistency checks when they do not correctly reference the matching vocabulary, SHACL, and description files, violating the enforced three-file workflow and reference validation rules.