wiki

Index, search, and cross-reference Markdown pages in a local knowledge base.

1|Updated May 7, 2026
One-click install
npx skills add https://github.com/zchee/json-repair-rs --skill wiki-zchee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki
Source: https://github.com/zchee/json-repair-rs/tree/main/.codex/skills/wiki
Command: npx skills add https://github.com/zchee/json-repair-rs --skill wiki-zchee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Managing extensive project documentation and session knowledge can be cumbersome and scattered across multiple files, making retrieval and updates inefficient.

Core Features & Use Cases

  • Persistent Wiki Management: Create, update, and delete Markdown pages within a dedicated local directory.
  • Keyword Search & Cross-Referencing: Quickly locate relevant pages and link related content using native syntax.
  • Use Case: Collaborate on technical architecture notes by adding new pages, querying existing info with keywords, and maintaining a centralized knowledge base for team sessions.

Quick Start

Use the wiki skill to add a new page titled "Auth Architecture" with content on authentication design.

Frequently Asked Questions about wiki

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

FAQPage Schema
How do I manage local Markdown knowledge base pages for project collaboration?

You can manage a local Markdown knowledge base by creating, updating, and deleting pages within a dedicated directory to maintain centralized project documentation for team collaboration.

How does keyword search work for finding information in a Markdown wiki?

Keyword search in a Markdown wiki indexes local pages to quickly locate relevant project information and supports native syntax for cross-referencing related content.

Can I cross-reference related technical architecture notes in a local Markdown directory?

Yes, you can cross-reference related technical architecture notes using native Markdown syntax to link pages within your local knowledge base directory.

What is the best way to structure scattered project documentation into a centralized knowledge base?

The best way to structure scattered project documentation is to consolidate files into a dedicated local Markdown wiki directory, enabling persistent page management and keyword indexing.

Does this Markdown wiki tool require any external dependencies to run?

No, this Markdown wiki tool operates entirely as a local knowledge base without requiring any external dependencies, allowing you to manage project information independently.

When should I not use a local Markdown wiki for team collaboration?

You should avoid using a local Markdown wiki for team collaboration if your project requires real-time simultaneous editing or complex database-driven queries beyond simple keyword search.