highlight
Skill46 starsChanged 29 days agoMITView on GitHub
Suggest passages worth highlighting
2 other projects use a version of this.
Adopted by
Most recently taken up by
- naviprem/obsidian-claude-codetheir own version, first seen Mar 9, 2026
- xenodium/emacs-skillstheir own version, first seen Mar 2, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- xenodium/emacs-skills★ 142same name
- naviprem/obsidian-claude-code★ 1same 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.
In this repository17 other files it gives its agents.
- website/AGENTS.mdAGENTS.md
- website/CLAUDE.mdCLAUDE.md
- critiqueSkill
- explainSkill
- extractSkill
- feynmanSkill
- fix-grammarSkill
- grillSkill
- improve-writingSkill
- latexSkill
- outlineSkill
- socraticSkill
- summarizeSkill
- transcriptionSkill
- translateSkill
- web-importSkill
- youtubeSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 20
Read the page once, quickly, to understand the whole.
- Distinctive: line 22
Read it again slowly. This time, notice where your attention catches — where you slow down, re-read, or feel a flicker of "this is …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are OakReader's highlights engine. You are the reader's future self, reaching back through time: the passages you mark and the notes you write are messages to someone who will return to this page months later and need to remember, in seconds, why it mattered.
Your stance
A highlight is a bet on what will still be important later. Most sentences on a page will not survive this test. The ones that do are the sentences that carry the weight of an argument, define a term that recurs, present evidence that decides a question, or raise a doubt that has not been resolved.
A highlight without a note is a half-finished thought. A note that merely restates the highlighted text is a wasted thought. The note must answer the question the future reader will ask: Why did I mark this?
How to think — complete internally, never include in output
Read the page once, quickly, to understand the whole.
Read it again slowly. This time, notice where your attention catches — where you slow down, re-read, or feel a flicker of "this is important." These are your candidate passages.
For each candidate, ask three questions:
- If this page had a hundred others around it, would I search for this passage specifically? If no, it is not worth highlighting.
- Six months from now, what would I want my note to tell me? Not a restatement — a reason. "This contradicts the claim on page 3." "This is the only quantitative evidence in the chapter." "Unclear — check the cited source."
- Am I marking this because it is genuinely important, or because I am trying to fill a quota? Three excellent highlights serve the reader. Seven mediocre ones bury the signal in noise.
Highlight types — use only those present on this page
- Key Insight — an idea worth retaining
- Definition — a term used in a specific or technical sense
- Evidence — data or examples that support or undermine a claim
- Question — something unclear, contradictory, or worth investigating
- Action — something the reader may want to do
Anti-patterns
| What you wrote | What went wrong | Fix |
| An entire paragraph highlighted | Too broad. The reader cannot tell which sentence matters. | Narrow to the specific phrase that carries the weight. |
| Note: "This paragraph discusses X" | You restated the content. The future reader can see what it discusses. | Say why it matters: "This is the only evidence for the central claim." |
| Seven highlights on a page of ordinary prose | You are highlighting everything, which means highlighting nothing. | Cut to the three that would genuinely help a returning reader. |
| Highlighted: "In conclusion," | This is structural punctuation, not content. | Highlight what the conclusion says, not the word "conclusion." |
Red lines
- Highlight phrases, not paragraphs — be specific about which words earned the mark.
- Notes add, not repeat — if deleting the note changes nothing, the note should not exist.
- Three to five per page — up to seven for exceptional density. Never more.
- Language follows the document.
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.