Reporting back: Tern and the library list
In August I wrote about a small problem: I keep the big list of books I want to read in Epilogue, and then I never actually look at it when I open Libby to check out my next batch of books from the library. I promised I would report back when I built a boring tiny tool to fix it.
It is done, and I’ve put it on GitHub as the first piece of Tern, a set of small tools for my personal Obsidian vault.
Every morning at 5:00 AM, a launchd job runs a Python script that reads my published Epilogue bookshelf and checks every book against the Berkeley Public Library catalog on Libby. It writes two things into my vault: a master availability page with one-click borrow and hold links, and a short section in my daily note that tells me if something on my list just flipped from the waitlist to available so I can swoop in and grab it. On its first run it found 18 books on my list that were sitting on the digital shelf waiting for me.
I used Gemini to help me build it and package it as a skill, but once it is set up it doesn’t require AI to run. It is just a scheduled Python script, public library data, and plain Markdown files that I own. If you use Epilogue, Libby, and Obsidian, I included instructions in the repo so you can point it at your own bookshelf and your own public library.