tools/mdli

Edit, validate, and synchronize structured Markdown files in automated workflows.

2|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/weisberg/agent_tools --skill tools-mdli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tools/mdli
Source: https://github.com/weisberg/agent_tools/tree/main/tools/mdli
Command: npx skills add https://github.com/weisberg/agent_tools --skill tools-mdli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Managing structured Markdown documents is challenging due to inconsistent formatting and difficulty in making repeatable edits.

Core Features & Use Cases

  • Idempotent Document Updates: Ensure safe, repeatable modifications to sections, tables, blocks, and frontmatter.
  • Semantic Diffing and Validation: Detect structural changes and validate document schemas for quality assurance.
  • Use Case: Automate updating a status report with new data, ensuring no unintended changes or duplicates, and easily review differences before committing.

Quick Start

Use tools/mdli to ensure the presence of a specific section in a Markdown file.

Frequently Asked Questions about tools/mdli

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

FAQPage Schema
How do I automate updating Markdown files without introducing duplicate sections?

Automated Markdown editing prevents duplicates by applying idempotent updates to sections, tables, and frontmatter. This ensures safe, repeatable modifications to structured documents without unintended changes or content drift.

What is semantic diffing for Markdown and how does it validate structured content?

Semantic diffing for Markdown validates structured content by detecting structural changes rather than just text differences. It checks document schemas to ensure quality assurance and prevent formatting errors in knowledge bases.

How do I validate Markdown frontmatter and schemas for long-term documentation?

Validating Markdown frontmatter and schemas for long-term documentation requires a schema-aware engine. It checks structured content blocks to prevent drift and ensure consistent formatting across versioned project reports.

Can I use automated editing to synchronize complex Markdown tables in automated workflows?

Automated editing synchronizes complex Markdown tables in automated workflows by parsing structured content robustly. It supports change tracking and review needs, ensuring updates to blocks and tables remain consistent.

What's the best way to track structural changes in versioned Markdown knowledge bases?

Tracking structural changes in versioned Markdown knowledge bases is best handled through semantic diffing. It detects document structure modifications, allowing you to review differences and validate schemas before committing updates.

Why does Markdown formatting drift when automating status report updates?

Markdown formatting drifts during automated status report updates due to inconsistent parsing and lack of schema validation. Using a schema-aware engine prevents these errors by applying idempotent updates to specific sections.