legion-distill

Validates each block of durable prose for clarity, self-containment, and consistency before storage.

3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/runlegion/legion --skill legion-distill-runlegion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legion-distill
Source: https://github.com/runlegion/legion/tree/main/plugin/skills/legion-distill
Command: npx skills add https://github.com/runlegion/legion --skill legion-distill-runlegion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writers cannot reliably judge the clarity of their own prose, so specs, plans, intents, and checkpoints often reach the next reader with gaps, contradictions, or bare pointers that force the reader to stall or invent missing context. ## Core Features & Use Cases - Per-block quality gate: Runs four checks on every block as it is written -- one job per block, every word carrying, self-contained text instead of bare pointers, and consistency with prior blocks. - HALT-on-failure discipline: A block that fails any check stops the work; the gap is emitted rather than smoothed over with fluent prose, at input review, during drafting, and before storage. - Cold reader backstop: A separate reader reviews the artifact block by block from the text alone, catching what the writer cannot grade in its own work. - Use Case: Before storing an implementation plan another agent will build from, run the gate on each section; if a step says "retry per the operator's ruling" without the actual rule, HALT and fix it to carry the substance inline. ## Quick Start Ask the agent to run the distill gate on each block of the spec or plan you are drafting and halt on any block that fails a check.

Frequently Asked Questions about legion-distill

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

FAQPage Schema
How do I check whether a spec or plan is clear enough to hand off?

Run the four per-block checks on each block as you write it: one job per block, every word carrying, self-contained text instead of bare pointers, and consistency with blocks above it. Any failing block is a stop that must be fixed before continuing.

What is the cold reader check for written artifacts?

The cold reader is a separate reviewer, not the writer, who reads the artifact block by block from the text alone without fetching anything. If the reader cannot act on a block, that block goes back to the writer as a stop.

Does this gate apply to status updates and team posts?

No. It governs durable artifacts a stranger builds or acts from, such as specs, plans, intents, and checkpoints. Ephemeral posts, statuses, and signal notes should stay small, carrying a terse pointer or going as a directed signal to one agent.

What happens when a block fails one of the checks?

A failed block is a stop: you HALT, emit the gap, and do not proceed. You must not write the next block over a broken one or smooth the gap into fluent prose, whether the failure is in your input, your draft, or a pre-storage review.

Does the distill gate judge whether content is correct or true?

No. It only catches two failures: a block a later reader cannot follow from the artifact alone, and a claim with no source or a source that must be fetched to act. Judging truth or quality belongs to review and verify steps.