knowledge-engineering

Guides restructuring of external project documentation into structured, AI-indexable knowledge bases.

2.9k|733|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/zts212653/clowder-ai --skill knowledge-engineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-engineering
Source: https://github.com/zts212653/clowder-ai/tree/main/cat-cafe-skills/knowledge-engineering
Command: npx skills add https://github.com/zts212653/clowder-ai --skill knowledge-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External projects often lack structured documentation, so AI agents scanning them produce shallow, low-value understanding. This Skill turns implicit team knowledge into explicit, structured documents that AI memory engines can index and retrieve.

Core Features & Use Cases

  • Documentation Assessment: Diagnoses a project's documentation state across four scenarios (structured docs, code-only, scattered docs, split repos) and recommends an appropriate path.
  • Guided vs Autonomous Paths: Presents a Guided path (3-7 days of structured knowledge building) or an Autonomous path (scanning existing docs) and lets the user decide.
  • Three-Layer Knowledge Injection: Produces a domain glossary, business rules table, action mapping, and reusable pattern documents with YAML frontmatter templates ready for FTS5 and vector indexing.
  • Use Case: When deploying an AI agent into a client's codebase that has no docs, use this Skill to derive a documentation skeleton from code structure, then guide the team to fill in business concepts, rules, and operation mappings.

Quick Start

Ask the AI to evaluate my project's documentation status and guide me through building a structured knowledge base for it.

Frequently Asked Questions about knowledge-engineering

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

FAQPage Schema
How do I make my project documentation understandable to AI agents?

Convert implicit team knowledge into structured Markdown documents with YAML frontmatter: a domain glossary, business rules table, action mapping, and reusable patterns. Place them in the project so the memory engine can index them for full-text and semantic search.

What is the difference between the Guided and Autonomous documentation paths?

The Guided path takes 3-7 days where the AI guides you to build a structured knowledge system with high-confidence retrieval. The Autonomous path scans your existing docs as-is, which is faster but limited by current documentation quality.

How do I handle documentation scattered across wiki, Confluence, or Feishu?

Inventory external documents, migrate must-have content like concept definitions and API docs into the repository as Markdown with frontmatter, and keep links for low-priority items. Create an index in docs/README.md pointing to external locations.

Can AI understand a project that has only code and no documentation?

Yes, partially. The Skill derives a documentation skeleton from directory structure, class and function names, test files, and configs, then generates templates for the team to fill in. Scanning alone yields shallow understanding without this step.

When should I not use this knowledge engineering skill?

Skip it when the project already has a docs/ directory with Markdown files containing YAML frontmatter, since scanners can index that directly. It is also not intended for the cat-cafe project's own development.