wiki

Manage a persistent knowledge base with SQLite and YAML content.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Jurel89/copilot-omni --skill wiki-jurel89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki
Source: https://github.com/Jurel89/copilot-omni/tree/main/skills/wiki
Command: npx skills add https://github.com/Jurel89/copilot-omni --skill wiki-jurel89

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of managing long-lived project knowledge in a persistent, easily accessible manner.

Core Features & Use Cases

  • Persistent Knowledge Base: Maintain project knowledge across different runs and team members.
  • Query and Graph: Facilitate structured information retrieval and analysis through queries and graph representation.
  • CLI Validation: Provide a command-line interface for human-readable inspection and validation of the knowledge base.
  • Use Case: Imagine you have a complex project with various components. Use this Skill to store project documentation, specifications, and reference materials, enabling quick access and updates by the team.

Quick Start

Create a new page in the wiki with the command: wiki_write({ title: "Project Overview", body: "...", tags: ["project", "summary"] }).

Frequently Asked Questions about wiki

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

FAQPage Schema
How do I store and query project knowledge using a persistent knowledge base?

You can store and query project knowledge by writing pages with YAML-based content manipulation and retrieving them through structured queries. This persistent knowledge base uses SQLite for state storage to maintain documentation across runs.

What is the best way to visualize relationships in a project knowledge base?

Visualizing relationships in a project knowledge base is done through built-in graph visualization. This feature represents structured project documentation and specifications as an interconnected graph for easier analysis.

Can I validate wiki content and inspect the knowledge base from the command line?

Yes, you can validate wiki content and inspect the knowledge base using the provided CLI validation interface. This command-line tool allows for human-readable inspection of stored project specifications and reference materials.

Do I need SQLite to manage a persistent wiki for project documentation?

Yes, SQLite is required to manage this persistent wiki because it handles state storage. This database dependency ensures your project knowledge base maintains documentation and reference materials across different sessions.

How do I create a new page in a CLI knowledge base with YAML content?

To create a new page in the CLI knowledge base, use the write command with parameters for title, body, and tags. This YAML-based content manipulation stores the new entry directly into the persistent wiki.

What are the limitations of using a YAML-based wiki for collaborative knowledge management?

A limitation of this YAML-based wiki is that it relies on SQLite for state storage and CLI validation for inspection. It targets collaborative environments but may require manual command-line interaction rather than a graphical interface for updates.