new-wiki

Scaffolds a new project with the LLM-wiki framework, folders, config, and seeded documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a structured knowledge wiki for a new project involves repetitive manual work: creating folder hierarchies, writing config files, seeding documentation, and wiring up tooling. This Skill automates that entire bootstrap through a short guided interview, so a fresh project can capture decisions and ingest research from the first session. ## Core Features & Use Cases - Guided two-round interview: Collects project name, review-gate preference, description, optional project/ and research/ folder choices (stubs, empty, or none), and wiki location (vault notebook or inside the project) via selectable questions. - Global tooling state check: Detects whether the wiki skills, scripts, and agent are installed, stale, partial, or missing before asking anything, and never re-copies an already-installed set. - Full project scaffolding: Creates the target folder with git init, CLAUDE.md, README.md, .gitignore, .claude/wiki-config.json, wiki folder structure, framework-contract docs, and optional Google Drive OAuth setup; supports both Claude Code and Cursor. - Use Case: A developer starting a new fitness-app project types "/new-wiki fitness-app", answers six questions, and gets a git-initialized project with a registered notebook wiki containing project/, research/, and sessions/ folders ready for /wrap-up and /wiki-update. ## Quick Start Type "/new-wiki" followed by your project name and answer the interview questions to scaffold the project and wiki.

Frequently Asked Questions about new-wiki

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

FAQPage Schema
How do I set up a new project wiki with Claude Code?▼

Run /new-wiki with a project name after the one-time machine install (install-wiki.ps1 on Windows, install-wiki.sh on Mac/Linux). The skill checks global tooling, asks a short interview about folders and wiki location, then scaffolds the project and wiki structure.

What folder structure does the new-wiki scaffold create?▼

It creates the project folder with .claude/wiki-config.json, CLAUDE.md, README.md, and .gitignore, plus a wiki root holding README, how-to/ usage docs, optional project/ and research/ folders with default stubs, sessions/, and raw/sessions/.

Does new-wiki work with Cursor as well as Claude Code?▼

Yes, it detects a .cursor/ directory and switches to the Cursor variant. Cursor mode always bundles the skills into the project and generates .cursor/rules/*.mdc files from each SKILL.md so Cursor's agent picks them up.

Why does new-wiki say the target folder has unexpected entries?▼

Phase B stops when the target folder already contains files, to avoid overwriting existing work. Re-run with --force only after confirming; it keeps any existing CLAUDE.md, README.md, and .gitignore while writing everything else.

Can I skip the research or project folder when creating a wiki?▼

Yes, both halves are opt-in with stubs, empty, or none choices. A wiki with neither folder becomes a plain notes notebook with only sessions/, and either half can be added later by creating the folder.

How do I refresh the wiki skills after pulling updates?▼

Run /new-wiki --sync to refresh the /new-wiki skill itself from the bootstrap source. Use install-wiki.ps1 -RefreshOnly or wiki-upgrade.py to refresh the full global tooling, and new-wiki.py --phase docs to refresh a project's framework-managed docs.