Skill Distiller

The problem

A common failure mode when writing skill files is that they list many features but lack a path from a real pain point to a reusable process. This skill is aimed at situations where the experience is clear but the problem, reasoning, steps, and supporting tools are not. It helps turn fuzzy practice into a workable SKILL.md draft instead of a pile of disconnected actions.

How it works

It works in four moves:
- Problem: define frequency, time cost, failed attempts, and the change if solved, so a wish is not mistaken for a requirement.
- Theory: locate a methodology, classic framework, industry norm, or transferable logic that gives the process a defensible basis.
- Process: turn the idea into steps with inputs, outputs, pass/fail checks, and fallback behavior.
- Tools: choose prompts, scripts, workflows, or checklists for repeated, slow, or template-friendly steps.

Boundaries

It works best as a design scaffold for skills and for structured workflows in operations, content, support, or similar domains. The more specific the input, the more useful the output. It does not invent business judgments without evidence, and it does not replace validation with real data.