One-click install
npx skills add https://github.com/hschne/pi-stuff --skill wiki-hschne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki
Source: https://github.com/hschne/pi-stuff/tree/main/skills/wiki
Command: npx skills add https://github.com/hschne/pi-stuff --skill wiki-hschne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of scattered, hard-to-locate personal knowledge by providing a centralized, indexed wiki for all project specs, decisions, session logs, and research, so you never duplicate work or lose important context.

Core Features & Use Cases

  • Centralized Knowledge Storage: Save specs, plans, runbooks, session logs, and decision documents to the correct wiki collection with standardized naming and automatic index refresh.
  • Powerful Search & Retrieval: Use QMD's keyword, semantic, and hybrid search modes to quickly find past context, prior decisions, and existing research across your wiki.
  • Use Case: When starting a new project feature, search the wiki for past related decisions and existing specs to avoid repeating work and align with prior choices.

Quick Start

Use the wiki skill to search for all past decisions and context related to the current Mapit project feature.

Frequently Asked Questions about wiki

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

FAQPage Schema
How do I build a personal wiki for project knowledge management and finding past decisions?

To build a personal wiki for knowledge management, you need a centralized storage system that saves project specs, decisions, and session logs with standardized naming conventions. This ensures consistent, discoverable retrieval of historical context and prior research.

What is the best way to search historical context and prior work across personal project documents?

The best way to search historical context is using keyword, semantic, and hybrid search modes provided by QMD command-line tools. This allows you to quickly find past decisions, existing research, and related specs across your entire personal wiki.

How do I save runbooks and session logs to ensure they are discoverable later?

To save runbooks and session logs discoverably, store them in the correct wiki collection using standardized file naming conventions and automatic index refresh workflows. This enforces consistent layout and enables fast knowledge retrieval.

Can I use QMD command-line tools for personal knowledge retrieval and document storage?

Yes, you can use QMD command-line tools for personal knowledge retrieval and document storage. QMD supports keyword, semantic, and hybrid search modes to quickly find past context and prior work across your stored project documents.

Why does my personal knowledge base return duplicate work and scattered context?

Your personal knowledge base returns scattered context because it lacks a centralized, indexed wiki with standardized collection layouts and file naming conventions. Without automatic index refresh workflows, historical context and prior decisions become hard to locate.

When do I need a centralized knowledge base for project specs and research materials?

You need a centralized knowledge base for project specs and research materials when you want to avoid duplicating work or losing important context. It provides indexed storage for session logs and decisions, enabling fast search of prior work before starting new features.