Knowledge Base Builder

Design personal or team knowledge bases that make information findable, useful, and up-to-date. Transforms scattered documents, notes, and tribal knowledge into an organized, searchable system.

Usage

Describe the knowledge you need to organize, the audience, and your preferred tools. The skill produces:

• Information Architecture: Top-level categories and hierarchy
• Taxonomy: Tags, labels, and metadata schema for findability
• Article Templates: Standardized formats for different content types
• Style Guide: Writing standards for consistency across contributors
• Search Optimization: Titling and tagging conventions for easy discovery
• Contribution Workflow: How new content gets created, reviewed, and published
• Maintenance Plan: Regular review cycles to keep content current

Examples

1. Engineering Wiki: "Design a knowledge base for a 30-person engineering team. Need: architecture docs, runbooks, onboarding guides, API docs, and decision logs."

1. Personal PKM: "Set up a personal knowledge management system. I take notes on books, articles, podcasts, and meetings. Currently in 5 different apps, nothing connected."

1. Customer Support: "Build a knowledge base for our customer support team. 50 common questions, 20 troubleshooting guides, product documentation, and escalation procedures."

1. Company Handbook: "Design a company handbook/wiki for a 100-person remote company. Cover: policies, processes, tools, culture, benefits, and department-specific guides."

Guidelines

• Start with the 20% of knowledge that answers 80% of questions — don't try to document everything at once
• Use clear, descriptive titles — people search by how they think about a problem, not your internal terminology
• Every article needs an owner responsible for keeping it accurate
• Set up a quarterly review cycle: each article gets verified or updated every 90 days
• Make contribution easy: low-friction templates, clear guidelines, lightweight review process
• Include a "last verified" date on every article so readers know if content might be stale
• Link related articles to each other — knowledge bases are networks, not filing cabinets