knowledge-base-management

Organizes persistent agent knowledge into categorized markdown files with memory archiving rules.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/CHENHUI-X/toolbox --skill knowledge-base-management-chenhui-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-base-management
Source: https://github.com/CHENHUI-X/toolbox/tree/main/custom-skills/productivity/knowledge-base-management
Command: npx skills add https://github.com/CHENHUI-X/toolbox --skill knowledge-base-management-chenhui-x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents have limited memory capacity, and valuable information like credentials, server configs, and user preferences gets lost when memory fills up. This Skill sets up a persistent, categorized markdown knowledge base so nothing important is ever deleted. ## Core Features & Use Cases - Categorized Knowledge Base: Creates a directory tree of markdown files under /home/projects/hermes-knowledge/ with categories for credentials, environment configs, habit rules, and memory archives. - Memory Archiving Workflow: When agent memory approaches capacity (~80%), old entries are archived to dated markdown files before removal, never deleted outright. - Lookup-First Rules: Enforces two permanent memory rules — archive before deleting, and search the knowledge base before asking the user to repeat information. - Use Case: A user shares an API key and server topology in chat. The agent files the key under 账号密码/ and the topology under 环境配置/, then weeks later retrieves them from the knowledge base when memory no longer holds them. ## Quick Start Set up a categorized knowledge base for me with folders for credentials, configs, habits, and memory archives, and record the two iron rules in memory.

Frequently Asked Questions about knowledge-base-management

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

FAQPage Schema
How do I prevent an AI agent from losing information when its memory is full?

Archive old memory entries to dated markdown files in a knowledge base directory before removing them from active memory. This Skill triggers archiving at roughly 80% memory capacity and records permanent rules so the behavior persists every turn.

How to organize credentials and configs for an AI agent?

Store them in categorized markdown files: credentials and tokens under an accounts folder, server and network configs under an environment folder, and user preferences under a habits folder. Each file gets timestamps and context notes.

Should credentials be stored in agent memory or files?

Credentials should be stored in knowledge base files, not active memory, because memory is injected into every turn and has limited capacity. The agent records a pointer noting where the credential file lives instead.

What happens when the agent cannot find information in memory?

The lookup-first rule requires searching all knowledge base subdirectories with file search before asking the user to repeat themselves. Files remain in place after reading and are never moved or deleted.

What are the limitations of a file-based knowledge base for agents?

It requires file I/O on every lookup, so over-archiving forces constant disk reads for common questions. It also lacks encryption, so plaintext credential files should not be committed to git.