knowledge-base

Manage a persistent vault-based knowledge graph with Obsidian-compatible markdown tooling.

4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/danmestas/wardrobe --skill knowledge-base-danmestas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-base
Source: https://github.com/danmestas/wardrobe/tree/main/skills/knowledge-base
Command: npx skills add https://github.com/danmestas/wardrobe --skill knowledge-base-danmestas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent, compounding knowledge base for Claude Code. Drop sources into a vault, let an autoresearch agent synthesize a living wiki, query across sessions, and keep the structure healthy. Use when the user wants persistent notes, a knowledge graph, vault management, or mentions Obsidian, "second brain", or "persistent memory".

Core Features & Use Cases

  • Vault scaffolding and cross-project referencing to maintain a single, coherent knowledge graph.
  • Autoresearch and ingest tooling to synthesize and evolve a living wiki that persists across sessions.
  • Obsidian-compatible markdown primitives and vault-management utilities to organize notes and references.

Quick Start

Install the knowledge-base bundle and load it into your Claude Code workflow to start indexing sources into the vault and auto-synthesize a living wiki.

Frequently Asked Questions about knowledge-base

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

FAQPage Schema
How do I maintain a persistent knowledge graph across multiple Claude Code sessions?

A persistent knowledge graph across sessions is maintained by using a vault-based system to store, ingest, and query notes. This allows cross-project references and continuous knowledge updates to remain coherent between interactions.

Can I use an Obsidian vault with Claude Code for persistent knowledge management?

Obsidian vault workflows are fully supported through Obsidian-compatible markdown primitives. The system provides vault-management utilities to organize markdown notes, scaffold structures, and synthesize a living wiki.

How do I automatically synthesize a wiki from multiple research sources?

To automatically synthesize a wiki from research sources, you drop the sources into a vault and use autoresearch tooling. This ingests the inputs and evolves a living wiki that persists across sessions.

What is the best way to manage cross-project references in a markdown knowledge base?

Managing cross-project references in a markdown knowledge base is best handled through vault scaffolding utilities. This maintains a single, coherent knowledge graph by linking notes and querying across stored data.

Does a vault-based knowledge base require external dependencies for information retrieval?

No external dependencies are required for vault-based information retrieval. The system implements linting, querying, and saving natively through included markdown tooling and skill sets.

When should I not use a vault-based knowledge graph for information storage?

A vault-based knowledge graph is not ideal for ephemeral or single-session data that does not require cross-project references. It is designed for compounding, persistent knowledge rather than temporary session memory.