Obsidian Plugin Development
v1.0.0Create and develop Obsidian plugins from scratch. Use when building a new Obsidian plugin, scaffolding from the sample-plugin-plus template, or developing plugin features. Covers project setup, manifest configuration, TypeScript development, settings UI, commands, ribbons, modals, and Obsidian API patterns.
⭐ 2· 1.7k·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description match the content: an instruction-only skill for building Obsidian plugins. However, the SKILL.md expects tools like git, gh (GitHub CLI), pnpm, and standard Unix commands (cp, ln) but the registry metadata declares no required binaries — a mismatch that should be clarified.
Instruction Scope
Instructions legitimately cover cloning a GitHub template, running pnpm install, executing template scripts (e.g., ./scripts/setup-ref-links.sh), building, and copying output into ~/.obsidian/plugins. These are expected for plugin development, but running template scripts and package install scripts can execute arbitrary code — the skill does not include or show those scripts, so users should inspect them first.
Install Mechanism
No install spec and no code files are provided; the skill is instruction-only and does not itself write files or download archives. This reduces surface area compared to skills that install remote binaries.
Credentials
The skill requests no environment variables or credentials and does not declare access to unrelated services. That matches the declared metadata.
Persistence & Privilege
The skill is not forced-always or otherwise privileged. It is user-invocable and can be called autonomously (platform default), which is expected for a dev helper and is not by itself a red flag.
What to consider before installing
This skill is an instruction-only guide for building Obsidian plugins and is mostly coherent, but before you follow its steps:
- Expect to need git, the GitHub CLI (gh) or at least git + GitHub access, and pnpm; the metadata did not list these binaries — install or verify them yourself.
- The workflow instructs cloning a template repo and running pnpm install and template scripts (e.g., ./scripts/setup-ref-links.sh). Inspect the template repository, package.json, and any scripts referenced before running them — npm/pnpm install can run arbitrary lifecycle scripts.
- Review any scripts and the generated main.js/manifest.json before copying them into your ~/.obsidian/plugins folder and enabling the plugin in Obsidian. Treat the template repo as untrusted until audited.
- If you want to be extra safe, run pnpm install in an isolated environment (container or VM), or review dependencies and lockfiles first.
If you want, I can: list the exact commands the skill will run, parse the remote template's package.json/scripts (if you provide it or allow me to fetch the repo), or critique a plugin produced from this template for suspicious code or network calls.Like a lobster shell, security has layers — review code before you run it.
latestvk970sbrnmmrh3tvbp7f4sy898h802stj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.