obsidian-community-check

To run an Obsidian plugin community review scan automatically, this skill submits your git ref to the official review form and polls the page for pass, warning, or error findings.

Triggering an Obsidian plugin release validation check requires submitting a branch, tag, or commit to the community review page using your existing authenticated browser session to validate the release.

The Obsidian community review scan does not require a public API or CLI, because this skill interacts with the review page directly using your existing authenticated browser session.

You can automate polling the Obsidian community review page for scan completion, monitoring the status in real time and extracting exact pass, warning, or error findings.

The best way to verify an Obsidian plugin passes community review checks is automating the scan trigger and status polling to get a structured report of release-blocking issues without manual browser navigation.

You need an automated scan for Obsidian plugin marketplace publishing when preparing a new release version, ensuring the required community review checks are passed before submission.