ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified developer tools Safety 4/5

ontology-to-expertpack

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.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/brianhearn/ontology-to-expertpack
Or

What This Skill Does

The ontology-to-expertpack skill serves as a critical bridge between OpenClaw's legacy append-only knowledge graph (Ontology skill) and the modern, high-performance ExpertPack architecture. This utility automates the transformation of unstructured or semi-structured JSONL graph data into the standardized ExpertPack directory format. By parsing your graph.jsonl and optional schema.yaml, the skill maps individual entities and relations into organized, chunked content folders. It generates a production-ready manifest, a comprehensive glossary, and normalized file structures in kebab-case that are optimized for RAG (Retrieval-Augmented Generation) and multi-layer retrieval systems. It transforms disparate data points into an actionable, portable knowledge asset ready for deployment within the OpenClaw ecosystem.

Installation

To integrate this tool into your workspace, execute the following command in your terminal or via the OpenClaw CLI:

clawhub install openclaw/skills/skills/brianhearn/ontology-to-expertpack

Ensure that you have Python 3 installed in your local environment, as the skill utilizes a internal Python-based converter script to handle the graph traversal and file generation logic.

Use Cases

This skill is designed for advanced users and developers who have outgrown the limitations of a flat ontology graph. Use this when:

  1. Migrating Legacy Data: You want to upgrade your existing knowledge graph to take advantage of the sophisticated chunking and indexing capabilities of the ExpertPack standard.
  2. Knowledge Portability: You need to export a specific subset of learned knowledge into a portable folder structure for sharing across different OpenClaw agents or team environments.
  3. Performance Optimization: You are experiencing retrieval latency or context-window saturation and need a structured, tiered knowledge pack that allows for optimized semantic search.
  4. Governance Readiness: You need to prepare your data for external auditing, requiring the structured manifest and metadata tracking provided by the ExpertPack output.

Example Prompts

  1. "OpenClaw, I need to upgrade my current knowledge structure; run the ontology-to-expertpack converter on my local graph.jsonl to create a new pack in ~/expertpacks/project-alpha."
  2. "Migrate the ontology knowledge to a structured ExpertPack using the schema.yaml file located in my current project directory and name the resulting pack 'Technical Operations Handbook'."
  3. "Convert my memory ontology graph to an ExpertPack format and ensure the output type is set to process so it integrates correctly with my existing workflow automation."

Tips & Limitations

  • Chunking Strategy: While the skill generates essential summaries, remember that after conversion, you must run the ExpertPack chunker to fully populate the propositions/ and summaries/ folders for optimal retrieval results.
  • File Limits: The tool enforces a 3KB file size limit per content file to ensure high granularity during embedding; if you have massive monolithic nodes, consider pre-splitting them.
  • Dependencies: Always verify your schema.yaml syntax before conversion; improper mapping of relation rules can lead to broken navigation links in the generated _index.md files.
  • Deployment: The output directory is git-ready, so initialize a repository within the folder immediately after generation to track iterative changes to your knowledge pack.

Metadata

Stars4190
Views1
Updated2026-04-18
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-brianhearn-ontology-to-expertpack": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#knowledge-management#migration#graph-database#structured-data#rag
Safety Score: 4/5

Flags: file-read, file-write

Related Skills

expertpack

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) Opening or authoring a pack in Obsidian. Triggers on: 'expertpack', 'expert pack', 'esoteric knowledge', 'knowledge pack', 'pack hydration', 'obsidian vault', 'obsidian pack'. For CLI tools (ep-validate, ep-doctor, ep-graph-export, ep-strip-frontmatter) install expertpack-cli. 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. For serving any ExpertPack as an MCP endpoint (expertise-as-a-service), see EP MCP at github.com/brianhearn/ep-mcp.

brianhearn 4190

elite-to-expertpack

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'.

brianhearn 4190

expertpack-cli

Run ExpertPack CLI tools for validating, fixing, graphing, and deploying packs. Use when: running ep-validate, ep-doctor, ep-graph-export, ep-strip-frontmatter, or ep-fix-broken-wikilinks on a local pack. Triggers on: 'validate pack', 'ep-validate', 'ep-doctor', 'fix pack errors', 'graph export', 'ep-graph-export', 'strip frontmatter', 'deploy pack', 'ep-strip-frontmatter'. Requires the ExpertPack repo cloned locally (github.com/brianhearn/ExpertPack) — tools live in tools/validator/.

brianhearn 4190

expertpack-eval

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.

brianhearn 4190

self-improving-to-expertpack

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'.

brianhearn 4190