# Kb Init

> Use to create a new `llmkb` knowledge base for a project — scaffold it with llmkb init, then interview the user briefly to tailor SCHEMA.md to the project's domain and conventions.

- Skill: `hogu-dev/kb-init` (Agent Skill)
- Install (CLI): `npx skillmds@latest add hogu-dev/kb-init`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hogu-dev/kb-init/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: hogu-dev (https://skillmd.com/u/hogu-dev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hogu-dev/kb-init

---


# kb-init

Create and tailor a new `llmkb` knowledge base for a project.

## When to use

Starting a KB for a new project, or the user asks to set one up.

## Steps

1. **Scaffold.** Run `llmkb init <dir> --name <name> --description "<one line>"`.
   This creates the directory structure, `kb.yaml`, a starter `SCHEMA.md`, the
   `.llmkb/` gitignore, empty `index.md`/`log.md`, and a git repo.
2. **Interview briefly.** Ask the user:
   - What domain does this KB cover, and what will it mostly ingest?
   - Any naming or tagging conventions they want enforced?
   - What counts as a concept vs an entity here?
3. **Tailor `SCHEMA.md`** with their answers — add project-specific page-type
   guidance, tag vocabulary, and tone/length rules. Keep the required
   frontmatter contract intact.
4. **Confirm health.** Run `llmkb lint` (an empty KB should be clean) and append a
   `## [YYYY-MM-DD] init | <name>` line to `wiki/log.md`.

## Done when

The KB exists, `SCHEMA.md` reflects the project, and `llmkb lint` is clean.