A lot of people write Obsidian plugins now, often with AI help (I do too), and many of us hit the same things: the plugin works on desktop and breaks on phones, the directory rates it "Satisfactory" for warnings you only see after you publish, and the README needs screenshots and GIFs that take a while to record by hand.
I hit all three with my plugins (Snipsy, Dashy and Garmy), so I moved the tooling into one dev dependency and made it generic. Nothing in it is tied to my plugins: it reads the id and everything else from `manifest.json`, and it plugs into an existing plugin.
What it does:
- `opdk scan` runs the community scanner's ESLint config plus its CSS, source and manifest checks over every file git tracks, so you see the scorecard warnings before you release.
- `opdk build` bundles for the browser platform and fails if Node-only code reaches `main.js`. One of my plugins once failed on every phone because of exactly that.
- Demo films: screenshots and GIFs from the real Obsidian, with captions, a visible cursor and a phone layout, ready for the README and the listing.
- `opdk release patch` bumps the version in every file, builds and attests the files in GitHub Actions, checks the draft release byte for byte against a local build, and publishes it.
- End-to-end tests with Playwright in a real Obsidian, a fresh vault per test.
- A Vitest preset and a reusable CI workflow.
- If you use Claude Code: the repo is also a Claude Code plugin with one skill per module, so you can ask "film a demo GIF of my plugin" or "why did my scorecard drop". An eval suite checks that each kind of request picks the right skill.
About the scanner: when I started, my own `opdk scan` said 0 on two plugins that the directory rated "Satisfactory". I compared it line by line with the live scorecards and fixed the differences: the scanner type-checks with TypeScript 6, it lints folders that its published ignore list says it skips, and a few smaller things. Now `opdk scan` reports the same findings as the scorecards of my plugins' earlier releases, and all three show Review: Passed. That match comes from comparing scorecards, not from the scanner's source, and the docs mark what is inferred.
Repo: https://github.com/Dimagious/obsidian-plugin-dev-kit (MIT)
If you try it on your plugin, I'd like to hear what broke. Issues and PRs are welcome.