Delegating newsletter-reading to an agent without going brain-dead

For a while now, instead of reading newsletters myself, I've been feeding them to Claude Code running on my personal knowledge base.

The process is simple. I drag the emails from Mail.app into a temp folder, which saves them as .eml files. Claude has a few scripts to parse those files and pull out the content and links, then uses the fetch tool (or the Chrome/Safari MCP when a site blocks it) to read each piece and decide whether it's worth saving to my KB. I wrapped all of that logic into a skill: how to parse the files, how to judge what's worth keeping, which tools to use, how to categorize each item. So it runs the same way every time.

It was a good decision. My KB started growing much faster. But I noticed a side effect: I was going a little brain-dead. If I'm not reading anything myself, I lose touch with the trends and my thinking gets dull.

So I added one instruction to the skill: at the end of every run, present a curated reading list. Claude decides what's actually worth my time and gives me each pick as a title, a one-line reason it matters, and the link.

Now the newsletters do double duty. They grow my KB and hand me a short reading list straight from the source. I stay sharp without going back to reading every newsletter myself.