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.From its SKILL.md

Install

npx -y skills add hogu-dev/llmkb --skill kb-init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.2 KB, 285 tokens by cl100k_base, as published. Nobody here has run it

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

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.
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?
Tailor SCHEMA.md with their answers — add project-specific page-type guidance, tag vocabulary, and tone/length rules. Keep the required frontmatter contract intact.
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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.