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

Kon Release Publish

by 0xku in 0xku/kon

Tag, publish to PyPI, and create GitHub release for Kon with validation and rollback-safe steps

MITAuto-check passedDevelopment

Install Kon Release Publish

skills CLI
$ npx skills add 0xku/kon --skill kon-release-publish -a claude-code

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

GitHub CLI
$ gh skill install 0xku/kon kon-release-publish --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/0xku/kon.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/kon-release-publish .claude/skills/kon-release-publish && 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
kon-release-publish
GitHub stars
354
Token cost
~899 tokens
SKILL.md length
425 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Tag, publish to PyPI, and create GitHub release for Kon with validation and rollback-safe steps

  • Works in 10 steps: Preflight → Update CHANGELOG.md → Version bump → …
  • Development work in your project
  • SKILL.md covers Inputs to confirm, Versioning requirement, Files to bump and Release workflow, plus 2 more sections
  • Calls git and uv; reaches pypi.org; needs TWINE_PASSWORD

What it does

Kon Release Publish is an agent skill from 0xku/kon. Tag, publish to PyPI, and create GitHub release for Kon with validation and rollback-safe steps

Its SKILL.md is about 900 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 and Git. The repository describes itself as: Kon is a minimal coding agent (and also a highly opinionated one). The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/kon-release-publish”

Requirements

  • Python 3

Workflow steps

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

  1. Preflight
  2. Update CHANGELOG.md
  3. Version bump
  4. Quality gates
  5. Commit
  6. Tag
  7. Push
  8. Build + verify artifacts
  9. Publish to PyPI
  10. Create GitHub release

What it can do on your machine

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

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • pypi.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • TWINE_PASSWORD

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Kon Release Publish loads about 899 tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 425 words of instructions outside code blocks.

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

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 0xku/kon at commit f5862a0, republished under its MIT licence (© 0xku). 425 words, ~899 tokens.

Download SKILL.mdSave it as .claude/skills/kon-release-publish/SKILL.md (or your agent's skills folder).
name
kon-release-publish
description
Tag, publish to PyPI, and create GitHub release for Kon with validation and rollback-safe steps

Kon Release + PyPI Publish

Use this skill when the user asks to cut a new Kon version, tag it, publish to PyPI, and/or create a GitHub release.

Inputs to confirm

  • Target version (example: 0.2.1)
  • Base range for notes (usually previous tag, example: v0.2.0..HEAD)
  • Whether to push main
  • Whether to publish to PyPI now
  • Whether to create GitHub release now

Versioning requirement

  • Kon's update check only supports strict numeric MAJOR.MINOR.PATCH versions such as 0.2.7 and 0.3.0.
  • Do not cut releases with PyPI/PEP 440 prerelease or suffix forms like 0.3.0rc1, 0.3.0b1, 0.3.0.post1, or 0.3.0.dev1 unless the update-check logic is updated first.
  • Even though PyPI commonly allows those formats, Kon releases should continue following plain X.Y.Z so update detection stays correct.

Files to bump

  • pyproject.toml → [project].version
  • src/kon/version.py → fallback VERSION = "..."
  • uv.lock → local package version block

Release workflow

  1. Preflight

    • git status --short --branch must be clean (or confirm with user)
    • git tag --list and git log --oneline <prev_tag>..HEAD to summarize changes

  2. Update CHANGELOG.md

    • Replace the ## [Unreleased] section's - No changes yet. with a new versioned heading: ## <version> - YYYY-MM-DD
    • Use git log --oneline <prev_tag>..HEAD to categorize changes into ### Added, ### Changed, ### Fixed sections
    • Credit external contributors with - @username
    • Commit message: docs: update changelog for <version>

  3. Version bump

    • Update version in all 3 files above

  4. Quality gates

    • uv run ruff format .
    • uv run ruff check .
    • uv run pyright .
    • uv run pytest

  5. Commit

    • Commit message: build: bump version to <version>

  6. Tag

    • Annotated tag: git tag -a v<version> -m "v<version> ..."
    • Include concise "changes since previous tag" bullets

  7. Push

    • git push origin main
    • git push origin v<version>

  8. Build + verify artifacts

    • rm -rf dist && uv build
    • uv run python -m twine check dist/*

  9. Publish to PyPI

    • Prefer token file if present (example ~/.pypi-token):
    • TWINE_USERNAME=__token__ TWINE_PASSWORD="$(< ~/.pypi-token)" uv run python -m twine upload dist/*
    • Verify:
      • https://pypi.org/project/kon-coding-agent/<version>/
      • https://pypi.org/pypi/kon-coding-agent/json reports latest version

  10. Create GitHub release

Show full SKILL.md (116 more words)Show less
  • If token exists at ~/.github-token, call Releases API:
  • POST /repos/<owner>/<repo>/releases with:
    • tag_name: v<version>
    • target_commitish: main
    • name: v<version>
    • generate_release_notes: true
  • If 403 occurs, report missing token scopes/permissions (contents:write required)

Important notes

  • Tagging and GitHub release are separate:
    • Tag = git ref in repository
    • Release = GitHub object attached to a tag (notes/assets)
  • You can do either independently, but most projects do both together for user-facing releases.
  • If PyPI publish succeeds but GitHub release fails, do not retag/re-publish. Just fix auth and create the release for the existing tag.

Output checklist to report

  • Changelog updated for <version>
  • Version bumped in all files
  • Checks passed
  • Commit hash
  • Tag created and pushed
  • PyPI upload URL
  • GitHub release URL (or exact error + remediation)

© 0xku, 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 .agents/skills/kon-release-publish of 0xku/kon.

Open the folder on GitHubat commit f5862a0

Compare with similar skills

Kon Release Publish 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.

Kon Release Publish compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Kon Release Publish this skill0xku/kon354—~899Automated safety check: PassMIT
Hunk Release Workflowmodem-dev/hunk9.6k—~3.8kAutomated safety check: PassMIT
Ansible Backport Creatoransible/ansible71k—~1.2kAutomated safety check: PassGPL-3.0
Worktrunk Release Workflowmax-sixty/worktrunk9.2k—~7.5kAutomated safety check: PassCustom licence
Git Gh Pat AuthNEventStore/NEventStore1.6k—~828Automated safety check: PassMIT
Coffee GB Releasetrekawek/coffee-gb1.2k—~1.4kAutomated safety check: PassMIT

Similar skills

  • 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.

    9.6k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Ansible Backport Creator

    ansible/ansible

    Creates backports of a merged Ansible devel pull request onto the right stable branches by cherry-picking its merge commit onto new backport branches.

    71k GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Worktrunk Release Workflow

    max-sixty/worktrunk

    Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.

    9.2k GitHub stars~7.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Git Gh Pat Auth

    NEventStore/NEventStore

    A skill your agent uses when: authenticating git and GitHub CLI for NEventStore tasks, fixing gh auth errors, setting PAT environment variables, preparing a shell session for git push and gh issue…

    1.6k GitHub stars~828 tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • Coffee GB Release

    trekawek/coffee-gb

    Releases the current Coffee GB Maven snapshot through the GitHub Maven release workflow, then verifies and curates the tag and GitHub release.

    1.2k GitHub stars~1.4k tokensUpdated 10 days ago
    DevelopmentAuto-check passed

  • ZCF Release Automation

    UfoMiao/zcf

    Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.

    6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from 0xku/kon

  • Kon Tmux Test

    0xku/kon

    E2E testing of kon using tmux sessions; IMPORTANT: only trigger this skill when user asks for e2e testing of kon

    354 GitHub stars~2.8k tokensUpdated 8 days ago
    Auto-check passed

  • Init

    0xku/kon

    Create or update AGENTS.md for this repository. An agent skill from 0xku/kon.

    354 GitHub stars~900 tokensUpdated 8 days ago
    Auto-check passed

  • Review

    0xku/kon

    Review code changes and return prioritized, actionable findings

    354 GitHub stars~958 tokensUpdated 8 days ago
    Auto-check passed

Works with

Categories

Questions about Kon Release Publish

What does Kon Release Publish do?

Tag, publish to PyPI, and create GitHub release for Kon with validation and rollback-safe steps. Kon Release Publish is an agent skill from 0xku/kon.

When should I use Kon Release Publish?

Kon Release Publish fits situations like: development work in your project.

How do I install Kon Release Publish in Claude Code?

Run `npx skills add 0xku/kon --skill kon-release-publish -a claude-code`. Or copy the skill folder (.agents/skills/kon-release-publish in 0xku/kon) into .claude/skills/kon-release-publish in your project. Claude Code loads it when a task matches its description.

How do I install Kon Release Publish in Codex?

Run `npx skills add 0xku/kon --skill kon-release-publish -a codex`. Or copy the skill folder (.agents/skills/kon-release-publish in 0xku/kon) into .agents/skills/kon-release-publish in your project. Codex loads it when a task matches its description.

Can I use Kon Release Publish 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 0xku/kon --skill kon-release-publish -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kon-release-publish, .gemini/skills/kon-release-publish, .github/skills/kon-release-publish and .opencode/skills/kon-release-publish in your project.

What does Kon Release Publish need to run?

Going by SKILL.md and its folder, Kon Release Publish needs the command-line tools its instructions call (git and uv) and credentials named TWINE_PASSWORD. Our summary lists: Python 3.

Does Kon Release Publish access the network?

SKILL.md names 1 domain. In commands or code: pypi.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Kon Release Publish 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 Kon Release Publish use?

Kon Release Publish 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 Kon Release Publish use?

About 899 tokens (SKILL.md is roughly 3.6k 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 Kon Release Publish?

Skills that share tags, products or a category with Kon Release Publish: Hunk Release Workflow (modem-dev/hunk, 9.6k stars), Ansible Backport Creator (ansible/ansible, 71k stars), Worktrunk Release Workflow (max-sixty/worktrunk, 9.2k stars) and Git Gh Pat Auth (NEventStore/NEventStore, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Kon Release Publish?

0xku (a GitHub user) maintains it in 0xku/kon, which has 354 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 3, 2026.

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