notemd-markdownlisted
Install: claude install-skill a-aigner/notemd-skills
# notemd Flavored Markdown
notemd stores each note as a `.md` file in a per-project vault. On disk it uses **Obsidian-compatible** syntax (wikilinks, `> [!type]` callouts, `#tags`, KaTeX), but its renderer supports only a **subset** of Obsidian. Writing an unsupported construct (mermaid, `![[embeds]]`, `%%comments%%`, `==highlight==`) is silent — the file saves, but the note renders the raw text. This skill covers only what notemd actually renders. Standard Markdown (headings, bold, italic, lists, quotes, code, tables) works as normal and is assumed knowledge.
## What notemd supports vs. Obsidian
| Works in notemd | Does NOT render in notemd |
|---|---|
| Wikilinks `[[Name]]`, `[[Folder/Name]]`, `[[Name\|Alias]]` | Embeds `![[Note]]`, `![[image.png]]` |
| Callouts `> [!type]` — 5 types only (see below) | Obsidian callout types outside those 5 |
| `#tags`, frontmatter `tags` | `%%comments%%` |
| KaTeX math `$…$`, `$$…$$` | `==highlight==` |
| Footnotes, task lists, tables, `<details>` toggles | Mermaid diagrams |
## Internal links (wikilinks)
notemd resolves wikilinks by Obsidian's **closest-note / shortest-path** rule and tracks renames automatically (each note carries a durable internal `id`).
```markdown
[[Note Name]] Link to the closest note named "Note Name"
[[Folder/Note Name]] Disambiguate when two notes share a name
[[Note Name|Display Text]] Custom link text
```
- Use `[[Folder/Name]]` **only** to disambiguate — if a name is unique,