What is release-desktop?

A release procedure for the Sapiom Studio desktop app, which is distributed as installers for macOS, Linux, and Windows. It uses Changesets to prepare version updates and Git tags to start publishing.

Use it to prepare a desktop release, create final or beta tags, and check builds before publishing.

It prevents releases from using mismatched versions or the wrong update channel.

How sapiom/sapiom-js configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to sapiom/sapiom-js. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/sapiom/sapiom-js/main/.claude/skills/release-desktop/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/sapiom/sapiom-js

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sapiom/sapiom-js/release-desktop/github.svg)](https://agentmods.dev/skills/sapiom/sapiom-js/release-desktop)

Your own site

<a href="https://agentmods.dev/skills/sapiom/sapiom-js/release-desktop"><img src="https://agentmods.dev/badge/skills/sapiom/sapiom-js/release-desktop/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sapiom/sapiom-js/release-desktop"><img src="https://agentmods.dev/badge/skills/sapiom/sapiom-js/release-desktop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,825 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00103	$0.01825
Opus 5.5	$0.00041	$0.00730
Sonnet 5.5	$0.00021	$0.00365
Haiku 4.5	$0.00010	$0.00183

Measured 8d ago against content hash 7192c713544e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-desktop scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/release-desktop/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Releasing the Sapiom Studio desktop app

The desktop app ships as signed installers (dmg/zip on macOS, AppImage/deb on Linux, nsis on Windows), NOT to npm. A release is cut by pushing a git tag on main; version bumping is handled by changesets first.

The invariant that governs everything

The tag must equal packages/harness-desktop/package.json's version exactly (e.g. tag v0.2.4 ⇔ version 0.2.4). The desktop-release.yml prepare job fails fast on a mismatch. package.json — not the tag — is the source of truth for the artifact names and the app's self-reported version and update channel.

Tag conventions (drive the update channel)

Tag	Release	Channel
`v1.2.3`	final	`latest` (everyone)
`v1.2.3-beta.1`	pre-release	`beta` (opted-in only)

workflow_dispatch (manual run of desktop-release.yml) builds artifacts only — no tag, no publish. Useful to smoke a build without releasing. Dispatch from main only: prepare fails on any other branch, because the signing secrets live in the desktop-release environment, which admits only v* tags and main.

The full flow

Every fix/feature PR carries a changeset. .changeset/<name>.md with the bumped package(s) and a summary. Format:
```
---
"@sapiom/harness-desktop": patch
"@sapiom/harness": patch
---

One-paragraph, user-facing description of the change.
```
- A change only in @sapiom/harness needs only that entry — harness-desktop gets a patch bump automatically (changeset config updateInternalDependencies: "patch", since it depends on @sapiom/harness via workspace:^). But if you want the desktop CHANGELOG to describe a desktop-side fix, add an explicit @sapiom/harness-desktop entry too.
- If a PR merged without a changeset, its fix ships silently (no changelog entry). Add the missing changeset before releasing — a later PR's changeset file is fine; changesets are just release-note artifacts on main.
- Check coverage: ls .changeset/*.md (ignore README.md) and read each header.

Read the full file on GitHub · 123 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

8d ago Changed · +6 lines 7192c713544e
2mo ago First seen · 117 lines · 103 tokens per session scan A 64d821369e81

Subscribe to this mod's changes

release-desktop is a skill published in the GitHub repository sapiom/sapiom-js (22 stars, last pushed yesterday), licensed MIT. It adds 103 tokens to every session and 1,825 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

CI and CD DevOps and cloud Git and workflow Releases

release-desktop next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-desktopsapiom/sapiom-js	Skill	22	yesterday	MIT	A	103	Claude Code
github-release-managementruvnet/RuView	Skill	103k	yesterday	MIT	A	27	Claude Code
agent-github-modesruvnet/ruflo	Skill	81k	yesterday	MIT	A	21	Claude Code
xberg-releasexberg-io/xberg	Skill	9.5k	yesterday	MIT	A	16	Claude Code, Codex
factory-shipBuilderIO/skills	Skill	4.6k	4d ago	MIT	A	28	Claude Code
releaseprcompozy/compozy	Skill	2.8k	yesterday	MIT	A	53	Claude Code, Codex
gitlab-devopsautomateyournetwork/netclaw	Skill	715	yesterday	Apache-2.0	A	67	Claude Code, Codex

sapiom-js: Skill for Claude Code