obsidian-plugin-release

Coordinate Obsidian plugin releases and synchronize manifest, versions, and package metadata.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/magarcia/pylon-sync --skill obsidian-plugin-release-magarcia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-plugin-release
Source: https://github.com/magarcia/pylon-sync/tree/main/.agents/skills/obsidian-plugin-release
Command: npx skills add https://github.com/magarcia/pylon-sync --skill obsidian-plugin-release-magarcia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plugin developers often stumble over inconsistent manifest versions, missing release artifacts, and tangled submission requirements that delay Obsidian community releases, and this Skill outlines every checklist item so publishing flows reliably.

Core Features & Use Cases

  • Release Artifact Enforcement: Lists the required main.js, manifest.json, and optional styles.css files to attach to every GitHub Release so BRAT and the community store always fetch valid builds.
  • Metadata Synchronization: Guides you through keeping manifest.json, versions.json, and package.json in lockstep while enforcing semver tags that match GitHub releases and PR policies.
  • Review and Automation Prep: Details the submission checklist, community plugin review criteria, and GitHub Actions workflows needed to validate builds, run tests, and automate release creation from tagged commits.

Quick Start

Ensure manifest, versions, package, and Git tag match the new version before pushing so GitHub Actions can publish release artifacts.

Frequently Asked Questions about obsidian-plugin-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare an Obsidian plugin for a GitHub release?

Obsidian plugin release workflows coordinate GitHub releases by enforcing required build artifacts like main.js and manifest.json, ensuring valid builds for BRAT and the community store.

How do I synchronize manifest.json and versions.json when publishing an Obsidian plugin?

Synchronizing manifest.json and versions.json requires keeping both files in lockstep with package.json and enforcing semver Git tags that match your GitHub releases and PR policies.

What files are required for an Obsidian community plugin submission?

Obsidian community plugin submissions require attaching main.js, manifest.json, and optional styles.css to GitHub Releases, alongside synchronized versions.json metadata for review validation.

Can I automate Obsidian plugin releases using GitHub Actions?

You can automate Obsidian plugin releases using GitHub Actions workflows triggered by version tags to validate builds, run tests, and automatically publish release artifacts.

Why does my Obsidian plugin version mismatch fail the community review checklist?

Obsidian plugin community review checklist failures often stem from inconsistent manifest versions, missing release artifacts, or unsynchronized versions.json files that delay community releases.

Does configuring BRAT beta workflows require specific manifest versioning?

Yes, configuring BRAT beta workflows requires strict manifest versioning and synchronization across package.json and Git tags to ensure BRAT fetches valid plugin builds from GitHub Releases.