agentleFS
DeepExtremaDeepExtrema/Tesseract/skills/distill/SKILL.md

distill

Skill4 starsChanged 14 days agoMITView on GitHub

Use when Taimoor asks to consolidate the vault's raw memory — "distill the inbox", "promote captures to concepts", "consolidate what we learned about X" — or when the Inbox has piled up. Promotes repeated capture/session material into evergreen Claude/Concepts/ notes with cited sources.

77 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use layout, shape and 9 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-mecSkill

    layout

    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-7663Skill

    shape

    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

  • ReScienceLabSkill

    archive

    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

  • klauswgSkill

    ckm: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

  • iovisorSkill

    evolve

    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

  • bidodevSkill

    devils-advocate

    Challenges decisions, plans, and code by systematically arguing the opposing side. Surfaces risks, pokes holes in assumptions, and stress-tests thinking before committing. Supports intensity levels (gentle, balanced, ruthless, linus) and works with conversation context or a specific file reference. Trigger on requests like "challenge this", "poke holes", "what could go wrong", "play devil's advocate", "linus mode", or "/devils-advocate".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 73 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a nearby concept exists, EXTEND it — never create a near-duplicate with a different name.

    line 25
  2. Distinctive:

    Only claims that will still hold beyond the week they were written.

    line 30
  3. Very specific:

    Every claim cites its source note as a [[wikilink]].

    line 31
  4. Very specific:

    Delete nothing and move nothing — captures stay where they are.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 73 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Distill — promote memory into knowledge

Requires the tesseract MCP server. Turns layer-1 memory (captures, session logs) into layer-2 knowledge (concepts). Salience-gated: most raw material should NOT be promoted.

Steps

  1. Gather candidates:
    • With a topic argument: search_brain(topic, limit=10) plus query_notes(folder="Claude/Inbox").
    • Without: query_notes(folder="Claude/Inbox") plus the last ~14 days of Claude/Sessions/ notes (list_recent, filter by folder).
  2. Cluster the material into candidate concepts. The salience gate: a candidate qualifies ONLY if its idea appears in 2+ independent notes, or Taimoor named the topic explicitly. Everything else stays in the Inbox — premature promotion bloats Concepts and dilutes retrieval.
  3. For each qualifying candidate, search before writing: find_entity(name) and query_notes(folder="Claude/Concepts"). If a nearby concept exists, EXTEND it — never create a near-duplicate with a different name.
  4. read_note every source note in full — excerpts locate, they are not enough to distill from.
  5. upsert_concept(name, content). Content rules:
    • Only claims that will still hold beyond the week they were written.
    • Every claim cites its source note as a [[wikilink]].
    • Contradictions between sources are stated side by side with their dates, never silently resolved — the newer claim is flagged as newer, not declared the winner.
  6. Report in chat: what was promoted into which concept, and what was left in the Inbox and why (the gate's verdict, one line each).
  7. Delete nothing and move nothing — captures stay where they are. The organizer never touches Claude/, so the Inbox changes only when Taimoor prunes it.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.