- Home
- Skills
- Jykim
- Claude Obsidian Skills
- Obsidian Links
obsidian-links_skill
- Python
24
GitHub Stars
1
Bundled Files
3 weeks ago
Catalog Refreshed
2 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill jykim/claude-obsidian-skills --skill obsidian-links- SKILL.md6.0 KB
Overview
This skill formats, validates, and repairs Obsidian-style wiki links to match vault filename, folder, and header conventions. It ensures links point to existing files or headers before creation and fixes broken links when discovered. Use it to keep cross-references accurate, consistent, and traceable across your vault.
How this skill works
The skill inspects markdown files for wiki links, resolves folder prefixes and full filenames (including date prefixes), and searches the vault using glob/grep patterns to verify targets exist. For section links it reads the target file and matches header text character-for-character; for YAML properties it enforces quoted link entries. When a link is broken it searches for the correct target and offers or applies a corrected link and reports the change.
When to use it
- Creating new links to other notes in the vault
- Adding section links to specific headers within a note
- Formatting links in YAML frontmatter or list properties
- Validating links before committing changes
- Finding and fixing broken or guessed links
- Ensuring links point to original source files rather than topic indices
Best practices
- Always use the complete filename including date prefix when applicable (e.g., [[2025-10-31 Project Notes]]).
- Include folder path prefixes for clarity and consistency (e.g., [[Journal/2025-10-31]]).
- Verify the target file exists before creating a link using glob or direct file read. Never guess filenames.
- For section links copy header text exactly, character-for-character; if unsure, link to the file only.
- Wrap wiki links in quotes when used inside YAML lists or properties.
- When repairing links, search the vault for likely targets, update the link, verify the header, and report the original and corrected link.
Example use cases
- Linking a daily journal entry from a project note using [[Journal/2025-10-31#PKM System Maintenance]].
- Adding sources in YAML frontmatter as quoted links like sources: - "[[Journal/2025-10-31]]".
- Batch-validating a document set to detect and fix broken topic or person links.
- Converting guessed or slug-style section links to exact header text to avoid navigation errors.
- Searching for a missing article by keyword and updating broken references to the discovered file.
FAQ
Search the target file for the updated header. If it exists, update links to match the exact new header text. If unsure, replace section links with a file-only link and notify the author of the header change.
Can I link to topic indexes instead of original pages?
No. Always prefer linking to the original source file to preserve attribution and traceability. Search the Topics directory first, but link directly to the source page when available.