New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release

by dmkenney in dmkenney/xamal

Cut a Xamal release end-to-end (maintainer-only). An agent skill from dmkenney/xamal.

MITAuto-check passedDevelopment

Install Release

skills CLI
$ npx skills add dmkenney/xamal --skill release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dmkenney/xamal release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dmkenney/xamal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release .claude/skills/release && rm -rf skills-src

Use ~/.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/

Facts

Skill name
release
GitHub stars
106
Token cost
~873 tokens
SKILL.md length
447 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Cut a Xamal release end-to-end (maintainer-only). An agent skill from dmkenney/xamal.

  • Works in 7 steps: Prep. Run the version-bump skill for the… → Confirm with the user before any push:… → Commit. git add mix.exs CHANGELOG.md and… → …
  • The user wants to release x.y.z
  • SKILL.md covers The ordering invariant (why…, Steps and If the workflow fails
  • Calls git and gh

What it does

Release is an agent skill from dmkenney/xamal. Cut a Xamal release end-to-end (maintainer-only). Does the version-bump prep, then commits, pushes master, tags vx.y.z (last), and watches the Release workflow publish to Hex and create the GitHub Release. Use when the user wants to "release x.y.z", "publish to Hex", "tag and ship", or "cut a release". Requires push rights; the tag push triggers CI which needs HEXAPIKEY. For local prep only (no push), use the version-bump skill.

Its SKILL.md is about 870 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. It works with GitHub, Git and Elixir. The repository describes itself as: Deploy Elixir apps to bare metal servers. Like Kamal, but with native releases + Caddy instead of Docker. The licence is MIT.

When your agent uses it

  • The user wants to release x.y.z
  • CI which needs HEXAPIKEY

Example prompts

  • “release x.y.z”
  • “publish to Hex”
  • “tag and ship”
  • “/release”

Requirements

  • A credential in HEX_API_KEY

Workflow steps

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

  1. Prep. Run the version-bump skill for the target version (clean/current
  2. Confirm with the user before any push: show the version delta, the two
  3. Commit. git add mix.exs CHANGELOG.md and commit with the message
  4. Push master. git push origin master. Note: master is branch-
  5. Tag last, then push the tag.
  6. Watch the workflow. Find the run
  7. Verify the outputs and report

What it can do on your machine

Read from SKILL.md and the folder at commit 830bd63. 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
    • 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

Release loads about 873 tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 447 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~111
When it runs · the whole SKILL.md, loaded when a task matches
~873

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 dmkenney/xamal at commit 830bd63, republished under its MIT licence (© dmkenney). 447 words, ~873 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Cut a Xamal release end-to-end (maintainer-only). Does the version-bump prep, then commits, pushes master, tags vx.y.z (last), and watches the Release workflow publish to Hex and create the GitHub Release. Use when the user wants to "release x.y.z", "publish to Hex", "tag and ship", or "cut a release". Requires push rights; the tag push triggers CI which needs HEX_API_KEY. For local prep only (no push), use the version-bump skill.
metadata.version
1.0.0

Release

Cut a release of the Xamal Hex package. This is the privileged half — it pushes to master and pushes a tag, which triggers the Release workflow (.github/workflows/release.yml) to run mix hex.publish and create the GitHub Release. Only run when the user has push rights and intends to ship publicly.

This skill is about releasing the Xamal package to Hex — it is not about deploying an app with Xamal (mix xamal.deploy). Don't conflate them.

The ordering invariant (why this skill exists)

mix hex.publish reads the version from mix.exs, not from the git tag. So the tag must point at a commit where mix.exs already says the matching version, and the CHANGELOG.md must already have a ## [x.y.z] section (the workflow's awk extractor pulls release notes from it). Get the order wrong and you publish the wrong version or get a validation failure. Always push the version-bump commit first, then tag last.

Steps

  1. Prep. Run the version-bump skill for the target version (clean/current check, bump mix.exs, roll the changelog, verify wiring, mix ci). Do not proceed unless mix ci passed.

  2. Confirm with the user before any push: show the version delta, the two changed files, and the changelog section that becomes the release notes.

  3. Commit. git add mix.exs CHANGELOG.md and commit with the message Bump version to x.y.z (imperative mood, no AI attribution — see AGENTS.md).

  4. Push master. git push origin master. Note: master is branch- protected (normally requires a PR). The push may report a bypass — that's expected for a maintainer with admin. If it's rejected for being behind, stop, integrate, and re-run from prep.

  5. Tag last, then push the tag. git tag vx.y.z <bump-commit> then git push origin vx.y.z. If a stale vx.y.z tag already exists (e.g. a failed earlier attempt), delete it first locally and on the remote: git tag -d vx.y.z && git push origin :refs/tags/vx.y.z, then re-create it at the bump commit.

  6. Watch the workflow. Find the run (gh run list --workflow=Release --limit 3) and watch it (gh run watch <id> --exit-status). Expect every step green: Verify build → Publish package → Extract changelog section → Create GitHub Release.

  7. Verify the outputs and report:

    • GitHub Release: gh release view vx.y.z — confirm the notes match the changelog section.
    • Hex publish succeeded (the "Publish package" step is green).
Show full SKILL.md (66 more words)Show less

If the workflow fails

  • "Building xamal a.b.c" shows the wrong version / "Validation error(s)" → the tag points at a commit whose mix.exs is stale. The version bump didn't land before the tag. Fix mix.exs, push, delete + re-create the tag at the correct commit.
  • Empty / fallback release notes → no ## [x.y.z] section in CHANGELOG.md. Add it, then re-tag.
  • Always read the failing step's log: gh run view <id> --log-failed.

© dmkenney, 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 dmkenney/xamal.

Open the folder on GitHubat commit 830bd63

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.

Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skilldmkenney/xamal106—~873Automated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
PR Review State Fetchprisma/orm48k—~767Automated safety check: PassApache-2.0

Similar skills

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • PR Review State Fetch

    prisma/orm

    Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated today
    DevelopmentAuto-check passed

  • Mole Release Notes Publisher

    tw93/Mole

    Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

More from dmkenney/xamal

  • Version Bump

    dmkenney/xamal

    Prepare a new Xamal version locally — bump @version in mix.exs, roll the CHANGELOG.md

    106 GitHub stars~911 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Release

What does Release do?

Cut a Xamal release end-to-end (maintainer-only). An agent skill from dmkenney/xamal. Release is an agent skill from dmkenney/xamal. Cut a Xamal release end-to-end (maintainer-only).

When should I use Release?

Release fits situations like: the user wants to release x.y.z; CI which needs HEXAPIKEY.

How do I install Release in Claude Code?

Run `npx skills add dmkenney/xamal --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in dmkenney/xamal) 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 dmkenney/xamal --skill release -a codex`. Or copy the skill folder (.claude/skills/release in dmkenney/xamal) 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 dmkenney/xamal --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 and gh). Our summary lists: A credential in HEX_API_KEY.

Does 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 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 873 tokens (SKILL.md is roughly 3.5k 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: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

dmkenney (a GitHub user) maintains it in dmkenney/xamal, which has 106 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.

Source: dmkenney/xamal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.