doc-optimizer

Refactor Markdown documentation into deduplicated, purpose-driven files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gh-xj/claude-skills --skill doc-optimizer-gh-xj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-optimizer
Source: https://github.com/gh-xj/claude-skills/tree/main/.claude-plugin/skills/doc-optimizer
Command: npx skills add https://github.com/gh-xj/claude-skills --skill doc-optimizer-gh-xj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reduces duplication, improves structure, and lowers token usage by refactoring Markdown documentation across files to be concise and aligned with a single source of truth.

Core Features & Use Cases

  • Deduplication: Identify and remove repeated content across multiple Markdown files.
  • Structure Consolidation: Organize related sections into coherent topics and move content into purpose-driven files (README.md, data.md, tips.md).
  • Guidance for Practitioners: Provide a clear plan for token-efficient documentation and maintenance workflows.
  • Use Case: When you have multiple notes that cover the same process, run doc-optimizer to merge, prune, and normalize them into a minimal, consistent set of docs.

Quick Start

Run the doc-optimizer workflow on your docs directory to generate a compact, structured set of Markdown files (README.md, data.md, and tips.md).

Frequently Asked Questions about doc-optimizer

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

FAQPage Schema
How do I deduplicate Markdown documentation across multiple files?

Markdown documentation deduplication involves identifying repeated content across multiple files and consolidating it into a single source of truth. This skill targets multi-file projects to remove overlapping content and enforce a minimal, consistent structure.

What is the best way to structure Markdown files for token efficiency?

Structuring Markdown files for token efficiency involves converting repeated data into tables and organizing content into purpose-driven files. This approach lowers token usage by ensuring content is concise and aligned without redundant text.

How do I consolidate overlapping Markdown notes into a minimal set of docs?

Consolidating overlapping Markdown notes requires merging, pruning, and normalizing related sections into coherent topics. You can refactor multiple notes covering the same process into a compact set of structured files like README.md, data.md, and tips.md.

Does this documentation refactoring approach work with multi-file Markdown projects?

Yes, this documentation refactoring approach is specifically designed for multi-file Markdown projects with overlapping content and outdated guidance. It applies changes across README.md, data.md, and tips.md to consolidate files by purpose.

Why convert repeated Markdown data into tables?

Converting repeated Markdown data into tables enforces a token-efficient structure by replacing verbose, duplicated text with a compact format. This improves readability and lowers token usage while maintaining a single source of truth.