tldr
Skill0 starsChanged 10 days agoMITView on GitHub
Load this skill before you shorten a reply, a document, a file or a thread that exists. Use it when the user asks for a tldr, a TLDR, a summary or a recap. Use it also for the key points or the short version of a text. Use it also when the user says that a text is too long. Use it also when the user has no time to read a text. Do not use it to explain a command, a concept or code. Do not use it to write the summary section of a document or a PR. The skill keeps each decision, option, necessary change, doubt and limit of the source.
40 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- richkuo/rk-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 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 repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- rules/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- babysit-prSkill
- beast-uiSkill
- cleanupSkill
- councilSkill
- doc-viewSkill
- featuremapSkill
- file-prSkill
- frontend-designSkill
- full-sendSkill
- full-stopSkill
- impeccableSkill
- leaving-pr-commentsSkill
- modernizeSkill
- no-commentsSkill
- patrolSkill
- sol-loopSkill
- statechartSkill
- technical-writingSkill
- untangleSkill
- verify-prSkill
- whySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 14 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 35 edited versions we read keep these.
14
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
Use the text that the user names.
- Distinctive: line 38
Start with the answer. Then give one line for each item, in the order of importance, with each part that the source gives.
- Distinctive: line 44
Write an option and a necessary change in these shapes.
- Distinctive: line 52
When the source has several decisions or options, put the lines in groups.
- Distinctive: line 63
Keep the verb of obligation: "must", "should", "suggests", "can".
- Distinctive: line 65
Keep who says, doubts or does not know each thing, and whom it covers.
- Distinctive: line 68
Keep the scope of each claim: "only on X", "until Y", "if Z".
- Distinctive: line 69
Keep each part of a change.
- Distinctive: line 71
Keep numbers, names, identifiers, code and quotations exactly.
- Distinctive: line 75
Do not add a note, a cause, a conclusion or a computed number of your own.
- Distinctive: line 76
Do not fill a part that the source leaves open.
- Distinctive: line 81
Remove narration, background, praise, repeated text and offers of more work.
- Distinctive: line 82
Remove the method of a test, and how a step or a tool works inside.
- Distinctive: line 84
Remove a check that did not run when its result changes nothing that the reader does.
“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
TLDR
Shorten a text that exists. Keep what the reader needs for a decision or an action. The number of these items sets the length. The length of the source and a word count do not.
Target
Use the text that the user names. If the user names no text, use your last reply. Read the full source before you write.
List the items
List each item of the source that changes what the reader decides or does. For each item, look for these parts in the source:
- The answer or the recommendation, with its strength and its main reason.
- Each decision that waits on the reader, and who decides. For each option, the exact change, what it gives, what it costs or loses, and what it needs.
- Each change that must happen, with each of its parts and values, the date, and the result when it does not happen.
- Each condition or limit of a claim, a plan or an action. Look also in the sentences that name no problem.
- Each doubt or open question, with who holds it, its evidence, and who does not know the answer.
- Each check that did not run, or that ran only in part.
- Each number, name, date or cost that the reader needs.
This list is for you. A part that the source does not give stays out.
Write the result
Start with the answer. Then give one line for each item, in the order of importance, with each part that the source gives. Put a reason or another needed fact in the line of the item that it supports. Each sentence gives an item or a part of your list. Remove a sentence that gives none, and do not remove an item or a part to save words.
Write an option and a necessary change in these shapes. Leave out a part that the source does not give.
- <option>: <the exact change>. Gives: <what>. Costs: <what>. Needs: <what>.
- <change>: <each part, with its values>. By <date>. If it does not happen: <result>.When the source has several decisions or options, put the lines in groups. Give each group a label, such as "Decision", "Must do", "Limits" or "Open". Give each option its own line. For a yes or no decision, give what each answer causes, when the source says it.
Give each fact once. Write whole sentences.
Keep the meaning
- The certainty of the source is a fact, not a hedge. Keep its words, such as "seems", "probably", "slightly" or "not sure".
- Keep the verb of obligation: "must", "should", "suggests", "can". Keep a plain statement plain. "The test fails" is not "the test can fail".
- Keep who says, doubts or does not know each thing, and whom it covers. "I do not know" is not "nobody knows". "One reviewer disagrees" is not "the reviewers disagree".
- Keep the scope of each claim: "only on X", "until Y", "if Z".
- Keep each part of a change. "Set the timeout to 30 s" is a change. "Fix the timeout" is only a name for one.
- Keep numbers, names, identifiers, code and quotations exactly.
Add nothing
Do not add a note, a cause, a conclusion or a computed number of your own. Do not fill a part that the source leaves open. Do not write about your own work, such as what you read or did not change.
Remove the rest
Remove narration, background, praise, repeated text and offers of more work. Remove the method of a test, and how a step or a tool works inside. Remove a detail that only explains an item, such as the line count behind a slow test. Remove a check that did not run when its result changes nothing that the reader does.
Check
Compare the source with the result, paragraph by paragraph. Find each item of your list and each of its parts. Then compare each sentence of the result with the source. It must have the same strength, scope and owner. Restore what is missing or changed, in the words of the source.
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.

