create-knowledge-base-page

Generate Markdown knowledge-base pages with YAML frontmatter and navigation updates.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/mk-162/162-Demo-Handbook --skill create-knowledge-base-page
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-knowledge-base-page
Source: https://github.com/mk-162/162-Demo-Handbook/tree/main/OLD-%20docs/skills/create-page
Command: npx skills add https://github.com/mk-162/162-Demo-Handbook --skill create-knowledge-base-page

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation and publication of new Markdown knowledge-base pages in a GTSE Knowledge Base, ensuring consistent frontmatter and structure.

Core Features & Use Cases

  • Generate a Markdown page under docs/<category>/<slug>.md with proper frontmatter and content.
  • Update the category index file as needed to include the new page.
  • Validate inputs like category, slug, title, and content to maintain consistency in the knowledge base.

Quick Start

Use the create-knowledge-base-page skill to publish a new page under docs/strategy with slug 'q4-plan' and title 'Q4 Plan'

Frequently Asked Questions about create-knowledge-base-page

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

FAQPage Schema
How do I publish a new Markdown knowledge-base page with consistent frontmatter?

To publish a Markdown knowledge-base page, you provide the category, slug, title, content, and nav_order inputs to generate a file under docs/<category>/<slug>.md with the required YAML frontmatter.

What is needed to structure a Markdown file for a Jekyll documentation website?

Structuring a Markdown file for a Jekyll documentation website requires YAML frontmatter containing name, title, description, and nav_order. This metadata ensures the page integrates correctly into the site's navigation and category index.

How do I update the navigation index when adding a new page to a knowledge base?

Updating the navigation index when adding a knowledge base page is handled automatically by validating category, slug, and nav_order inputs, then updating the category index file to include the new document.

Can I use this approach to generate documentation pages under a specific category directory?

Yes, you can generate documentation pages under a specific category directory by providing the category and slug inputs, which places the final Markdown file directly under docs/<category>/<slug>.md.

What are the limitations of automating Markdown page creation for a knowledge base?

A limitation of automating Markdown page creation is the strict dependency on validating specific inputs like category, slug, title, and content, meaning incomplete metadata will prevent generating the knowledge-base document.