skills.rest
GoBeromsu
GoBeromsuCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

obsidian-publish

Submit Obsidian plugins to the community releases process with automated PRs.

2|Updated Mar 6, 2026
Search Tags:#release#obsidian#publish#pr-submission#obsidian-publish#plugin-submission
One-click install
npx skills add https://github.com/GoBeromsu/obsidian-workspace --skill obsidian-publish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: obsidian-publish
Source: https://github.com/GoBeromsu/obsidian-workspace/tree/main/.claude/skills/obsidian-publish
Command: npx skills add https://github.com/GoBeromsu/obsidian-workspace --skill obsidian-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill guides first-time Obsidian plugin authors through the community submission workflow, ensuring they understand the one-time release flow and how to meet automated bot checks.

Core Features & Use Cases

  • Provides a structured, step-by-step process for code review, readiness checks, release tagging, and automated PR submission.
  • Helps users verify that manifest.json, package.json, README, LICENSE, and release assets meet Obsidian's community submission requirements.
  • Guides users through re-triggering bot validation and resolving common submission issues when the bot flags problems.

Quick Start

From the plugin root, follow Steps 0 through 4 to prepare and submit your plugin to the Obsidian community.

Frequently Asked Questions about obsidian-publish

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

FAQPage Schema
How do I submit an Obsidian plugin to the community directory for the first time?▼

To submit an Obsidian plugin, you must complete readiness checks, verify your GitHub release, and submit an automated PR. This enforces validation of your manifest.json, README, LICENSE, and release assets.

What files are checked during an Obsidian plugin submission?▼

Obsidian plugin submission checks validate manifest.json, package.json, README, LICENSE, and release assets. Ensuring these files meet community requirements helps you pass automated bot validation.

Why did the Obsidian bot flag my plugin submission?▼

The Obsidian submission bot flags plugins when automated validation fails. You must resolve common submission issues like incorrect manifest formatting or missing assets and re-trigger validation through the bot feedback cycle.

Do I need a GitHub release before submitting my Obsidian plugin?▼

Yes, GitHub release verification is a required step before submitting your Obsidian plugin PR. The release must contain the correct assets to pass the end-to-end community publishing workflow.

What is the best way to prepare an Obsidian plugin for a community release?▼

The best way to prepare an Obsidian plugin release is following a structured process of code review, readiness checks, release tagging, and automated PR submission to meet all community submission requirements.

Related Skills

Explore More Software Engineering Skills→
Pryma-TechPryma-Tech

release

Automate version bumps, tests, commits, tagging, publishing, and GitHub releases.

Community
Advanced
richkuorichkuo
45

work-on-issue-loop

Automate GitHub issue implementation, pull request creation, and review feedback resolution.

Community
Advanced
corv89corv89
25

release

Merge PRs, tag versions, and publish GitHub releases with changelog notes.

Community
Advanced
mmartinsolivmmartinsoliv

pr-review-pending

Create pending GitHub pull request review comments from code review findings.

Community
Advanced