Setup Knowledge Base logo

Setup Knowledge Base

Organization
techwolf-ai
setup-knowledge-base

Interactive onboarding to create a structured knowledge base. Defines categories, scaffolds the directory structure, creates the index, and optionally imports initial content. Run this first before using /kb-answer or /kb-import.

Overview

Publishertechwolf-ai
Repositoryai-first-toolkit
Skill namesetup-knowledge-base
Stars
138
Forks
7
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by techwolf-ai on GitHub. Read the source before you install it.

Installation

Install the Setup Knowledge Base AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/knowledge-base/skills/setup-knowledge-base
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkit.git /tmp/ai-first-toolkit
mkdir -p .claude/skills
cp -r /tmp/ai-first-toolkit/plugins/knowledge-base/skills/setup-knowledge-base .claude/skills/setup-knowledge-base
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Setup Knowledge Base in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Setup Knowledge Base on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Setup Knowledge Base is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Knowledge Base Setup

Interactive setup that creates a structured, evidence-backed knowledge base in your project.

When to Use

  • Starting a new knowledge base from scratch
  • Adding a KB to an existing project

Step 1: Discover Purpose

Ask the user (one question at a time, use AskUserQuestion):

  1. What is this KB for? (e.g., product documentation, security/compliance, company knowledge, sales enablement, internal policies)
  2. Who will query it? (e.g., you personally, your team, AI agents answering questions)
  3. What categories make sense? Suggest 3-5 based on the domain, let the user adjust.

Example category suggestions by domain:

  • Product docs: technical, integrations, deployment, security, faq
  • Company knowledge: general, policies, processes, teams, faq
  • Sales enablement: product, competitive, customer-success, pricing, faq
  • Security/compliance: security, compliance, technical, general, faq

Step 2: Confirm Plan

Before creating anything, present the plan to the user:

I'll create this structure in your project:

kb/
  .kb-config.yaml
  index.md
  scopes/
    _default.yaml
    README.md
  {category1}/
  {category2}/
  {category3}/
scripts/
  kb-index.py
  kb-verify.py
  kb-validate.py
  kb-search.py
CLAUDE.md (or append to existing)

Ready to proceed?

Wait for user confirmation.

Step 3: Scaffold the KB

Read the template files from this plugin and adapt them for the user's project:

  1. Read templates/kb/.kb-config.yaml from this plugin. Create kb/.kb-config.yaml in the user's project, replacing the placeholder categories with the ones chosen in Step 1. Replace {{today}} with today's date.

  2. Read templates/kb/index.md from this plugin. Create kb/index.md, adding seed keywords for each chosen category. For example, if the user chose "security" and "technical", add initial keyword entries:

    | encryption, certificates, access | security/ |
    | API, architecture, deployment | technical/ |
  3. Read templates/kb/scopes/_default.yaml from this plugin. Copy to kb/scopes/_default.yaml.

  4. Read templates/kb/scopes/README.md from this plugin. Copy to kb/scopes/README.md.

  5. Create empty directories for each chosen category: kb/{category1}/, kb/{category2}/, etc.

  6. Read scripts/kb-index.py from this plugin. Copy to scripts/kb-index.py in the user's project.

  7. Read scripts/kb-verify.py from this plugin. Copy to scripts/kb-verify.py in the user's project.

  8. Read scripts/kb-validate.py from this plugin. Copy to scripts/kb-validate.py in the user's project.

  9. Read scripts/kb-search.py from this plugin. Copy to scripts/kb-search.py in the user's project.

Step 4: Create Project CLAUDE.md

Read templates/CLAUDE.md from this plugin. Create (or append to existing) CLAUDE.md in the user's project root. Replace {{category}} placeholders with the actual categories chosen in Step 1.

Step 5: Populate from Sources

The KB structure is ready, but empty. Ask the user:

"Do you have existing knowledge sources you'd like to import? (Notion pages, Slack channels, Confluence, local files)"

  • If yes: run /kb-refresh to populate the KB from those sources. It handles source discovery, scraping, and entry creation.
  • If no or skip: create one example entry in the first category to demonstrate the format. Read templates/kb/example/sample-entry.md from this plugin for the format, but write an entry relevant to the user's domain rather than copying the sample.

Step 6: Verify

Run the index script to confirm everything is wired up:

bash
python3 scripts/kb-index.py

Regenerate the "All Files by Category" section of kb/index.md from the current entries:

bash
python3 scripts/kb-index.py --write

Validate KB health (frontmatter, categories, related links):

bash
python3 scripts/kb-validate.py

If kb-index.py lists the entries and kb-validate.py reports "All entries valid", setup is complete.

Step 7: Summary

Tell the user:

  • What was created and where
  • How to add new entries (create .md files with YAML frontmatter in the right kb/{category}/ folder; nested sub-folders like kb/security/access/ are supported)
  • How to query the KB (/kb-answer)
  • How to import documents or bulk-import a directory (/kb-import)
  • How to add more sources or refresh existing ones (/kb-refresh)
  • How to list all entries (python3 scripts/kb-index.py)
  • How to search (python3 scripts/kb-search.py "keyword")

Frequently asked questions

What does the Setup Knowledge Base AI skill do?

Interactive onboarding to create a structured knowledge base. Defines categories, scaffolds the directory structure, creates the index, and optionally imports initial content. Run this first before using /kb-answer or /kb-import.

Why use Setup Knowledge Base on TypingMind?

Because you install it once and use it with any model. Setup Knowledge Base is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Setup Knowledge Base in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/knowledge-base/skills/setup-knowledge-base. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Setup Knowledge Base?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Setup Knowledge Base?

As many as you like. As long as a model supports skills, you can use Setup Knowledge Base with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Setup Knowledge Base AI skill free?

Yes. It is published on GitHub by techwolf-ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇