wiki

Manage a local markdown knowledge base with keyword and tag indexing.

2|Updated May 3, 2026
One-click install
npx skills add https://github.com/JustineDevs/roblox-ai-os --skill wiki-justinedevs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki
Source: https://github.com/JustineDevs/roblox-ai-os/tree/main/plugins/roblox-ai-os-creator-skills/skills/wiki
Command: npx skills add https://github.com/JustineDevs/roblox-ai-os --skill wiki-justinedevs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of fragmented project documentation by providing a centralized, searchable, and persistent markdown-based knowledge base that lives directly within your project environment.

Core Features & Use Cases

  • Persistent Knowledge Base: Maintains a structured collection of markdown files for architecture, decisions, and conventions.
  • Session Capture: Automatically logs discoveries and session progress to ensure no technical insights are lost.
  • Keyword Search: Enables rapid retrieval of project-specific information using tag and keyword matching without requiring complex vector databases.

Quick Start

Use the wiki skill to add a new page titled Architecture Overview with the content describing the current system design.

Frequently Asked Questions about wiki

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

FAQPage Schema
How do I maintain persistent markdown documentation for project tracking and session logging?

Markdown documentation for project tracking is maintained by storing technical notes and session logs in a local knowledge base. This facilitates centralized storage and retrieval of architecture decisions and conventions within your project environment.

What is the best way to capture session progress and technical discoveries in a local knowledge base?

Capturing session progress in a local knowledge base is achieved by automatically logging discoveries and technical insights into structured markdown files. This ensures no historical decision tracking or project context is lost between working sessions.

How does keyword search work for retrieving project-specific documentation without a vector database?

Keyword search for project documentation works by using tag and keyword matching to rapidly retrieve technical notes. This indexing approach operates locally without requiring complex vector databases or external search infrastructure.

Can I lint and index technical markdown notes within my project directory?

Linting and indexing technical markdown notes is supported directly within a dedicated project directory. This process validates and organizes your stored architecture decisions and session logs for reliable retrieval.

Does this local knowledge management approach require any external dependencies?

This local knowledge management approach requires no external dependencies to operate. It functions entirely within your project environment to maintain persistent context and historical decision tracking.

When should I use a markdown-based wiki instead of fragmented project documentation?

A markdown-based wiki should be used when fragmented project documentation prevents reliable context retrieval. It provides a centralized, searchable structure for storing conventions, architecture, and session logs directly in your project.