distill

Minimize and restructure repository documentation into modular files.

2|Updated Jul 11, 2024
One-click install
npx skills add https://github.com/nicograef/handbook --skill distill-nicograef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distill
Source: https://github.com/nicograef/handbook/tree/main/.claude/skills/distill
Command: npx skills add https://github.com/nicograef/handbook --skill distill-nicograef

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of bloated, duplicated, and stale documentation that makes repositories difficult to navigate and maintain. It removes redundant prose and restructures content into small, loadable units to improve clarity for both humans and AI agents.

Core Features & Use Cases

  • Blank-Slate Re-derivation: Evaluates documentation based on whether it would be written from scratch today, rather than editing existing text.
  • Deduplication and Restructuring: Identifies conflicting information across files and splits large monoliths into focused, single-purpose documents.
  • Safety-First Execution: Operates on a plan-first basis, requiring explicit user approval before any deletions or file modifications occur.

Quick Start

Run the distill skill to analyze the current repository and generate a plan for minimizing and restructuring the documentation.

Frequently Asked Questions about distill

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

FAQPage Schema
How do I remove redundant and stale documentation from a repository?

To remove redundant documentation, this Skill analyzes Markdown and text files to delete derivable prose, resolve conflicts, and split monoliths into modular files. It generates a plan-first approach, requiring explicit approval before modifying or deleting any content.

What is blank-slate re-derivation for documentation refactoring?

Blank-slate re-derivation evaluates whether documentation would be written from scratch today, rather than incrementally editing existing text. This mechanism ensures repository prose remains a high-value, source-of-truth reference by eliminating accumulated bloat.

How do I split large Markdown documentation files into modular components?

Splitting large Markdown monoliths involves identifying focused, single-purpose content boundaries and re-organizing them into loadable units. This Skill generates a restructuring plan that divides monolithic documents to improve repository navigation and maintenance.

Do I need a clean git working tree to refactor repository documentation?

A clean git working tree is required to safely perform plan-based deletions and file re-organization of documentation. This safety-first prerequisite ensures that all structural modifications to Markdown and configuration comments can be securely managed.

Can configuration comments be minimized alongside Markdown documentation?

Configuration comments can be minimized alongside Markdown documentation. This Skill operates across configuration comments and text files to ensure all repository prose remains concise and free of redundant or derivable information.

What is the best way to deduplicate conflicting information across repository files?

The best way to deduplicate conflicting information is to analyze the repository and generate a plan that identifies contradictions across files. This Skill ensures safe, plan-based deletions and restructuring to maintain a single source of truth.