wiki-init

Scaffolds a notebook folder with wiki, raw, inbox, and config directories.

Updated May 14, 2026
One-click install
npx skills add https://github.com/dadlabs-io/llm-wiki-bootstrap --skill wiki-init-dadlabs-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-init
Source: https://github.com/dadlabs-io/llm-wiki-bootstrap/tree/main/bootstrap/skills/wiki-init
Command: npx skills add https://github.com/dadlabs-io/llm-wiki-bootstrap --skill wiki-init-dadlabs-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a structured knowledge wiki for an existing project requires manually creating many folders and files with consistent conventions. This Skill automates that scaffolding so a notebook folder is created correctly in one confirmed step. ## Core Features & Use Cases - Notebook scaffolding: Creates <vault>/<topic>/ containing wiki/, raw/, answers/, _inbox/ (pending, done, failed, reports, archive), _config/feeds.md, template README and hub pages, and a first _INDEX.md. - Registry-based vault resolution: Resolves the target vault through .claude/wiki-config.json and the linked-notebooks registry, so no manual path configuration is needed in the normal case. - Confirmation-first workflow: Proposes the plan (project root, notebook path, topic, description) and runs only after user confirmation; it refuses to overwrite an existing topic. - Use Case: You have an existing project with no wiki and want to add one. Invoke the skill, confirm the proposed slug and scope description, and get a ready-to-fill notebook folder. ## Quick Start Ask the AI to run wiki init to add a wiki notebook to the current project, then confirm the proposed topic slug and description.

Frequently Asked Questions about wiki-init

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

FAQPage Schema
How do I add a wiki to an existing project?▼

Invoke the wiki-init skill with a topic slug and a one-to-two sentence scope description. It proposes the notebook path and plan, then creates the folder structure after your confirmation.

What is the difference between wiki-init and new-wiki?▼

new-wiki scaffolds whole projects and builds the wiki folders itself in its Phase B, so it never calls wiki-init. Use wiki-init only as a standalone scaffolder to add a notebook folder by hand to an existing project or a second topic.

What folder structure does wiki-init create?▼

It creates a wiki folder with stub subfolders and sessions, plus raw, answers, and _inbox directories with pending, done, failed, reports, and archive subfolders. It also writes _config/feeds.md, a README with a Scope section, hub pages, and a first _INDEX.md.

How does wiki-init decide where to create the notebook?▼

It resolves the vault through the registry: the project's .claude/wiki-config.json provides the notebook and registry entries pointing to linked-notebooks.json. You only pass --vault for a legacy in-project vault or when running from outside the project.

What happens if the topic folder already exists?▼

The wiki-init.py script errors out and refuses to overwrite an existing topic. Check whether the topic exists before running, and choose a different slug if it does.