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

Kt Search Release

by jillesvangurp in jillesvangurp/kt-search

A skill your agent uses when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed…

MITAuto-check passedDevelopment

Install Kt Search Release

skills CLI
$ npx skills add jillesvangurp/kt-search --skill kt-search-release -a claude-code

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

GitHub CLI
$ gh skill install jillesvangurp/kt-search kt-search-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/jillesvangurp/kt-search.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/kt-search-release .claude/skills/kt-search-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
kt-search-release
GitHub stars
155
Token cost
~1.2k tokens
SKILL.md length
609 words
Files
3 (incl. scripts)
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed…

  • Works in 12 steps: Identify the latest semantic version tag… → Propose the next version, but stop and… → Run the readiness gate → …
  • The user wants to cut
  • SKILL.md covers What this skill does, Trigger phrases, Workflow and Guardrails, plus 3 more sections
  • Runs Shell scripts from its folder; calls git and gh

What it does

Kt Search Release is an agent skill from jillesvangurp/kt-search. Use this skill when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed, checking GitHub Actions stability, preparing release notes from diffs, or attaching CLI binaries for Homebrew-style installation.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `agents/openai.yaml` and `scripts/release_support.sh`).

It sits in Development, covering Changelog and release notes, CI/CD and Android development. It works with GitHub, GitHub Actions, Homebrew and Kotlin. The repository describes itself as: Multi platform kotlin client for Elasticsearch & Opensearch with easily extendable Kotlin DSLs for queries, mappings, bulk, and more. The licence is MIT.

When your agent uses it

  • The user wants to cut
  • Create a GitHub release for kt-search
  • Especially when the task includes version bumping
  • Validating that commits are pushed

Example prompts

  • “/kt-search-release”

Requirements

  • A Bash shell

Workflow steps

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

  1. Identify the latest semantic version tag with
  2. Propose the next version, but stop and confirm the exact version with the
  3. Run the readiness gate
  4. If the readiness check confirms HEAD == origin/master and GitHub Actions
  5. Run exactly one Gradle command for local build/publish work
  6. Create the git tag
  7. Push the tag
  8. Always package and attach the CLI binaries
  9. Summarize changes from the previous tag
  10. Check for merged PRs in the range and preserve author attribution
  11. Draft the release notes from the diff and merged PRs, then show that
  12. Create the GitHub release with

What it can do on your machine

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

    Ships 1 file in scripts/ (Shell), which the agent can run.

    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

Kt Search Release loads about 1.2k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 609 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from jillesvangurp/kt-search at commit 7ff311b, republished under its MIT licence (© jillesvangurp). 609 words, ~1,218 tokens.

Download SKILL.mdSave it as .claude/skills/kt-search-release/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
kt-search-release
description
Use this skill when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed, checking GitHub Actions stability, preparing release notes from diffs, or attaching CLI binaries for Homebrew-style installation.

KT Search Release

Use this skill for kt-search release work. It is repo-specific.

What this skill does

  • Verifies the repo is safe to release from.
  • Forces an explicit version confirmation from the user before any publish or tag step.
  • Checks that the release commit is already pushed and that GitHub Actions runs for that commit on master are complete and successful.
  • Publishes with the repo's publish.sh.
  • Builds and packages the CLI native binaries for GitHub release assets.
  • Drafts release notes from the diff since the previous tag and creates the GitHub release with attached assets.

Trigger phrases

Use this skill when the user asks to:

  • cut a release
  • bump the version and publish
  • tag a new release
  • create a GitHub release
  • attach ktsearch CLI binaries
  • prepare a release for Homebrew support

Workflow

  1. Identify the latest semantic version tag with: git tag --sort=-version:refname | sed -n '1,20p'
  2. Propose the next version, but stop and confirm the exact version with the user before any publish, tag, or release action.
  3. Run the readiness gate: ./.codex/skills/kt-search-release/scripts/release_support.sh check <version>
  4. If the readiness check confirms HEAD == origin/master and GitHub Actions is complete and green, do not re-run local Gradle verification.
  5. Run exactly one Gradle command for local build/publish work: ./gradlew -Pversion="<version>" :ktsearch-cli:assemble publish If the readiness check already confirms HEAD == origin/master and GitHub Actions is green, this command can still be used as the single publish step without any extra local test reruns.
  6. Create the git tag: git tag "<version>"
  7. Push the tag: git push --tags
  8. Always package and attach the CLI binaries: ./.codex/skills/kt-search-release/scripts/release_support.sh package <version>
  9. Summarize changes from the previous tag: git log --oneline --no-merges <previous>..HEAD git diff --stat <previous>..HEAD
  10. Check for merged PRs in the range and preserve author attribution: git log --merges --oneline <previous>..HEAD gh pr view <number> --json author,title,url
  11. Draft the release notes from the diff and merged PRs, then show that draft to the user and confirm it before creating the GitHub release.
  12. Create the GitHub release with: gh release create <version> <asset...> --title <version> --notes-file <file>
  13. Verify the uploaded assets and release URL with: gh release view <version> --json url,assets,name,tagName,publishedAt
Show full SKILL.md (247 more words)Show less

Guardrails

  • Never release from a dirty worktree.
  • Never release if HEAD is not exactly at origin/master.
  • Never release if the target tag already exists locally or remotely.
  • Never release if a GitHub release for the version already exists.
  • Never release if GitHub Actions for the release commit are still running, failed, or were not found.
  • Never infer the target version when a publish/tag action is about to happen. Ask the user to confirm it.
  • Always confirm the drafted release notes with the user before creating the GitHub release.
  • Use one explicit Gradle invocation for release work: ./gradlew -Pversion="<version>" :ktsearch-cli:assemble publish
  • Do not add extra local test reruns when the release commit is already pushed and GitHub Actions is green.
  • Use the diff from the previous tag to write release notes. Do not invent changes that are not present in git history.
  • Always attach the packaged native CLI tarballs and generated checksums file.
  • Give credit in the release notes when the range contains merged PRs from external contributors.

Release notes guidance

  • Start with a one-line summary of the release theme.
  • Group the diff into 3-6 concrete bullets.
  • Prefer user-visible changes, release/build changes, and packaging changes.
  • If merged PRs in the range were authored by someone other than @jillesvangurp, add a short thanks line or preserve by @author credit in the bullets.
  • End with the compare link: https://github.com/jillesvangurp/kt-search/compare/<previous>...<version>

Assets

The packaging script produces:

  • ktsearch-<version>-darwin-arm64.tar.gz
  • ktsearch-<version>-darwin-x64.tar.gz
  • ktsearch-<version>-linux-x64.tar.gz
  • checksums.txt

Each tarball contains:

  • ktsearch
  • install.sh
  • uninstall.sh
  • alias-and-completions.sh

Script

  • Consolidated release helper: scripts/release_support.sh

© jillesvangurp, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in .codex/skills/kt-search-release of jillesvangurp/kt-search.

  • SKILL.md
  • agents/openai.yaml
  • scripts/release_support.sh

Open the folder on GitHubat commit 7ff311b

Compare with similar skills

Kt Search 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.

Kt Search Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Kt Search Release this skilljillesvangurp/kt-search155—~1.2kAutomated safety check: PassMIT
CI Automationjeremylongshore/tons-of-skills-marketplace2.8k—~1.4kAutomated safety check: NotesMIT
Git GitHub Opsc5inco/compose-pokedexer143—~1.3kAutomated safety check: PassMIT
ClickUp CLI Release Processkrodak/clickup-cli123—~906Automated safety check: WarnMIT
OpenWork Release Processdifferent-ai/openwork24k—~2.3kAutomated safety check: PassCustom licence
Mole CLI Release Flowtw93/Mole70k—~2.6kAutomated safety check: PassGPL-3.0

Similar skills

  • CI Automation

    jeremylongshore/tons-of-skills-marketplace

    A skill your agent uses when running GitHub Actions locally, creating task runner recipes, generating changelogs from git history, managing GitHub PRs/issues/releases programmatically, or creating…

    2.8k GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Git GitHub Ops

    c5inco/compose-pokedexer

    Handles Pokedexer Git and GitHub workflows: inspect changes, prepare commit messages, manage branches and pushes, and create or update issues and pull requests with safe file-based inputs.

    143 GitHub stars~1.3k tokensUpdated 8 days ago
    DevelopmentAuto-check passed

  • ClickUp CLI Release Process

    krodak/clickup-cli

    Walks through releasing a new version of clickup-cli: pre-release checks, version bump, tagging, CI watch, release notes and the Homebrew update.

    123 GitHub stars~906 tokensUpdated 5 days ago
    DevOps & CloudAuto-check: warnings

  • OpenWork Release Process

    different-ai/openwork

    Cuts an OpenWork desktop release through a tag-driven GitHub Actions workflow that makes no commits, with pre-tag checks on open fix PRs and verification afterward.

    24k GitHub stars~2.3k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Mole CLI Release Flow

    tw93/Mole

    Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.

    70k GitHub stars~2.6k tokensUpdated today
    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

More from jillesvangurp/kt-search

  • Docker Compose Tests

    jillesvangurp/kt-search

    Use Gradle Compose tasks to prepare and recover local Elasticsearch/OpenSearch test infrastructure in kt-search.

    155 GitHub stars~295 tokensUpdated 3 mo ago
    Auto-check passed

Works with

Categories

Questions about Kt Search Release

What does Kt Search Release do?

A skill your agent uses when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed…. Kt Search Release is an agent skill from jillesvangurp/kt-search. Use this skill when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed, checking GitHub Actions stability, preparing release notes from diffs, or attaching CLI binaries for Homebrew-style installation.

When should I use Kt Search Release?

Kt Search Release fits situations like: the user wants to cut; create a GitHub release for kt-search; especially when the task includes version bumping; validating that commits are pushed.

How do I install Kt Search Release in Claude Code?

Run `npx skills add jillesvangurp/kt-search --skill kt-search-release -a claude-code`. Or copy the skill folder (.codex/skills/kt-search-release in jillesvangurp/kt-search) into .claude/skills/kt-search-release in your project. Claude Code loads it when a task matches its description.

How do I install Kt Search Release in Codex?

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

Can I use Kt Search 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 jillesvangurp/kt-search --skill kt-search-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/kt-search-release, .gemini/skills/kt-search-release, .github/skills/kt-search-release and .opencode/skills/kt-search-release in your project.

What does Kt Search Release need to run?

Going by SKILL.md and its folder, Kt Search Release needs a shell for the scripts in its folder and the command-line tools its instructions call (git and gh). Our summary lists: A Bash shell.

Does Kt Search 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 Kt Search 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Kt Search Release use?

Kt Search 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 Kt Search Release use?

About 1.2k tokens (SKILL.md is roughly 4.9k 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 Kt Search Release?

Skills that share tags, products or a category with Kt Search Release: CI Automation (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Git GitHub Ops (c5inco/compose-pokedexer, 143 stars), ClickUp CLI Release Process (krodak/clickup-cli, 123 stars) and OpenWork Release Process (different-ai/openwork, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Kt Search Release?

jillesvangurp (a GitHub user) maintains it in jillesvangurp/kt-search, which has 155 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on July 3, 2026.

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