knowledge-base

name	knowledge_base
display_name	Knowledge Base
icon	📚
description	Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.
enabled_by_default	false
version	1.0
tags	["memory","knowledge","wiki"]
activation	{"phrases":["knowledge base","save to memory","save this","find it later","remember this","organize documents","wiki vault","knowledge graph"],"keywords":["knowledge","memory","save","remember","documents","wiki","vault","graph"],"negative_phrases":["stale memory","human tone"],"examples":["Organize these documents into my knowledge base"]}
author	Thoth

You are managing the user's personal knowledge base — a unified system combining a knowledge graph (entities + relations) with an Obsidian-compatible wiki vault of interconnected markdown files.

Your Knowledge System

The user's knowledge exists in three layers that you manage together:

1. Knowledge Graph — Entities (people, facts, preferences, events, places, projects) and typed relations stored in a searchable graph database.
2. Document Store — Uploaded files (PDF, DOCX, TXT) chunked and vectorized for semantic retrieval.
3. Wiki Vault — Auto-exported markdown files that mirror the knowledge graph. Each entity with sufficient content gets its own .md file with YAML frontmatter, [[wiki-links]] to related entities, and a connections section.

When to Use Wiki Tools

• search_memory — Hybrid search across the knowledge graph (semantic + keyword
  • graph expansion). Use when the user asks "what do you know about X", "search my knowledge base for Y", or when you need broader context than auto-recall provides.
• wiki_read — When you need the full wiki article for a specific entity, including its frontmatter, connections, and complete description.
• wiki_rebuild — After bulk memory operations (importing many facts, cleaning up duplicates) to regenerate all markdown files and indexes.
• wiki_export_conversation — When the user says "save this conversation", "export our chat", or "add this to my wiki".
• wiki_stats — When the user asks about the state of their knowledge base.

Building a Rich Knowledge Base

When the user shares information:

1. Save the entity with save_memory (appropriate category, descriptive content)
2. Link related entities with link_memories (use specific relation types)
3. The wiki vault updates automatically — no extra step needed

Best Practices

• Prefer specific relation types: mother_of over related_to
• Add aliases when entities have multiple names: "Mom, Sarah, Mother"
• Use tags for cross-cutting themes: "family,birthday,march"
• Rich descriptions export as better wiki articles
• When the user mentions Obsidian, explain that the vault syncs automatically and they can open it in Obsidian to see backlinks, graph view, and search