wiki

Maintain a persistent markdown wiki with keyword, tag, and category queries.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill wiki-dropsyoon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki
Source: https://github.com/dropsyoon/oh-my-claudecode/tree/main/skills/wiki
Command: npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill wiki-dropsyoon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of losing hard-won project insights between sessions by giving you a persistent, self-maintained knowledge base you can continuously grow.

Core Features & Use Cases

  • Ingest knowledge into pages: Store structured notes across multiple wiki pages so discoveries compound over time.
  • Query by keywords, tags, and categories: Retrieve relevant snippets from existing pages and use them to synthesize answers with citations.
  • Maintain quality with linting: Detect orphan pages, stale content, broken cross-references, oversized pages, and structural contradictions.
  • Quick Add and page management: Add small updates fast, list and read pages, and delete outdated content.

Quick Start

Use the wiki skill to add a new page by telling it: add a page titled "Auth Architecture" with the relevant notes and tags, then organize it under the architecture category.

Frequently Asked Questions about wiki

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

FAQPage Schema
How do I maintain persistent project knowledge across sessions without losing insights?

To maintain persistent project knowledge across sessions, use a markdown wiki to capture and query insights, preventing the loss of hard-won discoveries between interactions. It stores structured notes in a project-local directory, allowing your knowledge base to compound over time.

How do I query a markdown wiki using keywords and tags instead of embeddings?

Query a markdown wiki using keyword, tag, and category matching to retrieve relevant snippets from existing pages. This approach synthesizes answers with citations directly from your stored notes without relying on vector embeddings.

How can I detect broken cross-references and stale content in my documentation?

Detect broken cross-references, stale content, and orphan pages in your documentation by running wiki linting operations. This quality maintenance feature also identifies oversized pages and structural contradictions within your knowledge base.

Do I need a specific database to set up a local knowledge base for iterative Q&A?

No specific database is needed to set up a local knowledge base for iterative Q&A. The system requires only page storage in a project-local .omc/wiki directory to manage ingest, add, and query operations.

What is the best way to automatically capture session knowledge into documentation pages?

The best way to automatically capture session knowledge into documentation pages is using a log-driven auto-capture mechanism. This feature continuously ingests insights into your markdown wiki, ensuring important project discoveries self-compound over time.