obsidian-path-rules

To validate the SMB mount path before capturing articles in Obsidian, the skill checks the network share mount state to ensure files are written directly to the shared NAS storage instead of a local fallback disk.

The correct file naming convention for Obsidian article ingestion applies a structured format using the year, platform, month, day, and timestamp to ensure deterministic directory organization across cross-machine access.

To avoid filename collisions when multiple agents write notes to an Obsidian vault, the system scans existing files in the dated directory before creating new ones to handle multi-agent memo numbering safely.

Obsidian captures save to a local disk instead of shared NAS storage when the SMB network share is not properly mounted, requiring mount verification and recovery steps before initiating any write operations.

Yes, you can use this path validation for cross-machine Obsidian workflows on Windows, as it enforces shared-storage path normalization and deterministic directory conventions for safe team access.