knowledge-map-format

Enforces fixed Markdown templates for nine knowledge map dimensions with citation rules.

1|2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/zhizhunbao/textbook-rag --skill knowledge-map-format-zhizhunbao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-map-format
Source: https://github.com/zhizhunbao/textbook-rag/tree/main/.agent/skills/knowledge-map-format
Command: npx skills add https://github.com/zhizhunbao/textbook-rag --skill knowledge-map-format-zhizhunbao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Knowledge map files generated across different topics often drift in structure, citation style, and section numbering, making them hard to review and maintain. This Skill defines a single enforced format so every dimension file follows identical rules. ## Core Features & Use Cases - Fixed Dimension Templates: Provides mandatory chapter structures for all 9 dimensions (Map, Concepts, Math, Tutorial, Usage, Code, Pitfalls, History, Bridge), including section numbering and required tables. - Formatting Rules (R1-R7): Enforces frontmatter fields, per-section citation blocks, no nested code fences, ❌/✅ comparison formatting, separator rules, and source directory conventions (textbooks/, .documents/, .github/). - Quality Checklist: Ships a review checklist covering frontmatter completeness, citations, chapter counts, keyword formatting, and file naming ({topic}_{dimension}.md). - Use Case: When running /generate-knowledge-map for a new topic, apply these templates so the Math dimension includes a symbol table, intuition-first formulas with derivations, and worked numeric exercises, while Pitfalls entries follow the scenario/symptom/root-cause/fix/lesson structure. ## Quick Start Generate the knowledge map files for this topic using the knowledge-map-format templates and verify them against the quality checklist.

Frequently Asked Questions about knowledge-map-format

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

FAQPage Schema
How do I generate knowledge map files with a consistent format?▼

Apply the fixed templates defined for each of the 9 dimensions (Map, Concepts, Math, Tutorial, Usage, Code, Pitfalls, History, Bridge). Each dimension has mandatory chapter numbering, required tables, and per-section citation blocks that must be followed exactly.

What frontmatter fields are required in knowledge map files?▼

Each file needs topic, dimension, created, last_verified, source_versions, expiry (3m/6m/12m/never), and status (current/needs_review/outdated). Source versions must link to actual files in textbooks/, data/mineru_output/, .documents/, or .github/ directories.

Why does nested code block rendering break in Markdown knowledge files?▼

Nesting a bash code fence inside a markdown code fence causes rendering failure. The format rules require using 4-space indentation for inner code instead of nested fences, especially in ❌/✅ comparison examples.

Can I cite my own generated code as a source in knowledge maps?▼

No. The rules prohibit citing self-generated code or workspace source as authority for theoretical concepts. Citations must link to textbooks, MinerU outputs, official docs in .documents/, public papers, or open-source repos in .github/.

When should the Math dimension be skipped in a knowledge map?▼

Skip the Math dimension when the topic has no mathematical content, such as Docker or Git. Mark it with strikethrough and a not-applicable note in the Map file's file map table instead of generating an empty file.