tldr
Skill1 starsChanged 6 months agoMITView on GitHub
Shrink Claude's previous answer (or every finding so far in the session) into a one-sentence verdict plus up to three short findings. Use only when the user types /tldr or asks for "the short version", "one-sentence verdict", "summarize what you found".
40 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- richkuo/rk-skillstheir own version, first seen Nov 8, 2026
- LaansDole/my-hermes-skillstheir own version, first seen Nov 7, 2026
- beCyborg/jadlis-tldrtheir own version, first seen Nov 6, 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 versions40 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 40
- earlyaidopters/second-brain★ 193same name
- saksham10arora-dotcom/everything-claude-codex★ 74same 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
- SurefireStudios/tldr★ 9same name
- jamesblackwell/falcondeck★ 7same name
30 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 repository6 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 35 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
No argument: your previous answer in this conversation.
- Distinctive: line 44
If the answer corrected an earlier claim, the summary uses the corrected version.
- Distinctive: line 45
Keep a caveat only if it changes the decision.
- Distinctive: line 47
Never use the em dash character.
- Distinctive: line 48
No headers other than the ones in the shape above.
“Common” is measured: kept by at least 6 in 10 of the 35 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
TL;DR
Turn a long answer into something that can be read in ten seconds.
What to summarize
- No argument: your previous answer in this conversation.
all: every finding and conclusion so far in this session, with later corrections replacing the earlier claims they correct.
Output
Exactly this shape, nothing before or after it:
**Verdict:** <one sentence that answers the user's question: yes / no / partly, and why>
- <finding 1>
- <finding 2>
- <finding 3>
**Next:** <the one thing to do, or "nothing">- The verdict is one sentence, at most about 25 words. Lead with the answer ("No, ...", "Yes, ...", "Partly: ...").
- At most three findings, one line each, at most about 20 words each. Pick the ones that change what the user does. Fewer is fine.
- A finding may end with one pointer (a file:line, test name or link) only when it is the main evidence.
- "Next" is one action at most. Write "nothing" when there is no action.
Rules
- Summarize only what was already said. Add no new claims, checks or opinions. If something looks wrong while summarizing, say so in one extra line after "Next" instead of silently fixing it.
- If the answer corrected an earlier claim, the summary uses the corrected version.
- Keep a caveat only if it changes the decision. Drop the rest.
- Plain words. No jargon unless it is the name of the thing.
- Never use the em dash character. Use straight quotes only.
- No headers other than the ones in the shape above. No tables.
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.

