How to better use LLM on top of Obsidian

Context

I’ve been using Obsidian for 6 months and my vault has grown to roughly few hundred notes. Topics include work, meetings, discussion etc.

What I’m struggling with

  1. Properties / frontmatter — I add fields (tags, status, type, dates, etc.) but they don’t consistently connect notes or show up in ways that help me navigate the vault. Notes feel like isolated files with metadata pasted on top.

  2. Linking — I know wikilinks matter, but with this volume I’m not sure when to link, what deserves a dedicated note vs a bullet, or how to avoid either zero links or random cross-links that don’t reflect how I think.

What I’ve already tried

  • Mostly folders
  • Tags only / tags + links
  • MOC / index notes
  • Periodic notes / daily notes linking

What I want from the community

Not “use more links” in the abstract — I’d love concrete patterns, for example:

  • A minimal frontmatter schema (3–5 fields) that stays maintainable at scale
  • Linking rules of thumb (hub notes, MOCs, link on create vs link on review)
  • How you use graph filters / groups (or why you ignore the global graph)
  • Whether local graph + backlinks replaced global graph for you
  • Any LLM strategies you might have used

Overall love the product, keen to hear from the community about their experiences and workflows

2 Likes

When you want to quickly reach a certain note from a certain place. (Maybe also when you want to use link suggestions as a cheap autocomplete for names.) Links are easy to add and remove, so if you find a place where you wish you had one (.or didn’t have one), you can change that without much fuss. Whether that helps with LLM use I don’t know, but Google built the best search engine by paying attention to what people linked organically, so it seems worth a try.

I ignore it because it doesn’t seem obviously useful and I’ve never heard a compelling use case for it. I used to open it about once a year to browse around and try to make it pretty, but even that tapered off (I’ll do it again someday, probably). Also its more of a resource hog than than the rest of the app, and heats up my mobile devices. (But it’s OK to like it! Tastes vary.)

The type of a property is global across the vault. So it is enough to select a few properties and assign 1 type to each.

If you are using LLMs, I would keep type, status (active/superseded), date, supersedes and source. This is just my opinion, there is no measurement for that.

The status field is the most important here. An LLM can provide the same level of confidence for an old decision as for a new one, if there is no information that it was superseded.

Also, Bases can use these properties to create views with filters, so they could still be useful for you.

Finally: when you put links in the supersedes field, make it a list and enclose them in quotes, otherwise Obsidian does not understand them as links.