extract-graph

Extract entity-relation triples from Obsidian notes into graph memory stores.

Updated May 5, 2026
One-click install
npx skills add https://github.com/ethan-rio/skills --skill extract-graph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract-graph
Source: https://github.com/ethan-rio/skills/tree/main/skills/personal_agent/extract-graph
Command: npx skills add https://github.com/ethan-rio/skills --skill extract-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of siloed, unconnected note content that cannot be easily queried for relationships between entities, which limits the utility of personal knowledge management systems for complex research or project work.

Core Features & Use Cases

  • Entity-Relation Triple Extraction: Automatically pulls causal, temporal, and semantic relationships between entities (people, concepts, events, etc.) from Obsidian source and wiki notes, following a standardized taxonomy.
  • Flexible Graph Storage: Integrates with Honcho graph memory stores for production use, or falls back to local JSON-on-disk storage for prototyping when the Honcho schema is still being finalized.
  • Use Case: After curating a research note on a historical technology trend, use this skill to automatically extract entities like key inventors, related papers, and timeline events, so you can later query how different concepts influenced each other.

Quick Start

Use the extract-graph skill to process the note 'Source -- The Bitter Lesson.md' and add its extracted entities and relationships to your graph memory store.

Frequently Asked Questions about extract-graph

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

FAQPage Schema
How do I extract entity-relation triples from Obsidian notes?

You can extract entity-relation triples from Obsidian notes by applying this Skill to source, wiki, and inbox items. It automatically pulls causal, temporal, and semantic relationships between entities into a standardized taxonomy using LLM-powered validation and entity deduplication.

What is the best way to build a queryable knowledge graph from personal notes?

Building a queryable knowledge graph from personal notes is best achieved by extracting structured entity-relation triples from unconnected content. This approach transforms siloed Obsidian vault data into traversable graph memory, enabling complex relationship queries for research or project work.

Can I store extracted graph triples locally without an external database?

Yes, you can store extracted graph triples locally without an external database. The Skill integrates with Honcho graph memory stores for production use but also includes a local JSON-on-disk fallback specifically for prototyping when the schema is still being finalized.

Does graph extraction work with existing second-brain systems and PKM workflows?

Graph extraction works seamlessly with existing second-brain systems and PKM workflows. It processes Obsidian source notes to build traversable graph memory, allowing you to later query how different concepts, people, and events influenced each other within your personal knowledge management setup.

How does idempotent triple extraction prevent duplicate entities in a knowledge graph?

Idempotent triple extraction prevents duplicate entities in a knowledge graph by ensuring that processing the same Obsidian note multiple times yields consistent, non-redundant results. It combines LLM-powered validation with entity deduplication to maintain a clean and accurate graph memory store.

What are the limitations of using local JSON-on-disk storage for graph memory?

The limitation of using local JSON-on-disk storage for graph memory is that it is intended only for prototyping when the Honcho schema is still being finalized. For production use and complex traversable knowledge graph queries, integrating with Honcho graph memory stores is required.