Obsidian Plugin Release

This skill guides you through releasing, versioning, and distributing an Obsidian plugin. It focuses on everything that happens after development: version management, automated builds, submission to the community directory, beta testing, and post-release best practices.

When to Use This Skill

• Preparing a plugin for its first release
• Setting up automated GitHub Actions release workflows
• Updating manifest.json and versions.json correctly
• Submitting a plugin to the official Obsidian community directory
• Setting up BRAT beta testing for pre-release versions
• Optimizing plugin load time before release
• Storing API keys and tokens securely in a plugin
• Deciding whether a plugin should be desktop-only

Overview

A released Obsidian plugin is distributed via GitHub Releases. The community plugin system pulls main.js, manifest.json, and optional styles.css directly from release assets. To publish: