Release
kellerza/sunsynk
Bump sunsynk version (major/minor/bugfix), rewrite the Unreleased changelog heading, commit, push to main, and open a draft GitHub release with a v-prefixed tag.
Prepare and publish stable or beta releases of rnovacek/homeassistantczenergyspotprices, requiring approval of the exact version and release notes before publishing.
Install Release
$ npx skills add rnovacek/homeassistant_cz_energy_spot_prices --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rnovacek/homeassistant_cz_energy_spot_prices release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rnovacek/homeassistant_cz_energy_spot_prices.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release .claude/skills/release && rm -rf skills-srcUse ~/.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/
Install the "release" agent skill from https://github.com/rnovacek/homeassistant_cz_energy_spot_prices/tree/main/.agents/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rnovacek/homeassistant_cz_energy_spot_prices/tree/main/.agents/skills/releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rnovacek/homeassistant_cz_energy_spot_prices --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rnovacek/homeassistant_cz_energy_spot_prices release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rnovacek/homeassistant_cz_energy_spot_prices.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release .agents/skills/release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release" agent skill from https://github.com/rnovacek/homeassistant_cz_energy_spot_prices/tree/main/.agents/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rnovacek/homeassistant_cz_energy_spot_prices --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rnovacek/homeassistant_cz_energy_spot_prices release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rnovacek/homeassistant_cz_energy_spot_prices.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release .cursor/skills/release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release" agent skill from https://github.com/rnovacek/homeassistant_cz_energy_spot_prices/tree/main/.agents/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rnovacek/homeassistant_cz_energy_spot_prices.git --path .agents/skills/release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rnovacek/homeassistant_cz_energy_spot_prices --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rnovacek/homeassistant_cz_energy_spot_prices release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rnovacek/homeassistant_cz_energy_spot_prices.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release .gemini/skills/release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/rnovacek/homeassistant_cz_energy_spot_prices/tree/main/.agents/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rnovacek/homeassistant_cz_energy_spot_prices releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rnovacek/homeassistant_cz_energy_spot_prices --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rnovacek/homeassistant_cz_energy_spot_prices.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release .github/skills/release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/rnovacek/homeassistant_cz_energy_spot_prices/tree/main/.agents/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rnovacek/homeassistant_cz_energy_spot_prices --skill release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rnovacek/homeassistant_cz_energy_spot_prices release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rnovacek/homeassistant_cz_energy_spot_prices.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release .opencode/skills/release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/rnovacek/homeassistant_cz_energy_spot_prices/tree/main/.agents/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release- GitHub stars
- 136
- Token cost
- ~1.1k tokens
- SKILL.md length
- 601 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Prepare and publish stable or beta releases of rnovacek/homeassistantczenergyspotprices, requiring approval of the exact version and release notes before publishing.
- Requests to make the next release
- SKILL.md covers Prepare a concrete proposal, Required user approval and Publish the approved proposal
- Calls gh
- Beta of this integration
What it does
Release is an agent skill from rnovacek/homeassistant_cz_energy_spot_prices. Prepare and publish stable or beta releases of rnovacek/homeassistantczenergyspotprices, requiring approval of the exact version and release notes before publishing. Use for requests to make the next release or beta of this integration.
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. It works with Home Assistant. The repository describes itself as: Home Assistant integration that provides current Czech electricity spot prices based on OTE. The licence is Apache-2.0.
When your agent uses it
- Requests to make the next release
- Beta of this integration
Example prompts
- “/release”
What it can do on your machine
Read from SKILL.md and the folder at commit 2318bea. 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:
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 loads about 1.1k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 601 words of instructions outside code blocks.
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 rnovacek/homeassistant_cz_energy_spot_prices at commit 2318bea, republished under its Apache-2.0 licence (© rnovacek). 601 words, ~1,136 tokens.
Download SKILL.mdSave it as
.claude/skills/release/SKILL.md (or your agent's skills folder).- name
- release
- description
- Prepare and publish stable or beta releases of rnovacek/homeassistant_cz_energy_spot_prices, requiring approval of the exact version and release notes before publishing. Use for requests to make the next release or beta of this integration.
Czech Energy Spot Prices releases
Use this workflow for rnovacek/homeassistant_cz_energy_spot_prices. Read the repository's current AGENTS.md and release workflows before acting. Keep automatic skill discovery enabled.
Prepare a concrete proposal
- Inspect the working tree, branch, remotes, tags, and existing GitHub releases. Preserve unrelated uncommitted changes and exclude them from the release. Pull
mainwith a fast-forward update; if preserving local changes requires an autostash, inspect the reapplied diff for conflicts and duplicate imports. - Determine the next version from the current manifest, fetched tags, and published releases. The integration's version belongs in
custom_components/cz_energy_spot_prices/manifest.json, not the development project'spyproject.toml. FollowX.Y.ZbNfor betas; do not hardcode a version from a previous session. - Review all changes since the previous relevant release, including merged PRs beyond the current conversation. Inspect implementation when needed to substantiate release notes. Follow the existing release convention for tag names and assets; do not invent an asset requirement.
- Prepare the manifest version change and exact release notes locally. Notes should describe user-visible changes, relevant compatibility requirements, PR references, and a full changelog link. Do not include a Validation chapter or test/check results in published notes unless the user explicitly requests them. Report checks separately in the approval message.
- Run the full test suite and the declared type checker using the project's development environment, plus diff and manifest validation. Follow
AGENTS.mdfor commands and distinguish local resolved dependencies from CI's upgraded environment. Report failures or blocked checks accurately; resolve release-related regressions before proposing publication.
Required user approval
Show the proposed version, whether it is a beta/prerelease or stable release, the intended source commit, and the complete exact release notes in the conversation. Include a concise, separate account of verification results. Ask the user to approve this version and these notes for publication, then stop and wait for their reply.
This approval gate is an explicit user preference. Link this SKILL.md and quote "Approve the exact version and release notes before publishing" when explaining the pause.
A generic request such as "do another beta" authorizes preparation, not approval of unseen notes. Shell/network permission approvals are not editorial approval. If the user edits the proposed version or notes, prepare and show the revised proposal and obtain approval for it. Do not interpret elapsed time or silence as consent.
Before this approval, do not create the release commit or tag, push release changes, or create a GitHub release (including a draft). Local preparation and validation should be complete so approval is the final user decision. Once the exact proposal is approved, proceed without asking for the same approval again; execution-permission prompts may still be required by the environment.
Show full SKILL.md (167 more words)Show less
Publish the approved proposal
- Recheck local and remote state before publishing. If the release content or proposed version must change, return to the approval gate. Do not silently include newly arrived commits.
- Commit only the approved manifest bump and any explicitly approved release files. Create the matching tag at the verified release commit. Push the branch and tag atomically where supported; do not force-push or overwrite an existing tag.
- Use the approved notes verbatim, saved in a UTF-8 file and passed via
gh release create --notes-file. Use--verify-tag. For a beta, use--prerelease --latest=false; for stable releases, follow the repository's existing stable-release convention. - If a command is interrupted or fails, inspect the local commit/tag, remote refs, and GitHub release before retrying. Continue only missing steps for the approved proposal. Stop if an existing tag or release disagrees with it; do not overwrite or delete published state automatically.
- Verify the published release version, notes, prerelease status, and tag target, then provide its URL and report any remaining issues.
© rnovacek, 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 .agents/skills/release of rnovacek/homeassistant_cz_energy_spot_prices.
Open the folder on GitHubat commit 2318bea
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release this skillrnovacek/homeassistant_cz_energy_spot_prices | 136 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Releasekellerza/sunsynk | 339 | — | ~920 | Automated safety check: Pass | Apache-2.0 | |
| Releasecdpuk/ha-bestway | 134 | — | ~998 | Automated safety check: Pass | MIT | |
| GitHub Issue Solverhomeassistant-extras/device-card | 129 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Changelog Generatorbrunosabot/streamline-card | 269 | — | ~854 | Automated safety check: Pass | MIT | |
| Releasedcb/homeassistant-claude-kit | 123 | — | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Release
cdpuk/ha-bestway
Cut a release of this integration - bump the version in manifest.json, run the validation gates, commit, tag the merged commit, and draft categorised release notes for the GitHub release form.
GitHub Issue Solver
homeassistant-extras/device-card
Accept a GitHub issue URL or issue details, create a comprehensive plan (in plan mode - shows plan first), then implement the solution including tests and documentation, create/update release notes…
Changelog Generator
brunosabot/streamline-card
Generate an engaging, human-centric, and community-focused changelog from git history.
Release
dcb/homeassistant-claude-kit
Cut a new homeassistant-claude-kit version. An agent skill from dcb/homeassistant-claude-kit.
Release Notes
gduteil/cozytouch
Write releasenotes/<version.md for a Cozytouch release — what the release means for somebody running it, in their words, with a section emoji per theme.
Related
Works with
Categories
Questions about Release
What does Release do?
Prepare and publish stable or beta releases of rnovacek/homeassistantczenergyspotprices, requiring approval of the exact version and release notes before publishing. Release is an agent skill from rnovacek/homeassistant_cz_energy_spot_prices. Prepare and publish stable or beta releases of rnovacek/homeassistantczenergyspotprices, requiring approval of the exact version and release notes before publishing.
When should I use Release?
Release fits situations like: requests to make the next release; beta of this integration.
How do I install Release in Claude Code?
Run `npx skills add rnovacek/homeassistant_cz_energy_spot_prices --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in rnovacek/homeassistant_cz_energy_spot_prices) 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 rnovacek/homeassistant_cz_energy_spot_prices --skill release -a codex`. Or copy the skill folder (.agents/skills/release in rnovacek/homeassistant_cz_energy_spot_prices) 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 rnovacek/homeassistant_cz_energy_spot_prices --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 (gh).
Does Release 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 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 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 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?
Skills that share tags, products or a category with Release: Release (kellerza/sunsynk, 339 stars), Release (cdpuk/ha-bestway, 134 stars), GitHub Issue Solver (homeassistant-extras/device-card, 129 stars) and Changelog Generator (brunosabot/streamline-card, 269 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
rnovacek (a GitHub user) maintains it in rnovacek/homeassistant_cz_energy_spot_prices, which has 136 GitHub stars. The repository was last updated on September 22, 2026.
Source: rnovacek/homeassistant_cz_energy_spot_prices on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.