kb

Enforce knowledge-base rules and synchronize wiki, plan, and history folders.

1|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/pianzhu/my-claude-skills --skill kb-pianzhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb
Source: https://github.com/pianzhu/my-claude-skills/tree/main/skills/HelloAgents/kb
Command: npx skills add https://github.com/pianzhu/my-claude-skills --skill kb-pianzhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces comprehensive knowledge-base rules and automated synchronization for HelloAGENTS, ensuring consistency across documentation, planning, and history archives.

Core Features & Use Cases

  • Centralizes knowledge-base governance for HelloAGENTS workspace (helloagents/) and standard folders such as wiki/, plan/, and history/.
  • Supports knowledge synchronization, module index management, ADR maintenance, and quality checks to keep documentation up-to-date.
  • Use Case: When a new module is added or a plan is updated, run this skill to validate file structure, generate consistent metadata, and trigger KB updates.

Quick Start

Run the knowledge-base governance workflow to validate the HelloAGENTS KB structure and trigger synchronization across wiki/, plan/, and history/.

Frequently Asked Questions about kb

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

FAQPage Schema
How do I enforce knowledge-base governance rules for a HelloAGENTS workspace?

Knowledge-base governance for a HelloAGENTS workspace is enforced by validating the file structure across wiki/, plan/, and history/ directories. This process checks required files, section structures, and metadata to ensure complete documentation and ADRs.

What is the best way to maintain ADRs and change tracking in documentation?

Maintaining ADRs and change tracking requires standardized knowledge-base operations that validate history archives and plan updates. Automated synchronization triggers KB updates to keep documentation consistent when modules or plans change.

How do I validate file structure and generate metadata when a new module is added?

Validating file structure when adding a module involves running a knowledge-base workflow that checks required files and section structure. It generates consistent metadata and triggers synchronization across wiki/, plan/, and history/ folders.

Does knowledge-base governance work without external dependencies?

Knowledge-base governance operates without external dependencies, targeting the HelloAGENTS workspace internally. It manages standard folders directly to perform quality checks, module index management, and ADR maintenance independently.

When do I need to run knowledge-base synchronization for documentation?

Knowledge-base synchronization is needed when a new module is added or an existing plan is updated. Running the governance workflow validates the KB structure, checks file quality, and triggers updates to keep archives current.