consolidate
Skill0 starsChanged 2 months agoMITView on GitHub
Distill the current session into a Grove context tree. Use when the user explicitly asks to preserve durable memory; route the signal, write owner-voiced leaves, refresh the canopy, reindex, show the staged diff, and commit only after explicit approval.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- vinaySankar2004/vuhritheir own version, first seen Nov 3, 2026
- jantichy/claudetheir own version, first seen Oct 27, 2026
- es6kr/skillstheir own version, first seen Oct 13, 2026
- boaz-hwang/skilloomtheir own version, first seen Oct 8, 2026
- boaz-hwang/distilltheir own version, first seen Oct 8, 2026
- ilanbm/kpoppertheir own version, first seen Sep 23, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- jantichy/claude★ 45same name
- boaz-hwang/distill★ 14same name
- boaz-hwang/skilloom★ 14same name
- ilanbm/kpopper★ 12same name
- es6kr/skills★ 2same name
- spscream/ai-floppy★ 2same name
- vinaySankar2004/vuhri★ 0same name
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.
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 6 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
- Distinctive: line 9
Run this before anything else:
- Very specific: line 15
If either check fails, stop.
- Very specific: line 19
Read references/protocol.md relative to this skill directory and follow it end to end.
- Distinctive: line 21
Treat the request supplied with this skill invocation as an optional subject hint.
“Common” is measured: kept by at least 6 in 10 of the 6 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
Preflight
Run this before anything else:
command -v grove >/dev/null && test -d "${GROVE_ROOT:-$HOME/Grove}"If either check fails, stop. Tell the user that this skill requires the grove CLI and a Grove root (GROVE_ROOT, defaulting to ~/Grove), and that Grove is a separate project. Do not improvise a substitute memory store, and do not write anywhere else.
Protocol
Read references/protocol.md relative to this skill directory and follow it end to end. The bundled file is the canonical protocol for this skill: routing may skip a question but never acceptance; every leaf obeys the signal check and owner-voice rule; canopy refresh is mandatory.
Treat the request supplied with this skill invocation as an optional subject hint. If absent, scope the consolidation in the protocol's first beat.
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.