wiki-ingest-per-note

What problem does it solve?

Ingesting individual notes into a structured knowledge base wiki is often inconsistent and error-prone: missed privacy opt-outs, incorrect file conversions, inconsistent topic assignments, and skipped session logs lead to duplicate re-ingestion, lost context, and malformed wiki pages that require manual cleanup.

Core Features & Use Cases

• Privacy & Conversion Guardrails: Automatically skips notes marked with ingest: false, and enforces correct conversion workflows for non-Markdown files (emails, transcripts, PDFs, images) to ensure consistent companion file generation and date prefixing.
• Structured Topic Classification: Applies strict rules to assign notes to 8 predefined wiki topics and creates/updates wiki pages with proper cross-references, stub handling, supersession tracking, and contradiction flagging.
• Mandatory Session Logging: Enforces per-note log entry writing to track processed files and conversions, preventing duplicate re-ingestion in future batch runs.
• Use Case: For a team maintaining a long-lived work knowledge base, this skill ensures every ingested note is processed consistently, no source files are re-processed unnecessarily, and all wiki pages follow the same structural and provenance rules.

Quick Start

Invoke the wiki-ingest-per-note skill to process the next note in your active wiki ingestion batch, applying all required conversion, topic classification, and session logging rules.