dbs-knowledge

Organize local folders into navigable knowledge bases with version rules and health checks.

9.8k|1.1k|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/dontbesilent2025/dbskill --skill dbs-knowledge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dbs-knowledge
Source: https://github.com/dontbesilent2025/dbskill/tree/main/skills/dbs-knowledge
Command: npx skills add https://github.com/dontbesilent2025/dbskill --skill dbs-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Local files scattered across folders are hard for an AI agent to find, trust, and maintain. This Skill turns any folder into a structured knowledge base with a navigation file, version conflict rules, and agent entry points, so the agent can reliably locate, store, and cite your materials.

Core Features & Use Cases

  • Build: Audit a folder read-only, then generate a SOURCE_OF_TRUTH.md navigation file plus AGENTS.md and CLAUDE.md entry points for cross-agent discovery.
  • Store & Retrieve: Place new materials in the right directory without overwriting duplicates, and answer questions by reading original files with cited paths, freshness, and gaps.
  • Health Check & Slimming: Detect broken paths, duplicate "latest versions", and bloated navigation, then merge, sink details into local README.md files, and back up before rewriting.
  • Use Case: You have a folder full of course notes, drafts, and client documents. Run the Skill to generate a navigation map, then later ask "find my latest pricing notes" or "add this file to the knowledge base" in plain language.

Quick Start

Use the dbs-knowledge skill to turn this folder into a knowledge base and show me how to query it.

Frequently Asked Questions about dbs-knowledge

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

FAQPage Schema
How do I turn a local folder into an AI-searchable knowledge base?

Point the agent at your folder and it performs a read-only audit, then generates a SOURCE_OF_TRUTH.md navigation file mapping what to find, where it lives, and which version is authoritative. It also adds AGENTS.md and CLAUDE.md entry points so agents consult the navigation automatically.

How to manage file versions and duplicates in a local knowledge base?

The navigation file records explicit version and conflict rules, and new files are never overwritten on name collision; dates, versions, or sources create distinct names. When evidence is insufficient, conflicts stay marked as pending confirmation rather than guessing an authoritative version.

Does this knowledge base approach require a vector database or embeddings?

No. It deliberately avoids databases, vector stores, embedding services, and RAG pipelines. Everything runs on plain Markdown navigation files and directory README.md indexes that any agent can read directly.

Can Claude Code and other agents share the same knowledge base?

Yes. AGENTS.md serves as the shared project entry for Codex, WorkBuddy, and similar agents, while CLAUDE.md acts as a thin Claude Code pointer importing those rules. The navigation file itself stays host-independent.

What happens when the knowledge base navigation file gets too large?

A governance mode audits entry density, merges duplicate topic entries into single main entrances, and sinks file-level details into per-directory README.md indexes. The original navigation is backed up before any rewrite, and paths are re-validated afterward.

Will it move or delete my files without asking?

No. Audits and queries are read-only by default. Any move, rename, overwrite, delete, or batch change requires a preview listing affected paths and explicit user confirmation before execution.