Run any Skill in Manus with one click

ontology-to-expertpack

Stars6

Forks0

UpdatedMay 5, 2026 at 14:48

Convert an Ontology skill knowledge graph into a structured ExpertPack. Use when migrating from the Ontology skill's entity/relation graph (memory/ontology/graph.jsonl) to ExpertPack's richer format with multi-layer retrieval, EK measurement, and portable deployment. Output is Obsidian-compatible — includes YAML frontmatter on all content files and can be opened as an Obsidian vault. Triggers on: 'ontology to expertpack', 'convert ontology', 'export ontology', 'migrate ontology', 'ontology graph to pack', 'upgrade ontology'. Requires the Ontology skill's graph.jsonl and optionally schema.yaml.

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

brianhearn

brianhearn/expert-pack

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-to-expertpack
description	Convert an Ontology skill knowledge graph into a structured ExpertPack. Use when migrating from the Ontology skill's entity/relation graph (memory/ontology/graph.jsonl) to ExpertPack's richer format with multi-layer retrieval, EK measurement, and portable deployment. Output is Obsidian-compatible — includes YAML frontmatter on all content files and can be opened as an Obsidian vault. Triggers on: 'ontology to expertpack', 'convert ontology', 'export ontology', 'migrate ontology', 'ontology graph to pack', 'upgrade ontology'. Requires the Ontology skill's graph.jsonl and optionally schema.yaml.
metadata	{"openclaw":{"homepage":"https://expertpack.ai","requires":{"bins":["python3"]}}}

Ontology to ExpertPack Converter

Converts an OpenClaw Ontology skill's append-only knowledge graph into a fully compliant ExpertPack with multi-layer retrieval support.

How to Use

Run the converter script:

python3 {skill_dir}/scripts/convert.py \
  --graph memory/ontology/graph.jsonl \
  --output ~/expertpacks/my-knowledge-pack

Optional flags:

--schema memory/ontology/schema.yaml — uses type definitions and relation rules
--name "My Knowledge Pack" — custom pack name (defaults to "Ontology Export")
--type auto|person|product|process|composite — override auto-detected pack type

What It Produces

A complete ExpertPack at the output directory:

manifest.yaml — pack identity, type, context tiers, EK metadata placeholder
overview.md — summary of graph contents, entity/relation counts, navigation guide
Content organized by mapped category (relationships/, workflows/, facts/, concepts/, operational/, governance/)
_index.md in each content directory
relations.yaml — typed entity relation graph (schema 4.1 compliant)
glossary.md — entity types and terms
Retriever-anchored opening definitions and ## section headers for optimal chunking

Filenames use kebab-case. Concept atoms target 400–800 tokens with a 1,000-token ceiling; procedural/reference files stay focused and independently retrievable.

Post-Conversion Steps

cd into the generated ExpertPack directory
Verify content files are 400–800 tokens each (Schema 2.5 — no external chunker needed for correctly-sized files)
Run EK evaluator to measure esoteric knowledge ratio
Review and refine manifest.yaml context tiers
Commit to git and share via expertpack.ai or ClawHub

See expertpack.ai and the expertpack ClawHub skill for full pack maintenance workflows.

Keep the output pack git-friendly and ready for iterative deepening.

More from this repository

same repository

expertpack

brianhearn/expert-pack

Work with ExpertPacks — structured knowledge packs for AI agents. Obsidian-compatible: every pack is a valid Obsidian vault with Dataview support. Use when: (1) Loading/consuming an ExpertPack as agent context, (2) Creating or hydrating a new ExpertPack from scratch, (3) Configuring RAG for a pack, (4) Validating or fixing a pack with the CLI tools, (5) Opening or authoring a pack in Obsidian. Triggers on: 'expertpack', 'expert pack', 'esoteric knowledge', 'knowledge pack', 'pack hydration', 'validate pack', 'ep-validate', 'ep-doctor', 'obsidian vault', 'obsidian pack'. For EK ratio measurement and quality evals install expertpack-eval. For exporting an OpenClaw agent as an ExpertPack install expertpack-export. For converting an existing Obsidian Vault into an ExpertPack install obsidian-to-expertpack.

2026-07-066

obsidian-to-expertpack

brianhearn/expert-pack

Convert an existing Obsidian Vault into an agent-ready ExpertPack. Restructures vault content for EK optimization, RAG retrieval, and OpenClaw integration. Creates a copy — source vault is never modified. Use when: a user wants to make their Obsidian Vault usable by AI agents, convert OV to EP, drop their vault into OpenClaw as a knowledge pack, or make their notes RAG-ready. Triggers on: 'obsidian to expertpack', 'obsidian vault to ep', 'convert obsidian', 'OV to EP', 'obsidian agent ready', 'make my vault ai ready', 'obsidian knowledge pack', 'obsidian rag'.

2026-07-066

expertpack-eval

brianhearn/expert-pack

Measure ExpertPack EK (Esoteric Knowledge) ratio and run automated quality evals. Use when: (1) Measuring what percentage of a pack's content frontier LLMs cannot produce on their own, (2) Running automated eval sets against a pack-powered agent with LLM-as-judge scoring. Requires OpenRouter API key (auto-resolved from OpenClaw auth or OPENROUTER_API_KEY env var). Companion to the main expertpack skill. Triggers on: 'EK ratio', 'measure EK', 'blind probe', 'eval expertpack', 'pack quality eval', 'run eval', 'esoteric knowledge ratio'. Note: packs are Obsidian-compatible — eval results (ek_score) can be added to file frontmatter and queried in Obsidian via Dataview.

2026-05-056

expertpack-export

brianhearn/expert-pack

Export an OpenClaw instance's accumulated knowledge into a structured ExpertPack composite. Use when backing up an agent's identity, exporting for migration, or creating a portable knowledge snapshot. Handles auto-discovery (scanning workspace state to identify constituent packs), distillation (compressing raw state into structured EP files), and packaging (writing EP-compliant packs + composite manifest). Output is Obsidian-compatible — includes YAML frontmatter on all content files and can be opened as an Obsidian vault. NOT for importing/hydrating from an existing EP.

2026-05-056

elite-to-expertpack

brianhearn/expert-pack

Convert Elite Longterm Memory data into a structured ExpertPack. Migrates the 5-layer memory system (SESSION-STATE hot RAM, LanceDB warm store, Git-Notes cold store, MEMORY.md curated archive, and daily journals) into ExpertPack's portable format with multi-layer retrieval, context tiers, and EK measurement. Output is Obsidian-compatible — includes YAML frontmatter on all content files and can be opened as an Obsidian vault. Use when: upgrading from Elite Longterm Memory to ExpertPack, backing up agent knowledge, or migrating to a new platform. Triggers on: 'elite to expertpack', 'convert elite memory', 'export elite memory', 'migrate elite longterm', 'upgrade memory to expertpack', 'elite memory export'.

2026-04-216

self-improving-to-expertpack

brianhearn/expert-pack

Convert Self-Improving Agent learnings into a structured ExpertPack. Migrates the .learnings/ directory (LEARNINGS.md, ERRORS.md, FEATURE_REQUESTS.md) and any promoted content from workspace files into ExpertPack's portable format with multi-layer retrieval, context tiers, and EK measurement. Output is Obsidian-compatible — includes YAML frontmatter on all content files and can be opened as an Obsidian vault. Use when: upgrading from Self-Improving Agent to ExpertPack, backing up agent learnings, exporting accumulated knowledge, or migrating to a new platform. Triggers on: 'self-improving to expertpack', 'convert self-improving', 'export learnings', 'migrate self-improving', 'learnings to expertpack', 'convert learnings to pack'.

2026-04-216

name	ontology-to-expertpack
description	Convert an Ontology skill knowledge graph into a structured ExpertPack. Use when migrating from the Ontology skill's entity/relation graph (memory/ontology/graph.jsonl) to ExpertPack's richer format with multi-layer retrieval, EK measurement, and portable deployment. Output is Obsidian-compatible — includes YAML frontmatter on all content files and can be opened as an Obsidian vault. Triggers on: 'ontology to expertpack', 'convert ontology', 'export ontology', 'migrate ontology', 'ontology graph to pack', 'upgrade ontology'. Requires the Ontology skill's graph.jsonl and optionally schema.yaml.
metadata	{"openclaw":{"homepage":"https://expertpack.ai","requires":{"bins":["python3"]}}}

Ontology to ExpertPack Converter

Converts an OpenClaw Ontology skill's append-only knowledge graph into a fully compliant ExpertPack with multi-layer retrieval support.

How to Use

Run the converter script:

python3 {skill_dir}/scripts/convert.py \
  --graph memory/ontology/graph.jsonl \
  --output ~/expertpacks/my-knowledge-pack

Optional flags:

--schema memory/ontology/schema.yaml — uses type definitions and relation rules
--name "My Knowledge Pack" — custom pack name (defaults to "Ontology Export")
--type auto|person|product|process|composite — override auto-detected pack type

What It Produces

A complete ExpertPack at the output directory:

manifest.yaml — pack identity, type, context tiers, EK metadata placeholder
overview.md — summary of graph contents, entity/relation counts, navigation guide
Content organized by mapped category (relationships/, workflows/, facts/, concepts/, operational/, governance/)
_index.md in each content directory
relations.yaml — typed entity relation graph (schema 4.1 compliant)
glossary.md — entity types and terms
Retriever-anchored opening definitions and ## section headers for optimal chunking

Filenames use kebab-case. Concept atoms target 400–800 tokens with a 1,000-token ceiling; procedural/reference files stay focused and independently retrievable.

Post-Conversion Steps

cd into the generated ExpertPack directory
Verify content files are 400–800 tokens each (Schema 2.5 — no external chunker needed for correctly-sized files)
Run EK evaluator to measure esoteric knowledge ratio
Review and refine manifest.yaml context tiers
Commit to git and share via expertpack.ai or ClawHub

See expertpack.ai and the expertpack ClawHub skill for full pack maintenance workflows.

Keep the output pack git-friendly and ready for iterative deepening.