tldr
Skill1 starsChanged 7 months agoMITView on GitHub
Use when the user explicitly invokes /tldr to summarize the current conversation into a session note saved to a configured directory. For ambient surfacing of past sessions, use the session-recall skill instead.
39 other projects use a version of this.
Adopted by
Most recently taken up by
- richkuo/rk-skillstheir own version, first seen Nov 14, 2026
- annatomka/skillstheir own version, first seen Nov 8, 2026
- zazencodes/skillstheir own version, first seen Nov 8, 2026
- MarkPhamm/claude-skillstheir own version, first seen Nov 8, 2026
- nirberko/skillstheir own version, first seen Nov 8, 2026
- LaansDole/my-hermes-skillstheir own version, first seen Nov 7, 2026
Used with
Projects with it also use explain, handoff and 2 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.
sunnyclinches44Skillexplain
Explains code using real-world analogies and ASCII diagrams
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 6 projects that use this
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
Other versions39 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 39
- earlyaidopters/second-brain★ 193same name
- saksham10arora-dotcom/everything-claude-codex★ 96same name
- richkuo/rk-skills★ 50same name
- gsarig/skills★ 30same name
- peterpme/skills★ 28same name
- Vesely/skills★ 28same name
- nirberko/skills★ 19same name
- r13i/skills★ 17same name
- zazencodes/skills★ 15same name
- SurefireStudios/tldr★ 9same name
29 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 repositoryOne other file it gives its agents.
- session-recallSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 34 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Read the full conversation.
- Very specific: line 78
If multiple /tldr calls land on the same day, the slug differentiates them.
- Distinctive: line 89
Keep reverse chronological (newest first).
- Distinctive: line 96
If the conversation is clearly:
“Common” is measured: kept by at least 6 in 10 of the 34 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
TLDR — Session Note Saver
Summarize the current conversation as a session note and save it to disk.
Argument ($ARGUMENTS): optional freeform annotation that focuses the summary (e.g. "important — financial strategy change", "for partner's birthday").
Setup
Configure these paths in your project's CLAUDE.md (or set them inline in conversation):
- Sessions directory — where session notes live (default:
sessions/at the project root) - Index file — one row per saved session (default:
<sessions-dir>/INDEX.md) - Tags file — canonical tag registry, optional (default:
<sessions-dir>/TAGS.md)
Companion: the session-recall skill reads from the same directory + index. Pair them.
What to Capture
Read the full conversation. Identify:
- Title — short, descriptive, opinionated. "RAV4 PHEV — Trim Analysis and Purchase Plan", not "Car Discussion". Lead with the conclusion or the topic's real name.
- Summary — 2–3 sentences capturing the conclusion, not the process. "X turned out to be Y because Z" not "We discussed X."
- Tags — freeform but consistent. Check
<tags-file>before inventing new tags. Multiple tags expected — think "who would want to find this later?" - Sections — only include sections that are relevant:
## Key Decisions— if choices were made## Findings— if research produced conclusions## Recommendations— if products / tools / media were evaluated (name, price, where to get). This is the #1 thing the user tries to recall from past conversations.## Open Threads— anything left unfinished that a future session should know about
- Source — if the conversation was triggered by a URL (article, video, post), capture it in frontmatter.
Format
---
date: YYYY-MM-DD
tags: [tag1, tag2, tag3]
source: "https://..." # only if the conversation had a trigger URL
---
# Title
2–3 sentence summary.
## Key Decisions
- ...
## Findings
- ...
## Recommendations
- Product — $price at [vendor](url)
## Open Threads
- ...File Naming
<sessions-dir>/YYYY-MM-DD-slug.md
Slug: lowercase, hyphenated, 3–5 words max. Derived from the title.
Examples: 2026-03-12-rav4-purchase-research.md, 2026-03-28-postgres-tuning-checklist.md
If multiple /tldr calls land on the same day, the slug differentiates them.
After Writing
- Update the tags file — add any new tags to
<tags-file>, alphabetical. - Update the index file — add one line to
<index-file>:
Keep reverse chronological (newest first).YYYY-MM-DD | [Title](YYYY-MM-DD-slug) | tag1, tag2, tag3 - Confirm — show the user the title, tags, and file path. Don't dump the full content back at them.
When NOT to /tldr
If the conversation is clearly:
- A one-shot lookup ("what is prime reading")
- An automated workflow whose artifacts already exist elsewhere
…flag it and ask if they still want a session note. Don't refuse — just check.
Companion Skill
The session-recall skill handles ambient surfacing of saved session notes during normal conversation. This skill writes new ones; that one reads them. Both touch the same index file.
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.

