Flick through an article too fast and Skim Recap hands the skipped passage back in a card beside your cursor. If a term stops you, select the word or phrase and press Feynman: Gemma uses the surrounding paragraph, nearby context, heading, and page title to explain what it means here. Everything runs locally through LiteRT-LM and WebGPU—no account or hosted LLM API.
Skim Recap Reviews
The community submitted 1 review to tell us what they like about Skim Recap, what Skim Recap can do better, and more.
4.0
Based on 1 review
Review Skim Recap?
EneyProactive AI for Mac. Free test, 20,000 credits.
Promoted
Reviews
Most Informative
Glarity - Summarize Google and YouTube
Thanks @galdayan! And thanks for the specific complaint — that's the part I can actually use.
On Feynman getting that framework name right: that one's allowed to go past the passage. The recap isn't. It only says what the text said, because making things up about something you scrolled past is just lying to you. But that's exactly why a recap is useless when the thing you didn't get is a word the page never explained. So Feynman drops that rule. The tradeoff is it's the one output that can be confidently wrong, which is why it never runs on its own - you have to ask for it.
Now the false trigger. You found something real, but it's narrower than it looks. 😀
It does already remember what it recapped. Covered paragraphs get stored as text, not pixel positions (those move around once images load), so flicking over the same stretch again finds nothing new and it stays quiet.
What it doesn't know is what you read. Reading leaves no trace, so a section you went through carefully looks exactly like one it's never seen.
Also — dismissing already works, it's just not obvious: click anywhere off the card, or scroll back up a little and it goes away. If you didn't find that, that's on me, not on you.
Ive written your suggestion down. I'm collecting these right now rather than building each one as it comes in, because a few of them point at the same underlying thing and I'd rather fix that once than patch it three times.
In the meantime the Flick threshold slider in the popup is the blunt version: 1,200px by default, turn it up and it fires less.