rcode-distillator

Compress source documents into lossless, LLM-ready markdown distillates.

2|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-distillator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rcode-distillator
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/core/rcode-distillator
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-distillator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

rcode-distillator turns source documents into a dense, lossless distillate so an LLM can load the essential facts, decisions, entities, and relationships without unnecessary prose.

Core Features & Use Cases

  • Lossless compression: Preserves every meaningful heading, named entity, constraint, decision, and relationship while removing repetition and filler.
  • Thematic organization: Groups content into compact markdown themes that are easy for downstream models to scan and reuse.
  • Semantic splitting: Breaks large source sets into coherent section distillates when token budgets or document size require it.
  • Round-trip validation: Can reconstruct and compare against the original sources to catch gaps and hallucinations.
  • Use case: Distill architecture notes, PRDs, research reports, or mixed documentation folders into a single LLM-ready context file for analysis, planning, or review.

Quick Start

Ask the skill to distill the selected source documents into a lossless markdown distillate for your chosen downstream consumer.

Frequently Asked Questions about rcode-distillator

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

FAQPage Schema
How do I compress markdown documentation into lossless LLM context?

Lossless document compression for LLM context works by applying thematic compression rules and semantic splitting to preserve headings, named entities, decisions, and relationships while removing repetition and filler. The output is a dense markdown distillate ready for downstream model consumption.

Can I distill mixed JSON and YAML source files into a single context file?

Yes, you can distill mixed JSON, YAML, text, and markdown documentation sets into a single LLM-ready context file. The analyzer processes mixed documentation folders and groups content into compact markdown themes for downstream comparison, analysis, or archival condensation.

What is semantic splitting and when do I need it for document distillation?

Semantic splitting breaks large source documentation sets into coherent section distillates when token budgets or document size require it. This allows the distillation process to handle large architecture notes, PRDs, or research reports without exceeding downstream model context limits.

Does round-trip validation catch hallucinations in compressed LLM context?

Round-trip validation catches hallucinations in compressed LLM context by reconstructing and comparing distillates against original sources to identify gaps. It ensures the compression preserved every meaningful heading, named entity, constraint, decision, and relationship without losing critical information.

What's the best way to prepare architecture notes and PRDs for LLM analysis?

The best way to prepare architecture notes and PRDs for LLM analysis is to distill them into a lossless markdown context file using thematic compression. This removes unnecessary prose while preserving decisions, constraints, and relationships for dense context loading during downstream planning or review.