Markdown Obsidian Linker
This skill enforces clean markdown headers to ensure compatibility with Obsidian internal linking and other markdown parsers.
Instructions
When writing or auditing markdown content:
Scan directories recursively: When a directory path is provided, use the
globtool with the pattern**/*.mdto locate all markdown files within the target folder and its subdirectories.Keep headers clean: Do not include links or markdown formatting inside the header itself.
- Bad:
### [Header](url) - Good:
### Header
- Bad:
Place links in content: Put external links in the body text immediately following the header.
Reason: Links inside headers break the anchor generation for internal linking in Obsidian (e.g.,
[[#Header]]) and many markdown parsers.
Examples
Correct Pattern
### My Tool
[My Tool](http://url) - Description of the tool...
Incorrect Pattern
### [My Tool](http://url)
Quick Fix
If you encounter a header with a link, refactor it immediately. When processing a folder, apply this to every .md file found:
Target Folder: fix-links ./docs
File Search (using glob): glob(pattern="**/*.md", path="./docs")
Before:
## [Project X](https://github.com/org/project-x)
After:
## Project X
[Project X](https://github.com/org/project-x)
Converted and distributed by TomeVault — claim your Tome and manage your conversions.