Practical guide
How to summarize a Substack reading list
Summarize only publicly readable or legitimately received issue bodies, preserve the publication's voice and byline, and state clearly when a post was read but left out or could not be read in full.[1][2]
Why this gets difficult
A Substack reading list often mixes deeply personal writing, reported analysis, quick notes, audio, and paywalled posts. A generic summarizer can flatten those differences and overstate what it was able to read.[1][2]
A practical way through
- Use the publication's public feed where it exposes the issue, or receive subscribed issues through a separate newsletter address.[1][2]
- Record the exact publication and issue URLs before any summary is written.[1][2]
- Compare related publications only when they serve the same reading goal; category labels are not enough.[1][2]
- Keep the author's distinct argument and original link even when shared background is merged with another issue.[1][2]
An example
The situation: Three Substacks cover an economic release: one reports the data, one argues for a policy response, and one sends only a paywalled teaser.[1][2]
What changes: The readable issues are read together, the policy argument stays distinct, and the inaccessible teaser is not reconstructed from its headline.[1][2]
What you get: The brief remains useful without fabricating access or turning three authors into one anonymous voice.[1][2]
What to watch for
Sources worth keeping
How Scottie helps
Scottie can read public feeds or issues forwarded to a private @scottie.fyi address, then include selected material in a linked brief without accessing the subscriber's personal inbox.[3]