Run any Skill in Manus with one click

ontology-map

Stars2

Forks0

UpdatedFebruary 6, 2026 at 23:03

Map local tags, categories, or terms to standard formal ontologies (like SKOS or industry-specific standards) to ensure interoperability.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

dandye

dandye/information-architecture

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	ontology-map
description	Map local tags, categories, or terms to standard formal ontologies (like SKOS or industry-specific standards) to ensure interoperability.
required_roles	{"scribe":"roles/scribe.editor"}
personas	["taxonomist","information-architect"]

Ontology Mapper Skill

Analyze a list of local terms (tags, categories) and suggest mappings to standard ontologies to improve content classification and interoperability.

Inputs

SOURCE_TERMS - A list of terms or a path to a file containing terms to map.
TARGET_ONTOLOGY - (Optional) The standard ontology to map to (e.g., "SKOS", "Dublin Core", "Schema.org"). Default: "SKOS".

Workflow

Analyze: Review the SOURCE_TERMS to understand their local context and usage.
Search: Look up potential matches in the TARGET_ONTOLOGY spec.
Map: suggest:
- Exact Match (skos:exactMatch)
- Broader Match (skos:broader)
- Narrower Match (skos:narrower)
- Related Match (skos:related)

Output

A mapping table (Markdown or CSV) linking Input Term -> Target URI/Term -> Relation Type.

More from this repository

same repository

named-entity-normalization

dandye/information-architecture

Normalize named entities and concept variants into canonical forms using controlled vocabularies or standard taxonomies.

2026-05-232

vocabulary-overlap-analysis

dandye/information-architecture

Analyze vocabulary overlap and identify named entities unique to domain/document corpora.

2026-05-232

document-tree-generate

dandye/information-architecture

Transform lengthy documents into a semantic tree structure. It extracts sections, summaries, and hierarchies optimized for use with Large Language Models (LLMs).

2026-04-092

ontology-define

dandye/information-architecture

Design formal ontologies using OWL/RDFS. Defines classes, properties, and relationships for complex semantic modeling.

2026-02-062

content-inventory

dandye/information-architecture

Systematic cataloging of information assets. Creates comprehensive inventories or card sorting materials from content.

2026-02-062

json-ld-generate

dandye/information-architecture

Generate JSON-LD structured data for web content. Maps content to Schema.org types to improve search engine understanding and rich result eligibility.

2026-02-062

name	ontology-map
description	Map local tags, categories, or terms to standard formal ontologies (like SKOS or industry-specific standards) to ensure interoperability.
required_roles	{"scribe":"roles/scribe.editor"}
personas	["taxonomist","information-architect"]

Ontology Mapper Skill

Analyze a list of local terms (tags, categories) and suggest mappings to standard ontologies to improve content classification and interoperability.

Inputs

SOURCE_TERMS - A list of terms or a path to a file containing terms to map.
TARGET_ONTOLOGY - (Optional) The standard ontology to map to (e.g., "SKOS", "Dublin Core", "Schema.org"). Default: "SKOS".

Workflow

Analyze: Review the SOURCE_TERMS to understand their local context and usage.
Search: Look up potential matches in the TARGET_ONTOLOGY spec.
Map: suggest:
- Exact Match (skos:exactMatch)
- Broader Match (skos:broader)
- Narrower Match (skos:narrower)
- Related Match (skos:related)

Output

A mapping table (Markdown or CSV) linking Input Term -> Target URI/Term -> Relation Type.