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 Notes

by boundless-xyz in boundless-xyz/boundless

Internal — for Boundless team members only. An agent skill from boundless-xyz/boundless.

Apache-2.0Auto-check: notesDevelopment

Install Release Notes

skills CLI
$ npx skills add boundless-xyz/boundless --skill release-notes -a claude-code

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

GitHub CLI
$ gh skill install boundless-xyz/boundless release-notes --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/boundless-xyz/boundless.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ops-release-notes .claude/skills/release-notes && 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-notes
GitHub stars
193
Token cost
~1.1k tokens
SKILL.md length
582 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

Internal — for Boundless team members only. An agent skill from boundless-xyz/boundless.

  • Works in 4 steps: Gather inputs → Research → Write the notes → …
  • The user wants to write release notes
  • SKILL.md covers Process and References
  • Calls just and gh

What it does

Release Notes is an agent skill from boundless-xyz/boundless. Internal — for Boundless team members only. Generate release notes for a new Boundless version. Fetches PR details, explores code changes, and produces prover-facing documentation with config examples, migration guides, and worked examples. Use when the user wants to write release notes, changelog entries, or upgrade guides.

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 Development, covering Changelog and release notes and Code migrations. The repository describes itself as: Monorepo for Boundless, the universal ZK protocol. The licence is Apache-2.0.

When your agent uses it

  • The user wants to write release notes
  • Changelog entries

Example prompts

  • “/release-notes”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Gather inputs
  2. Research
  3. Write the notes
  4. Iterate

What it can do on your machine

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

    • just
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use 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 Notes loads about 1.1k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 582 words of instructions outside code blocks.

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

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:60
    to pass them via `BROKER_EXTRA_ARGS` in `.env` (since most provers use `just prover up`) AND as direct CLI flags

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 boundless-xyz/boundless at commit 93e971a, republished under its Apache-2.0 licence (© boundless-xyz). 582 words, ~1,136 tokens.

Download SKILL.mdSave it as .claude/skills/release-notes/SKILL.md (or your agent's skills folder).
name
release-notes
description
Internal — for Boundless team members only. Generate release notes for a new Boundless version. Fetches PR details, explores code changes, and produces prover-facing documentation with config examples, migration guides, and worked examples. Use when the user wants to write release notes, changelog entries, or upgrade guides.

Release Notes Generator

Generate release notes for a new Boundless release. The audience for broker changes is prover operators -- people running the broker who need to understand what changed, how to configure it, and how to migrate.

Process

Step 1: Gather inputs

Ask the user for:

  1. Version number for this release
  2. Previous release tag to compare against (e.g., v1.2.2)
  3. Key PRs or features to highlight -- the user will tell you which PRs or topics matter. Don't try to cover every commit.
  4. Current market context if relevant (e.g., current pricing in USD/Bcycle, token prices) for realistic examples
Step 2: Research

For each feature the user wants covered:

  1. Fetch PR details with gh pr view <number> --repo boundless-xyz/boundless --json title,body
  2. Read the actual code to understand how the feature works -- don't rely solely on PR descriptions
  3. Read config structs, default values, and broker.toml template to get accurate config examples
  4. Check compose.yml for env var support and justfile for how provers actually run things (just prover up)

Use subagents to research multiple PRs in parallel.

Step 3: Write the notes

Follow these principles:

Structure
  • Start with a brief overview paragraph summarizing all highlighted features in one sentence
  • Include a full changelog link: [vOLD...vNEW](https://github.com/boundless-xyz/boundless/compare/vOLD...vNEW)
  • Each feature gets its own section with: what changed (1-3 sentences on the change, new paragraph, then 1-3 sentences on why it matters), how to use it (how to enable with examples)
  • End with an "Upgrade Notes" section summarizing action items
Writing style
  • Write for prover operators, not developers. Focus on config changes, CLI flags, and operational impact.
  • Lead with what the user needs to do, not how the code works internally
  • Be direct and concise. No filler, no marketing language.
  • Use "the broker" not "we" or "the system"
  • Don't use emojis
Config examples
  • Show the recommended/minimal config first, not the full config with all options
  • Use realistic values based on current market rates (ask the user if unsure)
  • For broker.toml changes, always show the TOML syntax exactly as it would appear in the file. Show before + after if relevant.
  • For CLI flags, show how to pass them via BROKER_EXTRA_ARGS in .env (since most provers use just prover up) AND as direct CLI flags
  • For env vars, show the export syntax
Show full SKILL.md (203 more words)Show less
Migration guides
  • Show a clear before/after comparison with labeled TOML blocks
  • Call out which fields are removed, renamed, or have new defaults
  • Always note backward compatibility -- existing configs should work without changes unless there's a breaking change
Worked examples
  • Use real order data where possible. Ask the user for a reference order from the explorer if they don't provide one.
  • Convert all comparisons to USD when demonstrating USD-based features
  • Show the math step by step so operators can verify their own config
Features to watch for

When researching broker changes, pay attention to:

  • Pricing: min_mcycle_price, collateral pricing, pricing overrides in crates/boundless-market/src/prover_utils/config.rs
  • Config: broker.toml template at broker-template.toml, MarketConfig struct
  • RPC/monitoring: chain monitors, gas estimation in crates/broker/src/
  • CLI flags: Args struct in crates/broker/src/lib.rs, check for BROKER_EXTRA_ARGS support in compose.yml
  • Telemetry: crates/broker/src/telemetry.rs
  • Hot-reload: note when config changes take effect without restart
Step 4: Iterate

The user will review and give feedback. Common adjustments:

  • Reordering sections to lead with the most impactful change
  • Adjusting example values to match current market conditions
  • Adding or removing detail from specific sections
  • Changing the framing of a feature (e.g., "show the simplification, not the mechanism")

References

Use v1.4.0 release from https://github.com/boundless-xyz/boundless/releases as a reference for tone, structure, and level of detail.

© boundless-xyz, 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/ops-release-notes of boundless-xyz/boundless.

Open the folder on GitHubat commit 93e971a

Compare with similar skills

Release Notes 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 Notes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Notes this skillboundless-xyz/boundless193—~1.1kAutomated safety check: NotesApache-2.0
Deprecate R Functions and Argumentstidyverse/dplyr5.1k1 repos~1.2kAutomated safety check: PassCustom licence
Releasing Php Packageyansongda/pay5.4k—~1.6kAutomated safety check: PassMIT
Releasejaemk/self_update961—~2.2kAutomated safety check: PassMIT
Releasejaemk/cached2.1k—~2.8kAutomated safety check: PassMIT
Mariadb Operator Release Notesmariadb-operator/mariadb-operator1k—~3.3kAutomated safety check: PassApache-2.0

Similar skills

  • Deprecate R Functions and Arguments

    tidyverse/dplyr

    Walks through deprecating an R function or argument in a package: lifecycle warning, silenced tests, a new snapshot test, documentation badge and NEWS entry.

    5.1k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed

  • Releasing Php Package

    yansongda/pay

    A skill your agent uses when preparing to publish a new version of a PHP Composer package and need to write or update CHANGELOG, upgrade guides, and documentation before tagging and releasing

    5.4k GitHub stars~1.6k tokensUpdated 10 days ago
    DevelopmentAuto-check passed

  • Release

    jaemk/self_update

    Prepare a release (bump the crate version, update CHANGELOG.md with a migration guide for breaking changes, regenerate README, commit), or run a pre-release review.

    961 GitHub stars~2.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Release

    jaemk/cached

    Prepare a release (bump versions across all Cargo.toml files, update CHANGELOG.md, refresh the migration guide, regenerate README, commit), or run a pre-release review.

    2.1k GitHub stars~2.8k tokensUpdated 7 days ago
    DevelopmentAuto-check passed

  • Mariadb Operator Release Notes

    mariadb-operator/mariadb-operator

    Create the release notes and upgrade guide for a mariadb-operator release.

    1k GitHub stars~3.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Skia Analyst

    mono/SkiaSharp

    Analyze Skia features for SkiaSharp - produces a unified analysis of what shipped (upstream engine benefits, PR links, migration guides) and what's missing (impact/priority/effort scoring, hidden…

    5.6k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

More from boundless-xyz/boundless

All 12 skills in this repo

  • Boundless CLI

    boundless-xyz/boundless

    How to use the Boundless CLI — the primary interface for the Boundless ZK proof marketplace.

    193 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed

  • Ops Indexer Query

    boundless-xyz/boundless

    Internal — for Boundless team members only. An agent skill from boundless-xyz/boundless.

    193 GitHub stars~3.5k tokensUpdated 1 mo ago
    Auto-check passed

  • Ops Query

    boundless-xyz/boundless

    Internal — for Boundless team members only. An agent skill from boundless-xyz/boundless.

    193 GitHub stars~3.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Localnet

    boundless-xyz/boundless

    Start and interact with the Boundless localnet (docker compose-based local development network).

    193 GitHub stars~1.8k tokensUpdated 1 mo ago
    Auto-check: notes

  • Ops Add New Chain

    boundless-xyz/boundless

    Internal — for Boundless team members only. An agent skill from boundless-xyz/boundless.

    193 GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Ops Check Balances

    boundless-xyz/boundless

    Internal — for Boundless team members only. An agent skill from boundless-xyz/boundless.

    193 GitHub stars~4.9k tokensUpdated 1 mo ago
    Auto-check: notes

Categories

Questions about Release Notes

What does Release Notes do?

Internal — for Boundless team members only. An agent skill from boundless-xyz/boundless. Release Notes is an agent skill from boundless-xyz/boundless. Internal — for Boundless team members only.

When should I use Release Notes?

Release Notes fits situations like: the user wants to write release notes; changelog entries.

How do I install Release Notes in Claude Code?

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

How do I install Release Notes in Codex?

Run `npx skills add boundless-xyz/boundless --skill release-notes -a codex`. Or copy the skill folder (.claude/skills/ops-release-notes in boundless-xyz/boundless) into .agents/skills/release-notes in your project. Codex loads it when a task matches its description.

Can I use Release Notes 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 boundless-xyz/boundless --skill release-notes -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-notes, .gemini/skills/release-notes, .github/skills/release-notes and .opencode/skills/release-notes in your project.

What does Release Notes need to run?

Going by SKILL.md and its folder, Release Notes needs the command-line tools its instructions call (just and gh).

Does Release Notes access the network?

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

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

Release Notes 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 Notes use?

About 1.1k tokens (SKILL.md is roughly 4.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 Notes?

Skills that share tags, products or a category with Release Notes: Deprecate R Functions and Arguments (tidyverse/dplyr, 5.1k stars), Releasing Php Package (yansongda/pay, 5.4k stars), Release (jaemk/self_update, 961 stars) and Release (jaemk/cached, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Notes?

boundless-xyz (a GitHub organization) maintains it in boundless-xyz/boundless, which has 193 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 26, 2026.

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