obsidian-wsl-vault-access
v1.0.0Work 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...
⭐ 1· 106·0 current·0 all-time
byWu Fei@wufei-png
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & 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.Like a lobster shell, security has layers — review code before you run it.
latestvk976kpxvjh90hgkf5v8xg3a1px83ast6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.