mp-publish-obsidian-plugin

Publish an Obsidian plugin to the community directory with validated manifest and release assets.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-publish-obsidian-plugin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mp-publish-obsidian-plugin
Source: https://github.com/MartinoPolo/mpx-claude-code/tree/main/skills/mp-publish-obsidian-plugin
Command: npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-publish-obsidian-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, npm, gh, git.

What problem does it solve?

This Skill solves the problem of manually and error-prone publishing an Obsidian plugin to the official community directory with correct metadata, release assets, and validation-ready PRs.

Core Features & Use Cases

  • Manifest-to-release validation: Ensures manifest.json values (id, name, description punctuation, version, author fields) meet Obsidian bot expectations before any GitHub actions.
  • Deterministic release publishing: Builds the plugin, creates/updates the GitHub release for the exact version (no v prefix), and uploads required assets like main.js and manifest.json (and styles.css when applicable).
  • Community directory PR automation: Forks or syncs obsidianmd/obsidian-releases, inserts the plugin entry into community-plugins.json with exact character matching, fetches the official PR template, and opens a compliant PR.

Quick Start

Use mp-publish-obsidian-plugin to publish your Obsidian plugin to obsidianmd/obsidian-releases by validating your manifest, building the release artifacts, creating the GitHub release, updating community-plugins.json, and opening the official-template PR.

Frequently Asked Questions about mp-publish-obsidian-plugin

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

FAQPage Schema
How do I publish an Obsidian plugin to the community directory?

To publish an Obsidian plugin, you must validate manifest.json metadata, build release artifacts like main.js, create a GitHub release for the exact version, and open a PR inserting your plugin entry into community-plugins.json.

What are the requirements for Obsidian plugin manifest validation?

Obsidian plugin manifest validation requires exact description punctuation and character-for-character description matching, while ensuring id, name, version, and author fields meet Obsidian bot expectations before initiating GitHub actions.

Do I need to include styles.css in my Obsidian plugin release?

You must include main.js and manifest.json in your GitHub release, and styles.css should also be uploaded when applicable to ensure all required release assets are present for the community listing.

How do I automate the community-plugins.json PR for an Obsidian plugin?

Automating the community-plugins.json PR involves forking or syncing the obsidianmd/obsidian-releases repository, inserting your plugin entry with exact character matching, and using the official PR template to target the master branch.

Does the GitHub release version for an Obsidian plugin need a v prefix?

No, the GitHub release for an Obsidian plugin must be created for the exact version specified in your manifest without a v prefix, ensuring deterministic release publishing and correct asset uploads.

What dependencies are required to automate Obsidian plugin publishing?

Automating Obsidian plugin publishing requires node, npm, gh, and git installed in your environment to build artifacts, manage GitHub releases, handle repository forking, and submit the community-plugins.json PR.