distill
Skill0 starsChanged 4 months agoMITView on GitHub
Crystallize the just-completed multi-step task into a new reusable Agent Skill under .claude/skills/. Use when the user runs /distill or asks to "turn this into a skill / make this repeatable" after finishing a workflow worth reusing.
76 other projects use a version of this.
Adopted by
Most recently taken up by
- persiyanov/skillstheir own version, first seen Nov 15, 2026
- komluk/scaffoldingtheir own version, first seen Nov 15, 2026
- Integralist/agent-skillstheir own version, first seen Nov 14, 2026
- theexperiencecompany/gaiatheir own version, first seen Nov 13, 2026
- venhdev/skillstheir own version, first seen Nov 8, 2026
- kylehughes/distillation-for-agentstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use layout, shape and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
owshq-mecSkilllayout
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 8 projects that use this
HAR5HA-7663Skillshape
Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.
Also in 11 projects that use this
ReScienceLabSkillarchive
Archive session learnings, debugging solutions, and deployment logs to .archive/yyyy-mm-dd/ as indexed markdown with searchable tags. Use when completing a significant task, resolving a tricky bug, deploying, or when the user says \"archive this\". Maintains .archive/MEMORY.md index for cross-session knowledge reuse.
Also in 3 projects that use this
klauswgSkillckm:design-system
Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.
Also in 3 projects that use this
iovisorSkillevolve
Evolve uBPF through a gated spec-first workflow that propagates approved changes through requirements, design, validation, implementation, and RFC alignment artifacts.
Also in 3 projects that use this
termdockSkillrecall
Retrieves cross-session memories about past decisions, lessons, and patterns. Use when user asks about prior work, past decisions, or mentions a feature. Triggers include check memory, what did we decide, how did we solve.
Also in 5 projects that use this
Other versions76 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 76
- talesofai/cohub★ 585same name
- juxt/allium★ 506same name
- educlopez/ui-craft★ 441same name
- Michaelliv/napkin★ 428same name
- nexmoe/DayBee★ 424same name
- nexmoe/eve★ 424same name
- Southclaws/storyden★ 348same name
- 10xChengTu/Mux0★ 337same name
- theexperiencecompany/gaia★ 327same name
- AkaraChen/aghub★ 271same name
66 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/00-defer-to-agents-md.mdcCursor rule
- bootstrap-stackSkill
- extract-versionSkill
- learnSkill
- reflectSkill
- seed-updateSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 72 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Follow the Anthropic skill-creator pattern:
- Very specific: line 22
add user-invocable: true if it's also useful as a /command.
- Very specific: line 23
Body: write the procedure as numbered, concrete steps — the exact commands, file patterns, gotchas, and a short example.
- Very specific: line 26
If the skill needs a helper script, add it under .claude/skills/$ARGUMENTS/ and reference it with a path relative to the skill directory …
- Very specific: line 32
If this repo is a git repo, commit: feat(skill): add $ARGUMENTS skill.
“Common” is measured: kept by at least 6 in 10 of the 72 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Turn what we just did into a reusable skill named $ARGUMENTS (kebab-case; if missing, propose one).
Follow the Anthropic skill-creator pattern:
- Scope it: in one sentence, what repeatable workflow does this skill capture? If the work wasn't actually repeatable/reusable, say so and stop (don't create noise).
- Create
.claude/skills/$ARGUMENTS/SKILL.mdwith YAML frontmatter:name: $ARGUMENTSdescription:a precise, trigger-friendly summary starting with what it does and the concrete situations it should activate in (this is what the model matches on — be specific).- add
user-invocable: trueif it's also useful as a/command.
- Body: write the procedure as numbered, concrete steps — the exact commands, file
patterns, gotchas, and a short example. Keep it under ~150 lines; put bulk reference in a
sibling file (e.g.
reference.md) and link it (progressive disclosure). - If the skill needs a helper script, add it under
.claude/skills/$ARGUMENTS/and reference it with a path relative to the skill directory (e.g../helper.py). Do not use${CLAUDE_PLUGIN_ROOT}here — that variable is only defined when a skill ships inside an installed plugin, not for a project-scope skill living in this repo. - Validate: re-read the frontmatter — does the description clearly say when to use it? Tighten if vague.
- If this repo is a git repo, commit:
feat(skill): add $ARGUMENTS skill. - Tell the user the skill is available and how it will trigger.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

