Store Submit
zhitongblog/solomd
Publish a SoloMD release to the stores that have no usable submission API — Google Play Console and Microsoft Partner Center — by driving them through the local Unzoo Browser REST API.
Cut a compliant ZettelFlow plugin release — version bump, versions.json, build, tag, and a GitHub Release whose notes follow the house format.
Install Release
$ npx skills add RafaelGB/Obsidian-ZettelFlow --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install RafaelGB/Obsidian-ZettelFlow release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/RafaelGB/Obsidian-ZettelFlow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release .claude/skills/release && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release" agent skill from https://github.com/RafaelGB/Obsidian-ZettelFlow/tree/main/.claude/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/RafaelGB/Obsidian-ZettelFlow/tree/main/.claude/skills/releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add RafaelGB/Obsidian-ZettelFlow --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install RafaelGB/Obsidian-ZettelFlow release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RafaelGB/Obsidian-ZettelFlow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/release .agents/skills/release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release" agent skill from https://github.com/RafaelGB/Obsidian-ZettelFlow/tree/main/.claude/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add RafaelGB/Obsidian-ZettelFlow --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install RafaelGB/Obsidian-ZettelFlow release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RafaelGB/Obsidian-ZettelFlow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/release .cursor/skills/release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release" agent skill from https://github.com/RafaelGB/Obsidian-ZettelFlow/tree/main/.claude/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/RafaelGB/Obsidian-ZettelFlow.git --path .claude/skills/release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add RafaelGB/Obsidian-ZettelFlow --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install RafaelGB/Obsidian-ZettelFlow release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RafaelGB/Obsidian-ZettelFlow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/release .gemini/skills/release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/RafaelGB/Obsidian-ZettelFlow/tree/main/.claude/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install RafaelGB/Obsidian-ZettelFlow releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add RafaelGB/Obsidian-ZettelFlow --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/RafaelGB/Obsidian-ZettelFlow.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/release .github/skills/release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/RafaelGB/Obsidian-ZettelFlow/tree/main/.claude/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add RafaelGB/Obsidian-ZettelFlow --skill release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install RafaelGB/Obsidian-ZettelFlow release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RafaelGB/Obsidian-ZettelFlow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/release .opencode/skills/release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/RafaelGB/Obsidian-ZettelFlow/tree/main/.claude/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release- GitHub stars
- 174
- Token cost
- ~1.4k tokens
- SKILL.md length
- 525 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
Cut a compliant ZettelFlow plugin release — version bump, versions.json, build, tag, and a GitHub Release whose notes follow the house format.
- Works in 9 steps: Pre-flight quality gate → Choose the version → Bump the version → …
- The user asks to release
- SKILL.md covers 0. Pre-flight quality gate, 1. Choose the version, 2. Bump the version and 3. Build & smoke-test, plus 6 more sections
- Calls git, gh and npm
What it does
Release is an agent skill from RafaelGB/Obsidian-ZettelFlow. Cut a compliant ZettelFlow plugin release — version bump, versions.json, build, tag, and a GitHub Release whose notes follow the house format. Use when the user asks to "release", "publish a new version", "cut a release", "bump the version", or "prepare a release".
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Changelog and release notes. It works with GitHub, Obsidian and npm. The repository describes itself as: ZettelFlow is a plugin for Obsidian that helps you to create and manage your notes in a Zettelkasten way. The licence is MIT.
When your agent uses it
- The user asks to release
- Publish a new version
- Bump the version
- Prepare a release
Example prompts
- “release”
- “publish a new version”
- “cut a release”
- “/release”
Workflow steps
9 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 0676350. 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
Shell commands in SKILL.md call:
gitghnpmnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, gh and npm, which can reach the network depending on how they are called.
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
Release loads about 1.4k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 525 words of instructions outside code blocks.
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
Auto-check passed
The automated check found no risky patterns in SKILL.md.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from RafaelGB/Obsidian-ZettelFlow at commit 0676350, republished under its MIT licence (© RafaelGB). 525 words, ~1,427 tokens.
Download SKILL.mdSave it as
.claude/skills/release/SKILL.md (or your agent's skills folder).- name
- release
- description
- Cut a compliant ZettelFlow plugin release — version bump, versions.json, build, tag, and a GitHub Release whose notes follow the house format. Use when the user asks to "release", "publish a new version", "cut a release", "bump the version", or "prepare a release".
Release ZettelFlow
A release is driven by pushing a git tag: .github/workflows/releases.yml runs npm ci +
npm run release, verifies the tag matches manifest.version, and creates a GitHub Release named
after the tag with dist/main.js, manifest.json, dist/styles.css. Obsidian's community
directory then runs its automated review on the new version.
Release notes live on the GitHub Release (the tag) — never in a file in the repo. Do not commit a
RELEASE_NOTES.md. The workflow publishes auto-generated notes; you then replace the body with the curated house-format notes viagh release edit(step 7).
0. Pre-flight quality gate
Run the obsidian-plugin-quality skill and resolve blocking findings. Then make sure the tree
is green and main is up to date:
git checkout main && git pull --ff-only origin main
npm run verify # typecheck + oxlint + eslint-obsidianmd + jest (all blocking)1. Choose the version
Follow semver. Confirm the minAppVersion the build actually requires (bump only if you started
using a newer Obsidian API). Work on a release/X.Y.Z branch, PR into main — never commit the
bump straight to main.
2. Bump the version
npm version X.Y.Z --no-git-tag-version--no-git-tag-version is required: it must not create the tag or commit here (we tag main
after the PR merges). The version lifecycle script runs version-bump.mjs, which updates:
package.json→X.Y.Z(npm itself)manifest.json→version(keeps itsminAppVersion)versions.json→ adds"X.Y.Z": "<minAppVersion>"(tells Obsidian which build to serve)
version-bump.mjs does NOT touch manifest-beta.json — sync it by hand (BRAT beta channel),
keeping version, minAppVersion and description in lockstep with manifest.json:
node -e 'const fs=require("fs");const m=require("./manifest.json");const b=require("./manifest-beta.json");
b.version=m.version;b.minAppVersion=m.minAppVersion;b.description=m.description;
fs.writeFileSync("manifest-beta.json",JSON.stringify(b,null,"\t")+"\n");'Verify all four agree before continuing.
3. Build & smoke-test
npm run release # tsc type-check gate, then minified build to dist/Confirm dist/main.js and dist/styles.css exist, then load them in a real vault
(.obsidian/plugins/zettelflow/) and smoke-test the primary flow (open a canvas flow, build a note).
4. Commit, PR, merge
Only the version files — no notes file.
git add manifest.json manifest-beta.json versions.json package.json package-lock.json
git commit -m "chore(release): X.Y.Z"
git push -u origin release/X.Y.Z
gh pr create --base main --title "chore(release): X.Y.Z" --body "..."
gh pr merge <n> --merge --admin --delete-branch5. Tag main and push
Only tag once the release commit is on main, and only when the user asked to release.
git checkout main && git pull --ff-only origin main
git tag X.Y.Z # tag == manifest.version, NO leading "v"
git push origin X.Y.Z # this triggers the release workflow6. Wait for the workflow
gh run watch $(gh run list --workflow=releases.yml --limit 1 --json databaseId -q '.[0].databaseId')It builds, enforces the tag/version guard, and creates the Release with the three assets.
Show full SKILL.md (226 more words)Show less
7. Write the release notes onto the Release (the house format)
Draft into a scratch file outside the repo (e.g. the session scratchpad or $TMPDIR), then:
gh release edit X.Y.Z --notes-file /path/outside/repo/notes-X.Y.Z.mdKeep this exact structure and voice; omit a section only when it has nothing in it:
# Shinny new things
- **Feature name** — what it does for the user, in one or two sentences.
# Improvements
- **Area** — what got better.
# No longer broken
- What was broken, phrased from the user's side — now fixed.
# Under the hood
- Internal/infra change worth noting.Rules that keep it consistent with previous releases:
Level-1
#headings, in that order. Yes, "Shinny" — it is the house spelling, keep it.Bullets lead with a bold subject, then an em dash
—, then plain prose.Write for users, not commits. Group many commits into one meaningful line; skip pure churn.
Draft it from the real diff:
bash git log <previous-tag>..HEAD --no-merges --pretty=format:'%s' | sed 's/ (#[0-9]*)$//' | sort -uCross-check tone against the last release:
gh release view <previous-tag> --json body -q .body.
8. Verify the release
gh release view X.Y.Z --json tagName,assets,body -q '.tagName, (.assets[].name)'- Exactly three assets:
main.js,manifest.json,styles.css. - The tag equals
manifest.jsonversion(the workflow fails the build otherwise). - The body is the curated house-format notes, not the auto-generated list.
- For an existing directory plugin no PR is needed — Obsidian picks up the new tag. For a first
submission, open a PR to
obsidianmd/obsidian-releasesadding it tocommunity-plugins.json.
Notes
- Never hand-edit
dist/— it is generated and git-ignored. - Docs deploy separately (push to
main→documentation.yml); a release tag does not deploy docs. - If the workflow fails on the tag/version guard, fix
manifest.json, delete the tag (git push --delete origin X.Y.Z), and re-tag.
© RafaelGB, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/release of RafaelGB/Obsidian-ZettelFlow.
Open the folder on GitHubat commit 0676350
Compare with similar skills
Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release this skillRafaelGB/Obsidian-ZettelFlow | 174 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Store Submitzhitongblog/solomd | 1.2k | — | ~1.7k | Automated safety check: Notes | MIT | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Version ReleaseNG-ZORRO/ng-zorro-antd | 9.2k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Hunk Release Workflowmodem-dev/hunk | 9.5k | — | ~3.8k | Automated safety check: Pass | MIT |
Similar skills
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Version Release
NG-ZORRO/ng-zorro-antd
NG-ZORRO/ng-zorro-antd repository release workflow. An agent skill from NG-ZORRO/ng-zorro-antd.
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
Release Notes
RAIT-09/obsidian-agent-client
Generate a GitHub release note draft for this Obsidian plugin repository.
More from RafaelGB/Obsidian-ZettelFlow
All 9 skills in this repoNew Action
RafaelGB/Obsidian-ZettelFlow
Scaffold a new ZettelFlow action following the project's 4-file convention (Action / Component / Settings / SettingsReader), register it, and document it.
Obsidian Plugin Quality
RafaelGB/Obsidian-ZettelFlow
Audit ZettelFlow against the official Obsidian plugin guidelines and the Community-hub automated review / quality score.
Specify
RafaelGB/Obsidian-ZettelFlow
Stage 1 of the SDD pipeline — write a ZettelFlow spec into a GitHub issue body (problem, value, functional requirements, testable acceptance criteria, capability disclosure, out-of-scope).
Sdd
RafaelGB/Obsidian-ZettelFlow
The Spec-Driven Development pipeline for ZettelFlow — the end-to-end flow (constitution → specify → plan → tasks → implement → verify) and which skill/agent owns each stage.
TDD
RafaelGB/Obsidian-ZettelFlow
The test-driven development workflow for ZettelFlow — write a failing test first, run jest, use the Obsidian mock and the bare-specifier alias mappings, and know which code is unit-testable.
Implement
RafaelGB/Obsidian-ZettelFlow
Stage 4 of the SDD pipeline — execute a ZettelFlow task checklist (in a GitHub issue comment) test-first (red → green → refactor), one commit per advance, keeping npm run verify green and CI green…
Related
Questions about Release
What does Release do?
Cut a compliant ZettelFlow plugin release — version bump, versions.json, build, tag, and a GitHub Release whose notes follow the house format. Release is an agent skill from RafaelGB/Obsidian-ZettelFlow.json, build, tag, and a GitHub Release whose notes follow the house format.
When should I use Release?
Release fits situations like: the user asks to release; publish a new version; bump the version; prepare a release.
How do I install Release in Claude Code?
Run `npx skills add RafaelGB/Obsidian-ZettelFlow --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in RafaelGB/Obsidian-ZettelFlow) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.
How do I install Release in Codex?
Run `npx skills add RafaelGB/Obsidian-ZettelFlow --skill release -a codex`. Or copy the skill folder (.claude/skills/release in RafaelGB/Obsidian-ZettelFlow) into .agents/skills/release in your project. Codex loads it when a task matches its description.
Can I use Release in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add RafaelGB/Obsidian-ZettelFlow --skill release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.
What does Release need to run?
Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git, gh, npm and node).
Does Release access the network?
SKILL.md contains no URLs. Its commands use git, gh and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Release use?
Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Release?
Skills that share tags, products or a category with Release: Store Submit (zhitongblog/solomd, 1.2k stars), Cutting A Release (TriliumNext/Trilium, 38k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Version Release (NG-ZORRO/ng-zorro-antd, 9.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
RafaelGB (a GitHub user) maintains it in RafaelGB/Obsidian-ZettelFlow, which has 174 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 8, 2026.
Source: RafaelGB/Obsidian-ZettelFlow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.