Kb init

Skill hogu-dev/llmkb/skills/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.

2 things to look at

28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
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.

Gives 0 of the 12 instructions most project setup skills give in 285 tokens

Counted across 999 of the 1,637 authors here whose files we hold, read 2026-08-07

Ask one question at a timein 29 of 999, across 28 files
Detect the package manager from lockfilesin 28 of 999, across 9 files
Present findings to the userin 26 of 999, across 5 files
Explore current repo statein 24 of 999, across 3 files
Update the agent skills block in place if it existsin 24 of 999, across 3 files
Install husky lint-staged and prettierin 23 of 999, across 4 files
Create the lintstagedrc filein 22 of 999, across 3 files
Commit all changed filesin 22 of 999, across 3 files
Run lint-staged to verify it worksin 22 of 999, across 3 files
Create the husky pre-commit filein 21 of 999, across 2 files
Create a prettierrc file if missingin 21 of 999, across 2 files
Initialize huskyin 21 of 999, across 2 files

Said here and by no other author read

run llmkb init with name and description
interview user about domain and conventions
tailor SCHEMA.md with interview answers
keep required frontmatter contract intact
run llmkb lint to confirm health
append init entry to log.md

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.