do-distill-to-skill

Distills articles, repos, and documents into structured agent skill files.

2|Updated May 25, 2026
One-click install
npx skills add https://github.com/edheltzel/Do-Skills --skill do-distill-to-skill-edheltzel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-distill-to-skill
Source: https://github.com/edheltzel/Do-Skills/tree/main/skills/harness/do-distill-to-skill
Command: npx skills add https://github.com/edheltzel/Do-Skills --skill do-distill-to-skill-edheltzel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning long-form knowledge sources like blog posts, GitHub repos, papers, and video transcripts into reusable agent skills is hard: raw summarization produces bloated, motivational content that agents cannot act on. This Skill provides a disciplined distillation process that extracts only transferable, decision-relevant knowledge. ## Core Features & Use Cases - Source Absorption and Extraction: Reads full sources (articles, repos, docs, papers, transcripts) and separates actionable rules, patterns, and anti-patterns from motivation, history, and persuasion. - Skill Shape Decisions: Guides whether a source becomes a single SKILL.md, a SKILL.md with references/, or multiple cross-referencing skills, using an explicit decision heuristic. - Ecosystem Translation: Rewrites code examples and idioms into the user's target language (e.g., TypeScript/Bun) so output is copy-pasteable. - Use Case: You find a 5,000-word blog post on type-driven design. Use this Skill to distill it into a ~200-line skill with practical rules, TypeScript examples, anti-patterns, and a code review checklist. ## Quick Start Distill this article into a reusable agent skill with concrete rules and TypeScript examples.

Frequently Asked Questions about do-distill-to-skill

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

FAQPage Schema
How do I turn a blog post into an agent skill?▼

Read the full article, extract the actionable rules and patterns while cutting motivation and history, then structure the result as rules, examples, anti-patterns, and a checklist in a SKILL.md file. Aim for a 7:1 to 20:1 compression ratio over the source.

How do I distill a GitHub repo into a reusable skill?▼

Explore the repo's architecture, entry points, and core implementation files, ignoring tests, CI, and build config. Extract design patterns, copy-paste utilities, and type tricks, then translate them into the user's language ecosystem.

When should a skill use reference files instead of a single SKILL.md?▼

Use references when the source covers multiple distinct sub-topics an agent might need independently. Keep principles and quick reference in SKILL.md under ~300 lines, and move deep dives into self-contained reference files.

What is the difference between distilling and summarizing content?▼

Summarizing preserves the source's structure and explanatory prose, while distilling keeps only decision-relevant rules, patterns, and anti-patterns an agent can act on. If the output approaches the source's length, it is a summary, not a distillation.

How does this skill relate to the skill-creator skill?▼

This skill handles the distillation process: extracting, filtering, and restructuring knowledge from sources. The skill-creator skill handles the mechanics such as directory structure, frontmatter format, validation, and packaging.