Agent skill

Keen Pbr Release Post

by maksimkurb in maksimkurb/keen-pbr

Draft keen-pbr release posts for GitHub and Telegram from git history.

GPL-3.0Auto-check passedDevelopment

Install Keen Pbr Release Post

skills CLI
$ npx skills add maksimkurb/keen-pbr --skill keen-pbr-release-post -a claude-code

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

GitHub CLI
$ gh skill install maksimkurb/keen-pbr keen-pbr-release-post --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/maksimkurb/keen-pbr.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/keen-pbr-release-post .claude/skills/keen-pbr-release-post && 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
keen-pbr-release-post
GitHub stars
141
Token cost
~844 tokens
SKILL.md length
375 words
Files
4 (incl. scripts, references)
Skills in repo
2
Repo updated
First seen
Licence
GPL-3.0

At a glance

Draft keen-pbr release posts for GitHub and Telegram from git history.

  • Works in 5 steps: Confirm you are in the keen-pbr… → Collect release context. → Analyze commits and touched files… → …
  • Asked to create
  • SKILL.md covers Overview, Workflow and Output Rules
  • Runs Shell scripts from its folder; calls git

What it does

Keen Pbr Release Post is an agent skill from maksimkurb/keen-pbr. Draft keen-pbr release posts for GitHub and Telegram from git history. Use when asked to create or prepare keen-pbr release notes, GitHub release text, Telegram release announcements, changelog summaries, or when the user mentions keenpbrreleasepost. The skill analyzes commits and touched files since the latest semver release tag, asks for approval of the change list, then drafts English GitHub notes and a Russian Telegram post. It drafts only and never publishes.

Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/release-style.md` and `scripts/collect_release_context.sh`).

It sits in Development, covering Changelog and release notes and Git workflow. It works with GitHub, Telegram and Git. The repository describes itself as: keen-pbr is a Policy Based Routing toolkit for Keenetic and OpenWRT routers / Инструменты для выборочной маршрутизации на роутерах Keenetic и OpenWRT. The licence is GPL-3.0.

When your agent uses it

  • Asked to create
  • Prepare keen-pbr release notes
  • GitHub release text
  • Telegram release announcements

Example prompts

  • “/keen-pbr-release-post”

Requirements

  • A Bash shell

Workflow steps

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

  1. Confirm you are in the keen-pbr repository.
  2. Collect release context.
  3. Analyze commits and touched files together.
  4. Produce an approval checkpoint before writing posts.
  5. After approval or edits, draft both posts.

What it can do on your machine

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

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

  • Network

    No URLs in SKILL.md. Its commands use git, 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

Keen Pbr Release Post loads about 844 tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 123 tokens; SKILL.md has 375 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~123
When it runs · the whole SKILL.md, loaded when a task matches
~844
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.5k

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 maksimkurb/keen-pbr at commit 4b0a09b, republished under its GPL-3.0 licence (© maksimkurb). 375 words, ~844 tokens.

Download SKILL.mdSave it as .claude/skills/keen-pbr-release-post/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
keen-pbr-release-post
description
Draft keen-pbr release posts for GitHub and Telegram from git history. Use when asked to create or prepare keen-pbr release notes, GitHub release text, Telegram release announcements, changelog summaries, or when the user mentions keen_pbr_release_post. The skill analyzes commits and touched files since the latest semver release tag, asks for approval of the change list, then drafts English GitHub notes and a Russian Telegram post. It drafts only and never publishes.

Keen PBR Release Post

Overview

Use this skill to prepare release-post drafts for the keen-pbr project from local git history. Always separate analysis from writing: first propose a change list for user approval, then draft the GitHub and Telegram posts only after the user approves or edits that list.

Workflow

  1. Confirm you are in the keen-pbr repository.

    • Prefer the current workspace if it contains .git and project files.
    • If unclear, inspect git remote -v, git status --short, and nearby files before asking the user.
  2. Collect release context.

    • Prefer scripts/collect_release_context.sh from this skill:
      sh
      /path/to/keen-pbr-release-post/scripts/collect_release_context.sh
    • If not using the script, run equivalent read-only commands:
      sh
      git describe --tags --abbrev=0 --match 'v[0-9]*.[0-9]*.[0-9]*' HEAD
      git rev-parse --short HEAD
      git log --oneline <base-tag>..HEAD
      git diff --name-status <base-tag>..HEAD
    • Treat the base tag as the latest reachable vX.Y.Z semver tag. Ignore non-release tags such as continuous.
  3. Analyze commits and touched files together.

    • Use commit names for intent, but verify scope from changed paths.
    • Group changes by product area:
      • Core
      • Web UI
      • OpenWrt & Repository
      • Keenetic OS
      • Documentation
      • CI/Build
      • Packaging
    • Merge noisy fixups and repeated CI attempts into one user-facing change.
    • Prefer user impact over implementation trivia. Mention internal details only when they explain a bug, migration, compatibility change, or risk.
  4. Produce an approval checkpoint before writing posts.

    • Output only:
      • detected range and target version if known,
      • grouped proposed change list,
      • unclear items or suggested omissions.
    • Ask the user to approve or edit the list.
    • Do not draft GitHub or Telegram posts yet.
  5. After approval or edits, draft both posts.

    • Read references/release-style.md before drafting.
    • GitHub post: English Markdown, concise sections, grouped bullets, full changelog compare link.
    • Telegram post: Russian announcement style, version header, numbered highlights, relevant warnings and upgrade notes, docs links, full changelog link.
    • Preserve user-approved facts. Do not invent release blockers, breaking changes, warnings, or metrics.
Show full SKILL.md (70 more words)Show less

Output Rules

  • Never publish to GitHub, Telegram, or any external service.
  • Never create release tags or commits.
  • Do not edit repository files while using this skill unless the user separately asks to save drafts.
  • If the target release version is not obvious from commits or project files, ask the user for it before final drafting.
  • If there are no meaningful user-facing changes, say so and suggest omitting the release announcement.

© maksimkurb, GPL-3.0. 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 3 other files (scripts, references) in .agents/skills/keen-pbr-release-post of maksimkurb/keen-pbr.

  • SKILL.md
  • agents/openai.yaml
  • references/release-style.md
  • scripts/collect_release_context.sh

Open the folder on GitHubat commit 4b0a09b

Compare with similar skills

Keen Pbr Release Post 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.

Keen Pbr Release Post compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Keen Pbr Release Post this skillmaksimkurb/keen-pbr141—~844Automated safety check: PassGPL-3.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Go-Redis Release Preparationredis/go-redis22k—~1.1kAutomated safety check: PassBSD-2-Clause
Hunk Release Workflowmodem-dev/hunk9.6k—~3.8kAutomated safety check: PassMIT
Worktrunk Release Workflowmax-sixty/worktrunk9.2k—~7.5kAutomated safety check: PassCustom licence
pybind11 Release Publicationpybind/pybind1118k—~2.5kAutomated safety check: PassCustom licence

Similar skills

  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • Official

    Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.

    22k GitHub stars~1.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • 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 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
  • Walks a maintainer through publishing a pybind11 release after the preparation PR merges, with preflight checks, confirmations before each push and a GitHub release.

    18k GitHub stars~2.5k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Obot Release Notes Drafter

    obot-platform/obot

    Drafts release notes for an upcoming Obot minor release and saves them as an unpublished GitHub draft release, never tagging or publishing.

    1.1k GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-check passed

More from maksimkurb/keen-pbr

  • Keen Pbr Symbolize Crash

    maksimkurb/keen-pbr

    Diagnose Keen PBR native crashes from KPBR-CRASH v1 or legacy raw logs.

    141 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Keen Pbr Release Post

What does Keen Pbr Release Post do?

Draft keen-pbr release posts for GitHub and Telegram from git history. Keen Pbr Release Post is an agent skill from maksimkurb/keen-pbr. Draft keen-pbr release posts for GitHub and Telegram from git history.

When should I use Keen Pbr Release Post?

Keen Pbr Release Post fits situations like: asked to create; prepare keen-pbr release notes; GitHub release text; telegram release announcements.

How do I install Keen Pbr Release Post in Claude Code?

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

How do I install Keen Pbr Release Post in Codex?

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

Can I use Keen Pbr Release Post 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 maksimkurb/keen-pbr --skill keen-pbr-release-post -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/keen-pbr-release-post, .gemini/skills/keen-pbr-release-post, .github/skills/keen-pbr-release-post and .opencode/skills/keen-pbr-release-post in your project.

What does Keen Pbr Release Post need to run?

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

Does Keen Pbr Release Post access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Keen Pbr Release Post 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 Keen Pbr Release Post use?

Keen Pbr Release Post is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Keen Pbr Release Post use?

About 844 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 663 tokens, read only when the agent opens those files.

What are the alternatives to Keen Pbr Release Post?

Skills that share tags, products or a category with Keen Pbr Release Post: Release Bump (jamiepine/voicebox, 57k stars), Go-Redis Release Preparation (redis/go-redis, 22k stars), Hunk Release Workflow (modem-dev/hunk, 9.6k stars) and Worktrunk Release Workflow (max-sixty/worktrunk, 9.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Keen Pbr Release Post?

maksimkurb (a GitHub user) maintains it in maksimkurb/keen-pbr, which has 141 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.

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