Install the "cut-release" agent skill from https://github.com/spiculedata/saiku/tree/development/.claude/skills/cut-release into .claude/skills/cut-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cut-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.
Type 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.
skills CLI
$ npx skills add spiculedata/saiku --skill cut-release -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "cut-release" agent skill from https://github.com/spiculedata/saiku/tree/development/.claude/skills/cut-release into .agents/skills/cut-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cut-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.
skills CLI
$ npx skills add spiculedata/saiku --skill cut-release -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "cut-release" agent skill from https://github.com/spiculedata/saiku/tree/development/.claude/skills/cut-release into .cursor/skills/cut-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cut-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.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add spiculedata/saiku --skill cut-release -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "cut-release" agent skill from https://github.com/spiculedata/saiku/tree/development/.claude/skills/cut-release into .gemini/skills/cut-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cut-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.
GitHub CLI
$ gh skill install spiculedata/saiku cut-release
Installs 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).
skills CLI
$ npx skills add spiculedata/saiku --skill cut-release -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "cut-release" agent skill from https://github.com/spiculedata/saiku/tree/development/.claude/skills/cut-release into .github/skills/cut-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cut-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.
skills CLI
$ npx skills add spiculedata/saiku --skill cut-release -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "cut-release" agent skill from https://github.com/spiculedata/saiku/tree/development/.claude/skills/cut-release into .opencode/skills/cut-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cut-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
cut-release
GitHub stars
1.3k
Token cost
~502 tokens
SKILL.md length
229 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0
At a glance
Cut a Saiku release via Gitflow — version bump, release branch, PR to main, tag, back-merge, and post-release chores.
Works in 8 steps: Bump the version on a branch off… → Update CHANGELOG.md with a section for… → Cut release/X.Y.Z off development and… → …
Asked to release
Calls git, mvn and gh
Publish a new Saiku version
What it does
Cut Release is an agent skill from spiculedata/saiku. Cut a Saiku release via Gitflow — version bump, release branch, PR to main, tag, back-merge, and post-release chores. Use when asked to release, tag, or publish a new Saiku version.
Its SKILL.md is about 500 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 Development, covering Git workflow and Markdown. It works with Model Context Protocol and Git. The repository describes itself as: Open-source semantic layer: one cube for Excel (MDX/XMLA), dashboards, and AI agents (MCP). Mondrian + Apache Calcite. The licence is Apache-2.0.
When your agent uses it
Asked to release
Publish a new Saiku version
Example prompts
“/cut-release”
Requirements
Docker
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
1Bump the version on a branch off development. Every reactor pom carries the literal release version (non-SNAPSHOT).
2Update CHANGELOG.md with a section for the release, and fold in any docs/release-notes-*-draft.md. Merge this to development via PR.
3Cut release/X.Y.Z off development and push it. release-prep.yml runs the mvn verify gate.
4Open a PR from release/X.Y.Z to main and merge it once green.
5Tag the merged main HEAD and push the tag.
6Replace the auto-generated release notes (a raw commit list) with the changelog section: gh release edit vX.Y.Z --notes-file .
7Back-merge main into development via a chore/back-merge-X.Y.Z PR.
8Post-release: bump LATEST_VERSION in telemetry/wrangler.toml (PR to development), and redeploy the demo box.
What it can do on your machine
Read from SKILL.md and the folder at commit 1aec85a. 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:
git
mvn
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, 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
Cut Release loads about 502 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 229 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~48
When it runs· the whole SKILL.md, loaded when a task matches
~502
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.
Download SKILL.mdSave it as .claude/skills/cut-release/SKILL.md (or your agent's skills folder).
name
cut-release
description
Cut a Saiku release via Gitflow — version bump, release branch, PR to main, tag, back-merge, and post-release chores. Use when asked to release, tag, or publish a new Saiku version.
Cut a release
Publishing is entirely CI-driven. Pushing a v* tag runs release.yml, which publishes the fat-JAR and dist zip (GitHub release assets), module jars (GitHub Packages), the Docker image (ghcr.io/spiculedata/saiku:<version>) and the npm embed package. Never mvn deploy locally.
Bump the version on a branch off development. Every reactor pom carries the literal release version (non-SNAPSHOT).bash
versions:set misses saiku-bom/pom.xml, so fix that by hand. Check with git grep -n '<version>OLD' -- '*pom.xml'.
Update CHANGELOG.md with a section for the release, and fold in any docs/release-notes-*-draft.md. Merge this to development via PR.
Cut release/X.Y.Z off development and push it.release-prep.yml runs the mvn verify gate.
Open a PR from release/X.Y.Z to main and merge it once green.
gh pr merge can silently no-op while a required check is pending. Before tagging, confirm main actually advanced: git fetch && git log -1 origin/main should show the release merge and the new version.
Tag the merged main HEAD and push the tag.bash
git tag vX.Y.Z origin/main && git push origin vX.Y.Z
If you tagged the wrong commit: gh run cancel the release run, git push origin :refs/tags/vX.Y.Z, git tag -d vX.Y.Z, then re-tag correctly.
Replace the auto-generated release notes (a raw commit list) with the changelog section: gh release edit vX.Y.Z --notes-file <file>.
Back-merge main into development via a chore/back-merge-X.Y.Z PR.
Post-release: bump LATEST_VERSION in telemetry/wrangler.toml (PR to development), and redeploy the demo box.
Cut 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.
A skill your agent uses when the user wants to create or update a changelog, release notes, product updates, or an MDX changelog page from git history or local code changes.
Drives the basemind code-intelligence tool from the command line for symbol search, callers, git history and blame, document search and web crawling, sharing its cache with the MCP server.
Cut a Saiku release via Gitflow — version bump, release branch, PR to main, tag, back-merge, and post-release chores. Cut Release is an agent skill from spiculedata/saiku. Cut a Saiku release via Gitflow — version bump, release branch, PR to main, tag, back-merge, and post-release chores.
When should I use Cut Release?
Cut Release fits situations like: asked to release; publish a new Saiku version.
How do I install Cut Release in Claude Code?
Run `npx skills add spiculedata/saiku --skill cut-release -a claude-code`. Or copy the skill folder (.claude/skills/cut-release in spiculedata/saiku) into .claude/skills/cut-release in your project. Claude Code loads it when a task matches its description.
How do I install Cut Release in Codex?
Run `npx skills add spiculedata/saiku --skill cut-release -a codex`. Or copy the skill folder (.claude/skills/cut-release in spiculedata/saiku) into .agents/skills/cut-release in your project. Codex loads it when a task matches its description.
Can I use Cut 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 spiculedata/saiku --skill cut-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/cut-release, .gemini/skills/cut-release, .github/skills/cut-release and .opencode/skills/cut-release in your project.
What does Cut Release need to run?
Going by SKILL.md and its folder, Cut Release needs the command-line tools its instructions call (git, mvn and gh). Our summary lists: Docker.
Does Cut Release access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Cut 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 Cut Release use?
Cut Release is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cut Release use?
About 502 tokens (SKILL.md is roughly 2k 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 Cut Release?
Skills that share tags, products or a category with Cut Release: Changelog Writer (jihe520/mindpocket, 350 stars), E2b Sandbox (agent-sandbox/agent-sandbox, 218 stars), GitHub (swarmclawai/swarmclaw, 688 stars) and basemind CLI Codebase Navigator (Goldziher/basemind, 108 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cut Release?
spiculedata (a GitHub organization) maintains it in spiculedata/saiku, which has 1,329 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.
Source: spiculedata/saiku on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
