1panel App Builder
arch3rPro/1Panel-Appstore
A skill your agent uses when packaging Docker deployments as 1Panel local app store apps, including GitHub projects, docker-compose.yml files, docker run commands, app metadata, version directories…
Meerschaum release process — bump version, update changelog, stage dev→main PR, run CI, publish to PyPI, tag, GitHub release, build/push Docker images, rebuild docs on prod VPS.
Install Release
$ npx skills add bmeares/Meerschaum --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bmeares/Meerschaum 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/bmeares/Meerschaum.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/bmeares/Meerschaum/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/bmeares/Meerschaum/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 bmeares/Meerschaum --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bmeares/Meerschaum release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bmeares/Meerschaum.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/bmeares/Meerschaum/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 bmeares/Meerschaum --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bmeares/Meerschaum release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bmeares/Meerschaum.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/bmeares/Meerschaum/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/bmeares/Meerschaum.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 bmeares/Meerschaum --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bmeares/Meerschaum release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bmeares/Meerschaum.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/bmeares/Meerschaum/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 bmeares/Meerschaum 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 bmeares/Meerschaum --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bmeares/Meerschaum.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/bmeares/Meerschaum/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 bmeares/Meerschaum --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 bmeares/Meerschaum release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bmeares/Meerschaum.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/bmeares/Meerschaum/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
- 154
- Token cost
- ~1.1k tokens
- SKILL.md length
- 402 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Meerschaum release process — bump version, update changelog, stage dev→main PR, run CI, publish to PyPI, tag, GitHub release, build/push Docker images, rebuild docs on prod VPS.
- Works in 7 steps: Bump version → Update the changelog → Stage the release branch and PR → …
- Cutting a new Meerschaum release
- SKILL.md covers 1. Bump version, 2. Update the changelog, 3. Stage the release branch… and 4. CI, plus 4 more sections
- Calls git, gh and docker; needs PYPI_TOKEN and TWINE_PASSWORD
What it does
Release is an agent skill from bmeares/Meerschaum. Meerschaum release process — bump version, update changelog, stage dev→main PR, run CI, publish to PyPI, tag, GitHub release, build/push Docker images, rebuild docs on prod VPS. Use when cutting a new Meerschaum release or preparing a release PR.
Its SKILL.md is about 1.1k 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 DevOps & Cloud, covering Deployment, Changelog and release notes and Containers. It works with Docker, GitHub and pandas. The repository describes itself as: Create and manage data pipes with Meerschaum. The licence is Apache-2.0.
When your agent uses it
- Cutting a new Meerschaum release
- Preparing a release PR
Example prompts
- “/release”
Requirements
- Python 3
- Docker
- A credential in PYPI_TOKEN
Workflow steps
7 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 89b1d6a. 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:
gitghdockerssh
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, docker and ssh, 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 these keys or tokens, usually read from environment variables:
PYPI_TOKENTWINE_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release loads about 1.1k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 402 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:67
Publish (token in `.env` as `PYPI_TOKEN`): - NoteMentions a .env fileSKILL.md:70
source .env
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 bmeares/Meerschaum at commit 89b1d6a, republished under its Apache-2.0 licence (© bmeares). 402 words, ~1,065 tokens.
Download SKILL.mdSave it as
.claude/skills/release/SKILL.md (or your agent's skills folder).- name
- release
- description
- Meerschaum release process — bump version, update changelog, stage dev→main PR, run CI, publish to PyPI, tag, GitHub release, build/push Docker images, rebuild docs on prod VPS. Use when cutting a new Meerschaum release or preparing a release PR.
Meerschaum Release Process
Follow these steps in order. The finished state: version bumped in meerschaum/config/_version.py, PR merged into main with CI passing, git tag pushed, GitHub release created, package on PyPI, Docker images on DockerHub, docs rebuilt on prod.
1. Bump version
Edit meerschaum/config/_version.py (__version__ = "X.Y.Z").
2. Update the changelog
Edit docs/zensical/news/changelog.md (the source of truth — root CHANGELOG.md is generated from it by scripts/docs.sh, which scripts/build.sh calls). Follow the existing style exactly:
- New
### vX.Y.Zheading under the current release-cycle##section, above the previous version. - One bullet per change:
- **Bolded title ending with a period.**followed by two trailing spaces (markdown line break), then an indented explanation paragraph on the next line. - Code blocks and examples are fine inside a bullet's explanation (indented to match).
Do NOT hand-edit root CHANGELOG.md; it's overwritten by the build.
3. Stage the release branch and PR
dev is recreated fresh from main for each release:
git checkout main && git pull
git branch -D dev
git checkout -b dev
# ...commit release changes (version bump, changelog, fixes)...Before the final commit, run ./scripts/build.sh — it may update requirements/*.txt and regenerate CHANGELOG.md; commit those too.
Push and open a PR from dev to main:
- Title: relevant gitmoji + version + short summary, e.g.
🐛 v3.4.6 Derive venvs path from root when MRSM_VENVS_DIR is unset. - Body: the changelog notes for this version verbatim, except the version heading uses one
#instead of###.
4. CI
The PR triggers .github/workflows/pytest.yaml on a self-hosted runner (~/actions-runner/run.sh on this machine). It runs ./scripts/test.sh db with MRSM_TEST_FLAVORS=all against the databases in tests/docker-compose.yaml.
If tests fail unexpectedly (stale DB state), reset the test databases:
cd tests/
docker compose down -v
docker compose up -dNever run two test.sh invocations concurrently (shared test_root + API port 8989).
Show full SKILL.md (147 more words)Show less
5. Merge, build, publish to PyPI
Once CI is green, mark the PR ready (release PRs often start as drafts) and merge:
gh pr ready <number>
gh pr merge <number> --squash
git checkout main && git pull
./scripts/build.sh # cleans, builds docs, regenerates requirements, builds wheel + sdist into dist/Publish (token in .env as PYPI_TOKEN):
source .env
TWINE_USERNAME=__token__ TWINE_PASSWORD="$PYPI_TOKEN" twine upload dist/*6. Tag and GitHub release
git tag -m "vX.Y.Z" vX.Y.Z # -m required: git config forces annotated tags
git push origin main --tagsCreate a GitHub release for the tag (gh release create vX.Y.Z --title "<same as PR title>" --notes-file <notes>). The release description = the PR body = the changelog notes, with the version heading demoted to a single #.
7. Prod VPS: Docker images and docs
ssh -p 2269 meerschaum@mrsm.io
cd ~/docs/Meerschaum
git pull
./scripts/docker/buildx.sh --push # build multi-arch Docker images and push to DockerHub
./scripts/build.sh # rebuild on Ubuntu/older Python (catches last-minute bugs); calls docs.sh which rebuilds the website docsOptionally run ./scripts/setup.sh (locally and on the VPS) to ensure latest dev packages before building.
Checklist
-
meerschaum/config/_version.pybumped -
docs/zensical/news/changelog.mdupdated (style matched) -
./scripts/build.shrun before final commit (requirements + CHANGELOG.md regenerated) - PR
dev→main, gitmoji title, changelog-verbatim body, CI green, merged - Wheel/sdist built from
mainand uploaded to PyPI via twine -
vX.Y.Ztag pushed; GitHub release created with same notes - Docker images built and pushed from prod VPS
- Docs rebuilt on prod VPS
© bmeares, Apache-2.0. 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 bmeares/Meerschaum.
Open the folder on GitHubat commit 89b1d6a
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 skillbmeares/Meerschaum | 154 | — | ~1.1k | Automated safety check: Notes | Apache-2.0 | |
| 1panel App Builderarch3rPro/1Panel-Appstore | 213 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Releasematrixorigin/memoria | 607 | — | ~494 | Automated safety check: Pass | Apache-2.0 | |
| Releasing MarchatCod-e-Codes/marchat | 137 | — | ~801 | Automated safety check: Pass | MIT | |
| Reflexo ReleaseMyriad-Dreamin/typst.ts | 1.2k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Railway Servicedavila7/claude-code-templates | 32k | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Release
matrixorigin/memoria
Cut a Memoria release. An agent skill from matrixorigin/memoria.
Releasing Marchat
Cod-e-Codes/marchat
Prepares marchat releases: version bumps, CHANGELOG, packaging checksums, GitHub Actions release workflow, and Docker tags.
Reflexo Release
Myriad-Dreamin/typst.ts
Guide Reflexo/typst.ts release preparation and operator handoffs.
Railway Service
davila7/claude-code-templates
Check service status, rename services, change service icons, link services, or create services with Docker images.
Project Release
swimmwatch/cloakbrowser-mcp
Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.
Related
Questions about Release
What does Release do?
Meerschaum release process — bump version, update changelog, stage dev→main PR, run CI, publish to PyPI, tag, GitHub release, build/push Docker images, rebuild docs on prod VPS. Release is an agent skill from bmeares/Meerschaum. Meerschaum release process — bump version, update changelog, stage dev→main PR, run CI, publish to PyPI, tag, GitHub release, build/push Docker images, rebuild docs on prod VPS.
When should I use Release?
Release fits situations like: cutting a new Meerschaum release; preparing a release PR.
How do I install Release in Claude Code?
Run `npx skills add bmeares/Meerschaum --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in bmeares/Meerschaum) 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 bmeares/Meerschaum --skill release -a codex`. Or copy the skill folder (.claude/skills/release in bmeares/Meerschaum) 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 bmeares/Meerschaum --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, docker and ssh) and credentials named PYPI_TOKEN and TWINE_PASSWORD. Our summary lists: Python 3; Docker; A credential in PYPI_TOKEN.
Does Release access the network?
SKILL.md contains no URLs. Its commands use git, gh, docker and ssh, 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 notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Release use?
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 Release use?
About 1.1k tokens (SKILL.md is roughly 4.3k 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: 1panel App Builder (arch3rPro/1Panel-Appstore, 213 stars), Release (matrixorigin/memoria, 607 stars), Releasing Marchat (Cod-e-Codes/marchat, 137 stars) and Reflexo Release (Myriad-Dreamin/typst.ts, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
bmeares (a GitHub user) maintains it in bmeares/Meerschaum, which has 154 GitHub stars. The repository was last updated on September 8, 2026.
Source: bmeares/Meerschaum on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.