obsidian-local-dev-loop
Pass
Audited by Gen Agent Trust Hub on Sep 9, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: The skill guides the user through setting up a local development environment for Obsidian plugins, including cloning templates, symlinking directories, and configuring build tools. The instructions follow established best practices for plugin development.
- [EXTERNAL_DOWNLOADS]: Instructions include cloning the official Obsidian sample plugin from
github.com/obsidianmd/obsidian-sample-plugin. This is a well-known repository provided by the official Obsidian organization and is the standard starting point for plugin development. - [COMMAND_EXECUTION]: Uses standard development commands such as
git,npm,ln, andmkdirto manage project files and dependencies. These commands are localized to the user's development directory and a dedicated vault path (~/ObsidianDev). - [DYNAMIC_EXECUTION]: Configures
esbuildfor watch mode andvitestfor unit testing. These are industry-recognized development tools used to compile and test TypeScript code during the development lifecycle. - [PRIVILEGE_ESCALATION]: Notes that Windows users may require an administrator terminal to execute the
mklinkcommand for creating directory symlinks. This is a documented operating system requirement and is presented as a manual step for the user to perform.
Audit Metadata