Nested snippets

Use {{snippet:abbreviation}} to embed one snippet in another.

Best regards,
{{snippet:zname}}

Typing {{snippet: in the editor opens an autocomplete list. Arrow keys to move, Enter or Tab to pick.

Insert a note

{{note:Master::Project brief}} inserts that note's text, as it is right now.

The point is a context document that cannot go stale. If the brief you paste at the start of every AI conversation is a note you already keep up to date, a snippet that pulls it in is always current, and there is no second copy to remember to edit.

You do not have to type it. Pick Insert a Note from the T menu in the token toolbar, or just type {{note: yourself. Either way the cursor lands inside the braces and a list of your notes opens there, across every vault. Type to narrow it: the search matches anywhere in a note's title rather than only at the start, and it matches folder names and vault names too, so obsidian narrows to one vault and standup finds "Team standup notes". Arrow keys move, Enter or Tab picks, Escape closes.

Picking writes the vault name in front: {{note:Obsidian::Work/Standup}}. That is deliberate. With more than one vault a title on its own is not a unique name, and a token that says which vault it means keeps working whichever vault you happen to have open.

The separator is two colons, so a note called Meeting: Q3 is still addressable. Inside a vault you can name a note by its title, or by its path when two notes share a name. A note without a vault in front of it, like {{note:Standup}}, is looked up in whichever vault is currently open, which is how every note token written before this worked and still does.

A note over about 20,000 characters is cut short with a visible marker rather than silently.

Not available inside script snippets. A note's text is whatever you wrote in it, and putting that into a shell command is not safe even when you wrote both.