Small builds
Page-saving extension
A Chrome extension that saves a web page or a podcast transcript from YouTube as an AI-written note in your second brain.
Why I built itLinks I sent to my own WhatsApp inbox got read once and never found again, so I built a one-click path into my second brain.
- It detects the page type and pulls transcripts from YouTube, which covers the podcasts I follow.
- It writes an AI summary note and files it in a GitHub repo or a Notion database.
- Only the pages I pick get saved, so the second brain holds the significant ones.
--- date: 2026-10-12 source_url: https://example.com/onboarding-checklists source_type: article category: product tags: [onboarding, activation, checklists] --- ## Why onboarding checklists stall ### Summary A checklist helps when each step is a task the user already wants to do. The article reports that one team cut its checklist from seven steps to three and more new users finished it. ### Key insights - Every step the user did not choose is a place to quit. - Order the steps by the value the user sees first. - Measure completion per step to find where users leave. ### Notable quote or data point > "Every step you remove is one fewer place to quit." ### My notes
Sample, invented. The article, the team and the quote are made up. The layout is the one the extension writes.
What you get
A Chrome extension you load unpacked from the repo.
- It saves with one click to one or more GitHub second brains, a Notion database or both.
Builds on: Readability.js by Arc90 and the Mozilla contributors (Apache 2.0), inside the extension. Notices in the repo.
Copy it
Time to set up: 15 to 20 minutes. The extension needs an AI API key.
It loads as an unpacked extension in Chrome.
Get the extension folder
[ -d ~/how-i-work ] || git clone https://github.com/DanielErCohen/how-i-work.git ~/how-i-work- Open
chrome://extensions, turn on Developer mode and choose Load unpacked. - Select
~/how-i-work/small-builds/page-saving-extension. - Create a private GitHub repo for captures (notes land in
00-inbox/) and a fine-grained token limited to that one repo. The extension keeps the token in the browser's extension storage in plain text.
The readme has every step (15 to 20 minutes).