Agent skill · software engineering · jeremylongshore
obsidian-ci-integration
Set up GitHub Actions CI/CD for Obsidian plugin development.
Why this skill is useful
Adds multiple executable GitHub Actions workflows and a version bump script specifically for Obsidian plugin development, which are not commonly found in public documentation.
What it needs
Requires npm installed locally. Requires github account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Obsidian CI Integration Overview GitHub Actions workflows for Obsidian plugin development: build validation on every push, automated releases when you tag, version-bump scripting, manifest.json validation, and BRAT beta channel support. Prerequisites GitHub repository with an Obsidian plugin Working local build (npm run build produces main.js) manifest.json and versions.json in repo root GitHub Actions enabled on the repository Instructions Step 1: Create Build Workflow Step 2: Create Release Workflow Step 3: Create Version Bump Script Step 4: Wire Version Bump into package.json Now npm version patch (or minor/major) runs the bump script automatically. Step 5: Add Manifest Validation Workflow Step 6: BRAT Beta Support Add a beta-manifest.json for BRAT beta testers: Beta users install via BRAT by entering your GitHub repo URL. BRAT fetches the latest release (including pre-releases) automatically — no submission to the community repo needed. Output .github/workflows/build.yml — validates build on every push/PR .github/workflows/release.yml — creates GitHub release with main.js, manifest.json, styles.css on tag push .github/workflows/validate.yml — checks version consistency across manifest, package.json, and versions.json version-bump.mjs — keeps manifest.json and versions.json in sync with package.json version Optional beta-manifest.json for BRAT beta channel Error Handling Error Cause Solution ------- ------- ---------- main.js not found Build script doesn't output to root Check esbuild outfile points to ./main.js Release has no assets Tag pushed before build Let the release workflow handle the build, don't attach manually Version mismatch Forgot npm version Run npm version patch instead of editing manifest by hand BRAT not picking up beta No pre-release on GitHub Create release and check "pre-release" checkbox npm ci fails No lockfile Commit package-lock.json to the repo Permission denied on release Missing contents: write Add permissions block to release job Exam …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/obsidian-ci-integration--b4c97a