Review filings from saved notes with Claude Code
A non-engineer used Claude Code to pull equity research from saved filings and notes, then checked the numbers with a second pass.
- What they did
- They kept their market research in a single local Obsidian vault made of plain-text files, with EDGAR filings saved alongside their notes. A top-level CLAUDE.md file described how the material was arranged and set the ground rules for Claude Code. The agent stayed inside those files, pulled out cited figures with source lines and accession numbers, ran another verification pass, and used small Python programs or Excel sheets for any calculations while the person reviewed the output and corrected mistakes.
- How it went
- Using that setup, they noticed a pattern in Accenture’s last five earnings releases that was hard to spot when each report was read alone: a bookings measure climbed from $3B to $5.9B, then vanished from later releases. They said the extra check helps catch mistakes, but the first read still isn’t clean and the model may fill gaps from memory unless it is tightly constrained.
- Tips
- Make the agent prove every calculation from quoted source text before it does any math. For long filings, require page-level quotes so you can trace each claim back to the original document.
Try it yourself with Claude Code
You are helping me do equity research from files I already keep locally. Start by reading [path to my notes] and the instructions in [CLAUDE.md path], then examine the sources I add for [company or ticker]. Summarize the business, recent performance, key risks, and unresolved questions in a new note, and connect it to related notes if that fits my folder structure. For every important fact or number, include the exact quoted source line and the filing accession number or document identifier. If you need to calculate something, first write a small script or spreadsheet that uses only quoted inputs from the source files, then show me the result. Before you make any change that would replace, remove, send, submit, or lock in content, stop and ask for my approval with the exact action spelled out. Save the finished note as [output file name] and leave my existing files untouched unless I approve edits.
Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.
Get 3 agent uses like this every morning
With the day's top AI news. Free, and one click to unsubscribe.
Related agent uses
Use Claude Code to assemble a research workflow
Kevin Yang used Claude Code to draft, code, and test most of a paper’s analysis while he checked each stage himself.
Convert YouTube videos into linked research notes
Claude Code can gather YouTube videos into NotebookLM, then export cited notes, a graph, audio, and flashcards into Obsidian.
Have a coding agent check papers before each experiment
A Claude Code agent with paper search found useful ideas that a plain run missed while tuning a small language model.
Search an Obsidian vault for old research files
A developer set up Claude Code to find and sort research material inside an Obsidian vault on macOS.
Turn new arXiv papers into nightly notes
A daily digest and nightly Claude Code summaries helped one person keep a small, organized notes folder for selected papers.
Turn transcripts and PDFs into themes and evidence tables
Use Claude Code to summarize interviews, build evidence tables, and draft an annotated bibliography from a study folder.