wiki

Ingest, query, and maintain markdown pages in a local wiki.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent, self-maintained markdown knowledge base for project and session knowledge.

Core Features & Use Cases

  • Ingest: add pages with a title and content to a local wiki under .omx/wiki.
  • Query & Read: search by keywords and read pages, with cross-reference links like [[page-name]].
  • Lifecycle & Maintenance: lint pages, list/read/delete, and auto-capture discoveries as session logs.

Quick Start

Instruct me to add a wiki page by title and content, then query or read pages as needed.

Frequently Asked Questions about wiki

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

FAQPage Schema
How do I persist project documentation and session notes in a markdown knowledge base?

You can persist project documentation by ingesting markdown pages with a title and content into a local wiki. The knowledge base captures session logs and design decisions, storing everything centrally for ongoing project reference.

How do I search markdown documentation and use cross-references to link related pages?

Search markdown documentation using local keyword and tag matching, which ensures fast offline access without vector embeddings. You can link related pages by inserting cross-reference syntax like [[page-name]] directly into your content.

Does this project wiki tool need vector embeddings or an internet connection to search?

No, this project wiki tool does not need vector embeddings or an internet connection. It uses a local index with keyword and tag matching to query the markdown knowledge base, ensuring fast and completely offline access.

What is the best way to maintain and lint markdown pages in a local project wiki?

The best way to maintain markdown pages is to use the built-in lint operation on your local project wiki. You can also list, read, and delete pages to manage the knowledge base lifecycle and auto-capture session discoveries.

Can I store design decisions and session logs offline without relying on a cloud database?

Yes, you can store design decisions and session logs completely offline under a local .omx/wiki directory. This self-maintained markdown knowledge base centralizes project information without requiring any external cloud database.