Jun 18, 2026, 12:01 PM

brain/.agents/skills/obsidian-cli/SKILL.md

@@ -31,7 +31,7 @@ For multiline content use `\n` for newline and `\t` for tab.
 
 Many commands accept `file` or `path` to target a file. Without either, the active file is used.
 
-- `file=<name>` — resolves like a wikilink (name only, no path or extension needed)
+- `file=<name>` — resolves like a knowledgelink (name only, no path or extension needed)
 - `path=<path>` — exact path from vault root, e.g. `folder/note.md`
 
 ## Vault targeting
@@ -104,3 +104,4 @@ obsidian dev:mobile on
 ```
 
 Run `obsidian help` to see additional developer commands including CDP and debugger controls.
+

brain/.agents/skills/obsidian-markdown/SKILL.md

@@ -1,24 +1,24 @@
 ---
 name: obsidian-markdown
-description: Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
+description: Create and edit Obsidian Flavored Markdown with knowledgelinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions knowledgelinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
 ---
 
 # Obsidian Flavored Markdown Skill
 
-Create and edit valid Obsidian Flavored Markdown. Obsidian extends CommonMark and GFM with wikilinks, embeds, callouts, properties, comments, and other syntax. This skill covers only Obsidian-specific extensions -- standard Markdown (headings, bold, italic, lists, quotes, code blocks, tables) is assumed knowledge.
+Create and edit valid Obsidian Flavored Markdown. Obsidian extends CommonMark and GFM with knowledgelinks, embeds, callouts, properties, comments, and other syntax. This skill covers only Obsidian-specific extensions -- standard Markdown (headings, bold, italic, lists, quotes, code blocks, tables) is assumed knowledge.
 
 ## Workflow: Creating an Obsidian Note
 
 1. **Add frontmatter** with properties (title, tags, aliases) at the top of the file. See [PROPERTIES.md](references/PROPERTIES.md) for all property types.
 2. **Write content** using standard Markdown for structure, plus Obsidian-specific syntax below.
-3. **Link related notes** using wikilinks (`[[Note]]`) for internal vault connections, or standard Markdown links for external URLs.
+3. **Link related notes** using knowledgelinks (`[[Note]]`) for internal vault connections, or standard Markdown links for external URLs.
 4. **Embed content** from other notes, images, or PDFs using the `![[embed]]` syntax. See [EMBEDS.md](references/EMBEDS.md) for all embed types.
 5. **Add callouts** for highlighted information using `> [!type]` syntax. See [CALLOUTS.md](references/CALLOUTS.md) for all callout types.
 6. **Verify** the note renders correctly in Obsidian's reading view.
 
-> When choosing between wikilinks and Markdown links: use `[[wikilinks]]` for notes within the vault (Obsidian tracks renames automatically) and `[text](url)` for external URLs only.
+> When choosing between knowledgelinks and Markdown links: use `[[knowledgelinks]]` for notes within the vault (Obsidian tracks renames automatically) and `[text](url)` for external URLs only.
 
-## Internal Links (Wikilinks)
+## Internal Links (Knowledge Baselinks)
 
 ```markdown
 [[Note Name]]                          Link to note
@@ -44,7 +44,7 @@ For lists and quotes, place the block ID on a separate line after the block:
 
 ## Embeds
 
-Prefix any wikilink with `!` to embed its content inline:
+Prefix any knowledgelink with `!` to embed its content inline:
 
 ```markdown
 ![[Note Name]]                         Embed full note
@@ -194,3 +194,4 @@ Reviewed in [[Meeting Notes 2024-01-10#Decisions]].
 - [Embed files](https://help.obsidian.md/embeds)
 - [Callouts](https://help.obsidian.md/callouts)
 - [Properties](https://help.obsidian.md/properties)
+