knowledge-base-overview

Organize markdown knowledge bases with Obsidian conventions and cross-links.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build and maintain personal knowledge bases as Obsidian-compatible markdown wikis. The LLM writes and maintains all wiki content, while humans curate sources, ask questions, and guide exploration.

Core Features & Use Cases

  • Vault-agnostic wiki generation and cross-linking across markdown files.
  • Ingest, organize, and maintain references; bootstrap MOC pages; ensure inbound/outbound links follow Obsidian conventions.
  • Supports Obsidian-native patterns, MOC navigation, and wiki health checks for consistency.

Quick Start

Bootstrap a new Obsidian-style wiki and start ingesting sources to build a linked knowledge base.

Frequently Asked Questions about knowledge-base-overview

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

FAQPage Schema
How do I automate building an Obsidian knowledge base using markdown?

You can automate an Obsidian knowledge base by using an LLM to write, organize, and maintain markdown wiki content while enforcing frontmatter metadata and cross-linking conventions across your vault.

Can I automatically generate MOC pages and cross-links in an Obsidian vault?

Yes, you can automatically bootstrap MOC navigation pages and ensure inbound and outbound cross-links follow Obsidian conventions across all markdown files in your vault.

What is the best way to ingest sources into a markdown wiki for Obsidian?

The best way to ingest sources into a markdown wiki is to automate ingestion workflows that organize references, enforce frontmatter metadata, and lint files for Obsidian-style consistency.

Does this approach to vault automation work without specific Obsidian plugins?

Vault automation works vault-agnostically by generating markdown files and cross-links that follow native Obsidian patterns and frontmatter conventions without requiring specific plugins.

Why are my Obsidian cross-links inconsistent after ingesting new wiki content?

Inconsistent cross-links occur when ingested content lacks enforced metadata or linting; running wiki health checks and enforcing Obsidian conventions during ingestion resolves these inconsistencies.

How do I maintain frontmatter metadata across a markdown knowledge base?

You maintain frontmatter metadata by running automated lint and query workflows that enforce Obsidian conventions and check wiki health for consistency across all markdown files.