wiki

Manage persistent markdown wiki pages with keyword and tag search.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/hotaq/Sprite_harmess --skill wiki-hotaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki
Source: https://github.com/hotaq/Sprite_harmess/tree/main/.codex/skills/wiki
Command: npx skills add https://github.com/hotaq/Sprite_harmess --skill wiki-hotaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of losing important project knowledge across chats, sessions, and scattered markdown files by giving you a durable local wiki you can query and maintain.

Core Features & Use Cases

  • Persistent Knowledge Capture: Store architecture notes, decisions, debugging findings, and conventions as local markdown pages.
  • Fast Local Retrieval: Find pages by keywords, tags, and category without relying on embeddings or external services.
  • Lifecycle Management: Add, read, list, lint, refresh, and delete pages while keeping an index and audit log in sync.
  • Use Case: A developer can record an authentication design decision, cross-link it to related pages, and later retrieve it during incident review or implementation work.

Quick Start

Ask the wiki skill to add a new local wiki page with your title, content, tags, and category, then have it save and index the entry under .omx/wiki.

Frequently Asked Questions about wiki

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

FAQPage Schema
How do I store and retrieve project knowledge locally using markdown?

To store project knowledge locally, you can create markdown pages with titles, tags, and categories, saving them to a local wiki for fast retrieval. Pages are indexed for keyword searches without relying on external services.

What is the best way to capture session logs and architecture decisions across developer sessions?

The best way to capture session logs and architecture decisions is using an append-only local knowledge base that records lifecycle changes. This ensures durable markdown capture and maintains an audit log across developer sessions.

Can I search my local wiki by tags and keywords without using embeddings?

Yes, you can search your local wiki by tags and keywords without using embeddings. The retrieval system relies on local indexing and cross-references rather than vector embeddings to find relevant markdown pages.

Does this local knowledge base work with existing markdown files in my project?

The local knowledge base works by storing content under a specific local storage directory. You add new pages through the provided workflow, which saves and indexes entries into the designated local wiki structure.

How do I lint and manage the lifecycle of markdown pages in a local wiki?

To manage the lifecycle of markdown pages in a local wiki, you can use built-in commands to lint, refresh, and delete entries. These actions keep the index and audit log synchronized without requiring external dependencies.