ingest-wiki

Ingest staged files into Twoweeks wiki with controlled index and log updates.

Updated May 4, 2026
One-click install
npx skills add https://github.com/panamini/pi-tooling --skill ingest-wiki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ingest-wiki
Source: https://github.com/panamini/pi-tooling/tree/main/skills/ingest-wiki
Command: npx skills add https://github.com/panamini/pi-tooling --skill ingest-wiki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingesting or editing Twoweeks wiki memory from project context can be error-prone, inconsistent, or lead to unintended corruption of durable pages.

Core Features & Use Cases

  • Mode-based wiki mutation: Choose ingest, lint, direct-update, or save-output to match the user’s intent.
  • Required neutral read order: Follow the specified page-reading sequence and fallbacks to avoid stale-cache mistakes.
  • Write guardrails: Enforce minimal, surgical updates to wiki/index.md, wiki/log.md, and (when needed) wiki/hot.md, while preserving existing conventions.

Example use case: You have staged edits ready to become durable wiki pages and want the system to ingest only what’s staged, update the index and logs, and keep cache as non-canonical.

Quick Start

Use the ingest-wiki flow in ingest mode to process staged files under wiki/rawinput/ and update the durable wiki pages accordingly.

Frequently Asked Questions about ingest-wiki

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

FAQPage Schema
How do I safely ingest project context into wiki memory without corrupting durable pages?

To safely ingest wiki memory, you use a mode-based mutation flow that processes staged files and applies surgical write updates to wiki/index.md and wiki/log.md, preserving existing conventions while keeping cache non-canonical.

What is the correct read sequence for updating wiki memory pages?

The correct wiki memory read sequence requires a neutral order that includes schema, agents, and cache fallbacks to prevent stale-cache mistakes before applying any surgical write updates to durable pages.

How do I lint wiki content before saving analysis output to wiki pages?

You lint wiki content by selecting lint mode within the ingestion flow, which validates staged files under wiki/rawinput/ against required read-sequence rules before allowing any updates to wiki/index.md or wiki/log.md.

When should I update wiki/hot.md during a wiki memory ingestion workflow?

You update wiki/hot.md only when routing or active context changes occur during the ingestion process, keeping all other writes strictly limited to wiki/index.md and wiki/log.md.

Can I directly edit wiki pages without going through a full ingestion process?

Yes, you can use direct-update mode to make surgical edits to durable wiki pages, bypassing full ingestion while still enforcing the neutral read-sequence and write guardrails to maintain page integrity.

What are the limitations of using automated ingestion for wiki index updates?

Automated wiki ingestion limits writes to wiki/index.md, wiki/log.md, and conditionally wiki/hot.md, preventing broad page rewrites and requiring staged files in wiki/rawinput/ to enforce controlled, surgical updates.