Agent skill · software engineering · jeremylongshore
obsidian-deploy-integration
Publish Obsidian plugins to the community plugin directory.
Why this skill is useful
Adds specific scripts and commands for publishing Obsidian plugins that the AI wouldn't reliably generate on its own.
What it needs
Requires gh, git, npm installed locally. Requires github account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Obsidian Plugin Deploy Integration Overview Release and distribute Obsidian plugins through multiple channels: the official community plugin directory, GitHub releases, BRAT beta testing, and manual installation. Covers the full lifecycle from building release assets to submitting your PR to the obsidian-releases repo. Prerequisites Obsidian plugin with main.ts, manifest.json, and styles.css (if applicable) GitHub repository for your plugin (public) gh CLI authenticated (gh auth status) Plugin passes obsidian-prod-checklist validation Instructions Step 1: Build Release Assets Step 2: Version Bump with version-bump.mjs Wire it into package.json so npm version triggers it automatically: Step 3: Create GitHub Release The release must include these files at the root level (not nested in folders): main.js — compiled plugin code manifest.json — plugin metadata styles.css — only if your plugin has custom styles Step 4: Submit to Community Plugins First-time submission requires a PR to the obsidian-releases repo: Review requirements the Obsidian team checks: manifest.json has all required fields (id, name, version, minAppVersion, description, author) id in manifest matches the id in your community-plugins.json entry No console.log in production code No eval() or dynamic code execution No remote code loading at runtime Plugin works on mobile if isDesktopOnly is not set Step 5: BRAT for Beta Testing Before submitting to community plugins, test your distribution via BRAT: 1. Users install BRAT from community plugins 2. In BRAT settings, they click "Add Beta Plugin" 3. They enter your GitHub repo URL: your-username/your-plugin-repo 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/obsidian-deploy-integration