distill

Extract formal Allium specifications from existing codebases.

446|24|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/juxt/allium --skill distill-juxt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distill
Source: https://github.com/juxt/allium/tree/main/skills/distill
Command: npx skills add https://github.com/juxt/allium --skill distill-juxt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you reverse-engineer existing codebases to create formal specifications, bridging the gap between implementation and intended behavior.

Core Features & Use Cases

  • Reverse Engineering: Understand complex code by distilling its core logic into a structured specification.
  • Documentation Generation: Automatically create living documentation from your codebase.
  • Use Case: You inherit a legacy Python service with no documentation. Use this Skill to analyze the codebase and generate an Allium specification that captures its essential rules and entities, making it understandable for new developers.

Quick Start

Use the distill skill to extract a specification from the codebase in the current directory.

Frequently Asked Questions about distill

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

FAQPage Schema
How do I reverse engineer an undocumented codebase to extract business logic?

You can reverse engineer an undocumented codebase by analyzing its code structure, identifying domain models, state transitions, and temporal triggers to distill implementation details into formal domain-level rules.

How can I generate living documentation from existing source code?

To generate living documentation from source code, analyze code patterns and external integrations to abstract the implementation into a structured specification that captures essential rules and entities.

What is the best way to extract formal specifications from legacy code?

The best way to extract formal specifications from legacy code is to analyze code structure to identify domain models and business logic, abstracting implementation details into structured domain-level rules.

Can I use distill to understand state transitions and temporal triggers in a codebase?

Yes, you can understand state transitions and temporal triggers by analyzing code patterns within the codebase to abstract implementation details into formal domain-level rules and specifications.

Does extracting specifications from code require any specific input format or environment?

Extracting specifications requires an existing codebase to analyze. The process analyzes code structure, domain models, and external integrations directly from the provided codebase in the current directory.