This skill should be used when the user asks to "set up KB explorer", "add a knowledge base", "explore this repo", "visualize the knowledge graph", "bootstrap kbexplorer", "configure kbexplorer", "run the knowledge base", "view issues as a graph", "browse repo knowledge", or mentions kbexplorer, knowledge base explorer, or knowledge graph visualization. Provides guidance for setting up, configuring, and running the kbexplorer interactive knowledge base tool — either as a submodule in another repo or self-hosted.
kbexplorer transforms any GitHub repository into a navigable, interactive knowledge graph. It visualizes issues, pull requests, README files, source directories, and hand-authored markdown as an interconnected constellation — explorable through card grids, force-directed networks, and deep-dive reading views.
Activate this skill when a user wants to:
The setup is fully agent-driven. The agent executes every step — the user only answers configuration questions during the interactive wizard.
If the current repo IS kbexplorer (check package.json name or git remote), skip submodule
setup. Run the init wizard directly, then start the dev server and validate:
node scripts/init.js # interactive config questions
npm run dev # agent starts this
# agent validates with playwright-cli
The agent performs these steps in order:
Add the submodule (agent runs this):
git submodule add https://github.com/anokye-labs/kbexplorer.git .kbexplorer
Run the interactive init wizard (user answers config questions):
node .kbexplorer/scripts/init.js
The wizard asks about content mode, title, visual style, theme, and features.
It creates .env.kbexplorer, content/config.yaml, adds npm scripts, and
installs dependencies automatically.
Start the explorer (agent runs this):
npm run kb:dev
Validate with playwright-cli (agent does this — MANDATORY):
Navigate to http://localhost:5173, take a screenshot, evaluate with vision.
| File | Purpose |
|---|---|
.env.kbexplorer | Vite env vars (VITE_KB_OWNER, VITE_KB_REPO, etc.) — gitignored |
content/config.yaml | Full kbexplorer configuration |
package.json updates | kb:dev, kb:build, kb:install scripts |
.gitignore update | Ensures .env.kbexplorer is ignored |
No content path set. kbexplorer auto-discovers issues, PRs, README, and source directories
from the target GitHub repo. Issue labels become clusters; #N cross-references become edges.
Set source.path to a directory of markdown files (e.g., content/). Each file's YAML
frontmatter defines node metadata, hierarchy, and connections. Full control over the graph.
---