abd-chunk-markdown

Chunk converted Markdown into retrieval-sized sections with YAML front matter metadata.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/agilebydesign/agilebydesign-skills --skill abd-chunk-markdown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: abd-chunk-markdown
Source: https://github.com/agilebydesign/agilebydesign-skills/tree/main/agents/abd-context-to-memory/skills/abd-chunk-markdown
Command: npx skills add https://github.com/agilebydesign/agilebydesign-skills --skill abd-chunk-markdown

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-dotenv, and includes scripts (resource) components.

What problem does it solve?

Split large Markdown files into retrieval-sized chunks with evidence labels, enabling efficient memory and retrieval workflows.

Core Features & Use Cases

  • Structure-aware chunking using section_boundaries, headings, and optional chunk_inputs.
  • Draft and apply a memory/context_chunking_spec.yaml to govern chunk sizes, taxonomy, and front matter.
  • Produce memory chunks with YAML front matter and section_path metadata for downstream embedding and search.

Quick Start

Run the chunk_markdown workflow on your topic folder to produce memory chunks with front matter for downstream embedding.

Frequently Asked Questions about abd-chunk-markdown

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

FAQPage Schema
How do I chunk Markdown files into retrieval-ready memory chunks for RAG workflows?

You can chunk Markdown for RAG by applying a context_chunking_spec.yaml to guide structure-aware splitting. This produces memory chunks with YAML front matter containing chunk_id, section_path, and taxonomy defaults ready for downstream embedding and retrieval.

What is structure-aware Markdown chunking and how does it handle section boundaries?

Structure-aware Markdown chunking splits documents using section_boundaries, headings, and chapter markers. Each resulting chunk retains its section_path and evidence metadata in YAML front matter, preserving document hierarchy for accurate downstream retrieval.

How do I add evidence metadata and taxonomy defaults to Markdown chunks?

Adding evidence metadata to Markdown chunks requires injecting YAML front matter into each segment during the chunking process. The system automatically tags each chunk with a chunk_id, section_path, and taxonomy defaults specified by your context_chunking_spec.yaml file.

Can I use a chunking specification file to control Markdown chunk sizes and front matter?

Yes, you can draft and apply a memory/context_chunking_spec.yaml to govern chunk sizes, taxonomy, and front matter. This specification file guides the structure-aware chunking process to ensure the output meets your specific retrieval and memory workflow requirements.

What is the best way to prepare converted Markdown for downstream embedding and search?

The best way to prepare converted Markdown for embedding is to chunk it into retrieval-sized segments with evidence labels. Applying a context_chunking_spec.yaml ensures each chunk includes YAML front matter with section_path metadata for efficient search.

Do I need python-dotenv to run Markdown chunking workflows?

Yes, python-dotenv is a required dependency for running the Markdown chunking scripts. You need this environment setup to execute the workflow that processes your topic folders and produces memory chunks with front matter.