Set Up a Personal Knowledge Base
Use a tool like Obsidian to store your personal notes as local Markdown files in a single, accessible folder.
Run a daily Gardener over an Obsidian or Markdown knowledge base. It cleans up notes, researches unfamiliar people and companies, adds headings, and connects related ideas while preserving the substance of what you wrote.
Download the skill for this workflow. Version 1.0.1.


with Claire Vo
John describes his open-source Gardener, which visits a Markdown knowledge base each day to clean, enrich, cluster, and cross-link notes.
A cleaner, connected knowledge base with useful headings, entity context, and links between related notes.
AI pair programmer
Follow the sequence once, then adapt the prompts, checks, and handoffs to your own setup.
6 steps
Use a tool like Obsidian to store your personal notes as local Markdown files in a single, accessible folder.
Use John's Gardener project or ask a coding agent to create a local script that reads and edits Markdown. Start with a small test folder and keep every change visible in Git or another version history.
Build a local Gardener for this Markdown folder. On each run: 1. Fix obvious spelling and grammar without changing my meaning or voice. 2. Add useful headings when a note has clear sections. 3. Link related notes only when the relationship is specific. 4. For an unrecognized person or company, add a short sourced context note only when identity is unambiguous. 5. Never delete original text. 6. Produce a summary of changed files, new links, and anything left unresolved. Test it on [test folder] before running it across the full vault.
Set up a scheduler, like a cron job, to automatically run the script on your notes folder once every day.
Keep automatic cleanup narrow: spelling, grammar, formatting, and obvious heading structure. Preserve informal phrasing and the author's original claims.
When a note mentions a clearly identifiable person or company, add a brief context block with source links. Skip names that cannot be matched confidently.
You are a research assistant. I will provide you with the name of a person or company mentioned in my personal notes. Your task is to provide a concise, one-paragraph summary of who they are or what they do. Include a link to their official website or a primary source like a Wikipedia page if available. Entity: [entity name]
Add headings and links that make the vault easier to browse. Reuse existing pages and aliases, and report possible connections instead of forcing weak links.
Analyze the following note and improve its structure. Add logical headings using Markdown (##). Identify the main concepts and suggest 3-5 other note titles from my knowledge base that should be linked here. Note content: [paste note text] Existing note titles: [list of other note titles]
Turn an idea into a PRD, user stories, and a plan.
How to recover when the loop fails and where human judgment helps.

Create a repository-based system to provide an AI assistant with durable context about your team, projects, and communication channels. This enables it to perform routine tasks like summarizing daily updates and identifying stakeholders, acting as a personalized chief of staff.

Use Meta's Muse to generate a printable, multi-page family newspaper that includes a weekly schedule, weather forecasts, and activity ideas. This workflow leverages Muse's strength in creating visually appealing, family-oriented artifacts.

Coordinate agents in Slack and Cursor to propose growth experiments for human review. Ezra’s Auto XP system was still being developed at the time of the episode.
Join 250,000+ product managers who use ChatPRD to write better docs, align teams faster, and build products users love.