obsidian-wsl-vault-access

Work with an Obsidian vault stored on Windows and accessed from WSL. Read, search, create, and edit markdown notes directly through mounted paths such as /mn...

Security Scan

Instructions, requirements, and behavior are consistent with the stated purpose: an instruction-only skill for reading and editing an Obsidian vault on Windows from WSL, and it does not request extra credentials or install code.

Purpose & Capability

Name, description, and runtime instructions align: the skill explains how to locate and operate on a vault via /mnt/<drive> paths and suggests common file operations. It does not request unrelated credentials, binaries, or installs.

Instruction Scope

SKILL.md confines actions to filesystem operations on the identified vault and recommends confirming the vault root before broad changes. Minor concern: the instructions rely on correct path identification and user/agent discipline — if the agent is given an incorrect path it could read or modify arbitrary files on the mounted Windows drives. The doc does recommend confirming root and preferring targeted edits.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is downloaded or written by the skill itself.

Credentials

The skill requests no environment variables or credentials. It implicitly requires access to the host filesystem (/mnt/*), which is appropriate for the stated purpose. It suggests using 'rg' for searches but does not declare it as a required binary — this is a usability note rather than a security mismatch.

Persistence & Privilege

The skill is not marked always:true and does not request persistent system-level privileges or modify other skills' configs. Autonomous invocation is allowed by platform default but not uniquely elevated here.

Assessment

This instruction-only skill is coherent for editing an Obsidian vault from WSL, but be aware it operates directly on your mounted Windows filesystem. Before using: (1) confirm the exact vault root path the agent will operate on; (2) make a backup or test on a copy before running bulk or automated edits; (3) require explicit confirmation for any write/bulk-change actions; (4) install ripgrep (rg) if you want the fast search behavior the skill suggests; (5) remember a misidentified path could allow reading or modifying other Windows files — restrict the agent's actions or review edits if you need tighter control.

Obsidian Vault (WSL)

Use this skill when the vault lives on Windows but is being accessed from WSL through /mnt/<drive>.

Workflow

1. Identify the vault root from the user-provided path before doing broad searches or edits.
2. Operate on the filesystem path directly; Obsidian does not require a special API for normal note work.
3. Preserve existing frontmatter, wiki-links, embeds, headings, and folder structure unless the user asks to change them.

Vault Location

Do not assume a fixed vault path.

Common patterns:

• Windows: C:\Users\<user>\Documents\<vault>\
• Windows: D:\Notes\<vault>\
• WSL: /mnt/c/Users/<user>/Documents/<vault>/
• WSL: /mnt/d/Notes/<vault>/

Treat the vault root as the directory containing the Obsidian note tree.

Path Translation

Windows -> WSL: C:\path\to\file -> /mnt/c/path/to/file
Windows -> WSL: D:\path\to\file -> /mnt/d/path/to/file
WSL -> Windows: /mnt/c/path     -> C:/path
WSL -> Windows: /mnt/d/path     -> D:/path

Replace backslashes with forward slashes and lowercase the drive letter under /mnt/<drive>.

Common Operations

Read a note

cat "/mnt/<drive>/<vault>/<path>/<filename>.md"

Search the vault

Prefer rg for speed:

rg "search term" "/mnt/<drive>/<vault>/"

Edit a note

Edit the markdown file in place with targeted changes instead of rewriting the whole note when possible.

Create a new note

Use a minimal template when metadata is needed:

---
title: Note Title
tags: []
---

# Note Title

Obsidian Conventions

• Notes are markdown files ending in .md
• YAML frontmatter is commonly used for metadata such as title, tags, and aliases
• Internal links use [[Note Name]]
• Embeds use ![[Note Name]]
• Callouts use > [!type]

Working Rules

• Confirm the vault root before making broad searches or bulk changes
• Prefer targeted edits over full-file rewrites
• Keep filenames, wiki-links, and folder structure consistent with the existing vault