kb-research-policy

Route and retrieve notes from a three-layer knowledge base using index-first search.

2|1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/kelp/kelp-claude-plugins --skill kb-research-policy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-research-policy
Source: https://github.com/kelp/kelp-claude-plugins/tree/main/plugins/knowledge-forge/skills/kb-research-policy
Command: npx skills add https://github.com/kelp/kelp-claude-plugins --skill kb-research-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a consistent, efficient policy for locating and retrieving past research, notes, and source material from a personal knowledge base so agents avoid wasting context or opening large notes prematurely.

Core Features & Use Cases

  • Index-first routing: Read cheap one-line index files to build a shortlist before fetching full notes.
  • MCP-backed search: Use qmd MCP lex and vec queries with intent to balance exact and fuzzy matches across curated and external collections.
  • Health and maintenance: Run simple checks and reindexing via project tasks to ensure the KB remains discoverable and fresh.
  • Use Case: Shortlist relevant wiki pages for a research query, validate findings against sources, and only open full notes when the candidate list is small.

Quick Start

Search the knowledge base for "what do we know about <topic>" and return a shortlist of candidate notes before opening full pages.

Frequently Asked Questions about kb-research-policy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search my personal knowledge base to find relevant past research notes?

To search a personal knowledge base, read cheap one-line index files first to build a shortlist of candidate notes, then use qmd MCP lex and vec searches with intent to balance exact and fuzzy matches before fetching full pages.

What is the best way to retrieve notes from a three-layer knowledge base without wasting context?

The best way to retrieve notes from a three-layer knowledge base is index-first routing: read index files to shortlist candidates across raw, wiki, and index layers, and only open full notes when the candidate list is small to avoid wasting context.

How does qmd MCP lex and vec search work for knowledge base retrieval?

Qmd MCP lex and vec search queries use intent to balance exact and fuzzy matches across curated and external collections, allowing you to shortlist relevant wiki pages for a research query before opening full notes for validation.

Can I run health checks and reindexing workflows on my personal knowledge base?

Yes, you can run simple health checks and reindexing via project tasks to ensure your personal knowledge base remains discoverable and fresh for future research queries and retrieval operations.

When should I avoid opening full notes during a research knowledge base search?

You should avoid opening full notes during a knowledge base search until after you have shortlisted candidates using index files and qmd MCP searches, preventing premature opening of large notes and context waste.

Do I need to read index files first before fetching full notes from my knowledge base?

Yes, you need to read index files first to build a shortlist before fetching full notes, as index-first routing ensures efficient retrieval and prevents opening large notes prematurely during research queries.