Kb Search logo

Kb Search

Organization
BlackBeltTechnology
kb-search

Search the local markdown knowledge base for facts, prior decisions, definitions, people, error codes, config flags, and how-we-fixed-it notes. ALWAYS search here BEFORE answering a project-specific question from memory, guessing, or asking the user. Use whenever you hit an unknown term, an unfamiliar entity, an error string, or a "how do we do X / why did we choose Y" question.

Overview

PublisherBlackBeltTechnology
Repositorypi-agent-dashboard
Skill namekb-search
Stars
330
Forks
51
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 BlackBeltTechnology on GitHub. Read the source before you install it.

Installation

Install the Kb Search 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/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/kb/skill/kb-search
  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/BlackBeltTechnology/pi-agent-dashboard.git /tmp/pi-agent-dashboard
mkdir -p .claude/skills
cp -r /tmp/pi-agent-dashboard/packages/kb/skill/kb-search .claude/skills/kb-search
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Kb Search 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 Kb Search 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 Kb Search 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.

kb-search — retrieve before you answer

A fast, local, zero-token FTS5 knowledge base over this project's markdown (@blackbelt-technology/pi-dashboard-kb). Retrieval is pull: you call it; nothing is auto-injected. Sub-second, deterministic, costs no model tokens — so call it freely on any uncertainty.

When to Use

  • Hit an unknown name / term / error string / config flag / function.
  • Need a past decision, convention, or "how we did X".
  • About to answer a factual question about this project from memory.
  • About to ask the user something the docs may already answer.

Procedure

  1. Extract the key entities from the problem (names, error strings, slugs, config keys, function names).
  2. Run: kb search "<entities>" --limit 8 --json
  3. Read only the top 1–2 hits' full content when needed: kb get <path> --section "<heading_path>"
  4. Still unresolved? Walk the graph from a hit: kb neighbors "<heading_path>" --depth 2 and kb backlinks "<path>".
  5. Paraphrase miss? Lexical search is weak when your words differ from the docs' words. Reformulate once using the domain's actual terms (synonyms, the real flag/class names) and re-search. Then escalate to the user only if the KB returns nothing relevant.
  6. Synthesize from the retrieved sections. Cite the path you used.

Pitfalls

  • Do NOT answer project-specific questions from memory without searching first.
  • Do NOT read whole files — search returns ranked sections with snippets; open full content only for the top hits.
  • Empty result is not a stop sign — reformulate with domain terms once, then ask.
  • Filter when you only want rules: kb search "<q>" --doc-type agents.

Verification

  • kb search returns ranked {path, headingPath, score, snippet} (lower score = more relevant).
  • Freshness is automatic: kb search runs an incremental reindex first unless --no-reindex.
  • Requires @blackbelt-technology/pi-dashboard-kb installed (kb on PATH) and a configured source (.pi/dashboard/knowledge_base.json or --source <dir>).

Frequently asked questions

What does the Kb Search AI skill do?

Search the local markdown knowledge base for facts, prior decisions, definitions, people, error codes, config flags, and how-we-fixed-it notes. ALWAYS search here BEFORE answering a project-specific question from memory, guessing, or asking the user. Use whenever you hit an unknown term, an unfamiliar entity, an error string, or a "how do we do X / why did we choose Y" question.

Why use Kb Search on TypingMind?

Because you install it once and use it with any model. Kb Search 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 Kb Search in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/kb/skill/kb-search. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Kb Search?

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 Kb Search?

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

Is the Kb Search AI skill free?

Yes. It is published on GitHub by BlackBeltTechnology 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 👇