distill-source-to-skilllisted

# distill-source-to-skill # Distill Source To Skill ## When to use - Source material (docs, repos, notes, transcripts) should become one installable skill package - Mechanisms, decision rules, and failure modes need extraction; not summaries - Not for revising an existing package in place (`author-skill`) ## Overview Use this skill to turn source material into a compact, installable skill package that a future agent can use without rereading the original source. Distill mechanisms, not summaries. ## Resource Guide - Read `references/source-to-skill-patterns.md` for source intake rules, multilingual handling, mechanism cards, package shape decisions, and validation checklists. - Use the target repository's own validator, registry generator, catalog generator, and eval conventions before adding new local scripts. ## First Principle The source is evidence. The skill is the reusable control surface: trigger, decision rules, workflow, output contract, boundaries, and validation. ## Workflow 1. Name the evidence boundary: source paths, links, languages, formats, sections read, sections unavailable, assumptions, sensitivity, intended audience, license, and publication authority. Access to a private source or history is not authority to publish it. 2. Choose the smallest mode: - quick brief: short pasted method or memo; - source audit: multiple files, transcripts, repositories, media, or mixed languages; - package build: user asks for files, repo changes,