Obsidian Plugin Release

What it does

When your agent uses it

• User says release the plugin
• Bump <plugin to X.Y.Z
• Ship a new Obsidian release
• Tag a new plugin version

Example prompts

• “release the plugin”
• “bump <plugin to X.Y.Z”
• “ship a new Obsidian release”
• “/obsidian-plugin-release”

Requirements

• Node.js

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

1. 1Verify clean tree — abort if uncommitted changes (unless --allow-dirty).
2. 2Verify version is new — versions.json must not already contain it.
3. 3Bump version atomically — write the same to manifest.json, package.json, and append versions.json keyed to current minAppVersion. Use…
4. 4Build — bun run build. Abort on non-zero.
5. 5Lint — bunx eslint src/ (skip if user has no src/ — JS-only plugins exist). Abort on errors.
6. 6Stage — git add manifest.json package.json versions.json main.js styles.css. Only those 5 files.
7. 7Commit — conventional message, no Co-Authored-By
8. 8Push main — git push origin .
9. 9Tag — git tag -a -m "Release " (annotated because tag.gpgSign=true is common; annotated works either way).
10. 10Push tag — git push origin . This triggers the release workflow.
11. 11Wait for workflow — gh run watch --exit-status against the latest run on this tag. Abort if it fails.
12. 12Verify release — gh release view --json assets must include main.js, manifest.json, styles.css. Attestation is verified via gh attestation…

What it can do on your machine

Read from SKILL.md and the folder at commit f0fe474. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 1 file in scripts/ (TypeScript and JavaScript), which the agent can run.

  Shell commands in SKILL.md call:

  • git
  • gh
  • bun
  • bunx
  • npm
  • npx

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Hosts in commands or code, which the agent is likely to contact:

  • community.obsidian.md

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Obsidian Plugin Release loads about 1.8k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 183 tokens; SKILL.md has 771 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~183

When it runs · the whole SKILL.md, loaded when a task matches

~1.8k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~3.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from crafter-station/skills at commit f0fe474, republished under its MIT licence (© crafter-station). 771 words, ~1,797 tokens.

name

obsidian-plugin-release

description

Release a new version of an Obsidian community plugin without forgetting steps. Use when: (1) user says "release the plugin", "bump <plugin> to X.Y.Z", "ship a new Obsidian release", "tag a new plugin version", "publish to the obsidian directory", (2) the working directory contains manifest.json + main.js + versions.json (Obsidian plugin signature), (3) user wants to scaffold the release workflow into an existing plugin (`scaffold-workflow` arg). Handles version bump across manifest.json + package.json + versions.json, build, lint, conventional commit, signed annotated tag, push, and lets the GitHub Actions workflow publish the release with build-provenance attestation. Idempotent and dry-run-safe.

version

1.0.0

bun run scripts/release.ts <version>          # via package.json script if user added it
# OR direct
~/.claude/skills/obsidian-plugin-release/scripts/release.ts <version>

© crafter-station, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in skills/obsidian-plugin-release of crafter-station/skills.

• SKILL.md
• references/changelog-style.md
• references/scanner-warnings.md
• scripts/release.ts
• templates/eslint.config.mjs
• templates/release.yml

Open the folder on GitHubat commit f0fe474