wiki-ingest-next-batch

Claim the next unclaimed batch of notes for wiki imports.

3|1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/rijnb/knowledge-base-wiki --skill wiki-ingest-next-batch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-ingest-next-batch
Source: https://github.com/rijnb/knowledge-base-wiki/tree/main/.junie/skills/wiki-ingest-next-batch
Command: npx skills add https://github.com/rijnb/knowledge-base-wiki --skill wiki-ingest-next-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When running large multi-batch imports of notes into your knowledge base wiki, interrupted sessions or parallel work across multiple sessions can lead to duplicate work, lost progress, or conflicting claims on batches of notes. This skill solves that by providing a safe, atomic way to pick up the next unclaimed batch without overlapping with other sessions.

Core Features & Use Cases

  • Atomic Batch Claiming: Uses file rename operations to atomically claim the next unprocessed batch, preventing duplicate work across parallel sessions.
  • State Validation: Automatically checks for in-progress imports, fully processed batches, and remaining unclaimed work to give clear status updates.
  • Use Case: If you are importing 1000 research notes into your wiki and split the work across 4 separate sessions, each session can run this skill to pick up the next available batch without stepping on each other's work.

Quick Start

Tell your AI assistant "ingest next batch" to claim and process the next unclaimed batch of notes for your knowledge base wiki import.

Frequently Asked Questions about wiki-ingest-next-batch

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

FAQPage Schema
How do I safely continue a wiki knowledge base import across interrupted sessions?

Parallel wiki note ingestion prevents duplicate work by using atomic file rename operations to claim the next unprocessed batch. This mechanism ensures multiple sessions never overlap on the same batch and all notes are processed exactly once.

What happens if my batch import of notes times out halfway through?

If a batch import times out, state validation automatically checks for in-progress imports and remaining unclaimed work. You can safely resume by claiming the next available batch without losing completed progress or repeating processed notes.

How do I start processing the next batch of notes for my wiki?

To process the next batch of notes for your wiki, instruct your AI assistant to ingest the next batch. The system will atomically claim the next unclaimed batch, validate current progress, and coordinate processing to ensure seamless continuation.

Can I use this for large-scale note ingestion split across multiple parallel sessions?

Yes, large-scale note ingestion split across multiple parallel sessions is fully supported. The atomic batch claiming mechanism coordinates work across sessions, making it suitable for importing thousands of research notes without overlapping or conflicting claims.

What is the best way to avoid duplicate work when importing 1000 research notes into a wiki?

The best way to avoid duplicate work when importing 1000 research notes into a wiki is splitting the task into discrete batches and using atomic claiming. This prevents parallel or interrupted sessions from processing the same notes twice.