bmad-distillator

Compress source documents into lossless, token-budgeted bullet distillates.

4|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/curdx/curdx-flow --skill bmad-distillator-curdx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-distillator
Source: https://github.com/curdx/curdx-flow/tree/main/.agents/skills/bmad-distillator
Command: npx skills add https://github.com/curdx/curdx-flow --skill bmad-distillator-curdx

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the problem of wasting context window tokens and cluttering prompts with bulky source documents, by turning multiple inputs into a single lossless, token-efficient distillate that an LLM workflow can consume without information loss.

Core Features & Use Cases

  • Lossless document distillation: Preserves every fact, decision, constraint, and relationship while stripping overhead, optimized for downstream LLM consumption.
  • Semantic splitting by token budget: Automatically splits output into an index plus self-contained topic sections when outputs would exceed a target size.
  • Verification and optional round-trip validation: Checks completeness and format rules, and can optionally reconstruct originals from the distillate to test losslessness.

Quick Start

Provide the Skill with your source documents and a destination output path, and it will generate a distillate that fits your token budget while preserving all required information.

Frequently Asked Questions about bmad-distillator

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

FAQPage Schema
How do I compress source documents for LLM context without losing information?

Lossless document distillation compresses multiple inputs into a dense, bullet-based distillate optimized for downstream LLM consumption. It preserves every fact, decision, constraint, and relationship while stripping overhead to save context window tokens.

How does semantic splitting work when a distillation output exceeds a token budget?

Semantic splitting by token budget automatically divides output into an index plus self-contained topic sections when results exceed a target size. This ensures generated distillates fit precisely within specified LLM context constraints without breaking topical coherence.

Can I validate that document compression preserved all original facts?

Verification and optional round-trip validation check distillate completeness and format rules, and can optionally reconstruct originals from the distillate to test losslessness. This confirms every fact survived the token optimization process.

What is the best way to optimize multiple bulky documents for a specific LLM workflow?

Provide source documents and a destination output path to generate a token-efficient distillate. The process applies stage-based routing, theme extraction, and deduplication to produce a single lossless output tailored to your downstream consumer's needs.

Are there limitations to lossless document distillation for large file processing?

When outputs exceed the token budget, distillation triggers semantic splitting into an index and self-contained topic sections rather than truncating data. Strict format compliance and optional completeness repair passes ensure no information is lost during this division.

Do I need to specify a downstream consumer when extracting a document distillate?

Specifying a downstream consumer is optional but recommended for optimizing the distillate format. The caller may also define a token budget to trigger semantic splitting and an output path to save the compressed results for the target LLM workflow.