A skill your agent uses when preparing HACS releases, versions, tags, or release notes.

MITAuto-check passedDevelopment

Install Release

skills CLI
$ npx skills add TimSoethout/goodwe-sems-home-assistant --skill release -a claude-code

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

GitHub CLI
$ gh skill install TimSoethout/goodwe-sems-home-assistant 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/TimSoethout/goodwe-sems-home-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/release .claude/skills/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
release
GitHub stars
147
Token cost
~411 tokens
SKILL.md length
212 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when preparing HACS releases, versions, tags, or release notes.

  • Works in 4 steps: Version: Update… → Release notes: Update RELEASE_NOTES.md… → Contributors: Credit code authors and… → …
  • Preparing HACS releases
  • Calls ruff
  • Tasks that involve Changelog and release notes

What it does

Release is an agent skill from TimSoethout/goodwe-sems-home-assistant. Use when preparing HACS releases, versions, tags, or release notes.

Its SKILL.md is about 410 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 for monitoring GoodWe SEMS+ solar inverters, batteries, smart meters, and energy data. The licence is MIT.

When your agent uses it

  • Preparing HACS releases
  • Tasks that involve Changelog and release notes

Example prompts

  • “/release”

Workflow steps

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

  1. Version: Update custom_components/sems/manifest.json. Base the next stable version on the latest stable release: patch for fixes, minor…
  2. Release notes: Update RELEASE_NOTES.md with all user-visible changes since the previous stable tag, including every beta. Keep notes…
  3. Contributors: Credit code authors and people who contributed information, testing, or troubleshooting. Verify GitHub handles; do not infer…
  4. Publish: Tag with the manifest version and publish a GitHub Release. Mark betas as prereleases; stable releases are regular releases. Copy…

What it can do on your machine

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

    • ruff

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

  • Network

    No URLs in SKILL.md.

    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 411 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 212 words of instructions outside code blocks.

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

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 TimSoethout/goodwe-sems-home-assistant at commit 72c06c7, republished under its MIT licence (© TimSoethout). 212 words, ~411 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Use when preparing HACS releases, versions, tags, or release notes.

HACS Release

  1. Version: Update custom_components/sems/manifest.json. Base the next stable version on the latest stable release: patch for fixes, minor for features, major for breaking changes. Use numbered prereleases (for example, 11.12.0-beta.1) for the intended stable version; breaking beta changes target the next major. Never reuse a published tag.
  2. Release notes: Update RELEASE_NOTES.md with all user-visible changes since the previous stable tag, including every beta. Keep notes concise; preserve existing links, add verified links when available, and never invent them. Include limitations and compatibility notes.
  3. Contributors: Credit code authors and people who contributed information, testing, or troubleshooting. Verify GitHub handles; do not infer them from email addresses.
  4. Publish: Tag with the manifest version and publish a GitHub Release. Mark betas as prereleases; stable releases are regular releases. Copy the release notes into the release description. Publishing triggers .github/workflows/release.yml to upload the ZIP; a tag alone is insufficient.

For a stable release after betas, use the same version number and preserve the full beta history in its notes. HACS users must opt into prereleases to receive betas.

Before finishing

  • Run the narrowest relevant tests; if code changed, run ruff check and ruff format --check on the touched area.
  • Confirm manifest/tag versions match, prerelease status is correct, and the ZIP uploaded.

© TimSoethout, 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 .github/skills/release of TimSoethout/goodwe-sems-home-assistant.

Open the folder on GitHubat commit 72c06c7

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.

Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skillTimSoethout/goodwe-sems-home-assistant147—~411Automated safety check: PassMIT
Releasekellerza/sunsynk339—~920Automated safety check: PassApache-2.0
Releasecdpuk/ha-bestway134—~998Automated safety check: PassMIT
GitHub Issue Solverhomeassistant-extras/device-card129—~3.4kAutomated safety check: PassMIT
Releasernovacek/homeassistant_cz_energy_spot_prices136—~1.1kAutomated safety check: PassApache-2.0
Changelog Generatorbrunosabot/streamline-card269—~854Automated safety check: PassMIT

Similar skills

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

    339 GitHub stars~920 tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • 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.

    134 GitHub stars~998 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • 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…

    129 GitHub stars~3.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Release

    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.

    136 GitHub stars~1.1k tokensUpdated 16 days ago
    DevelopmentAuto-check passed
  • Changelog Generator

    brunosabot/streamline-card

    Generate an engaging, human-centric, and community-focused changelog from git history.

    269 GitHub stars~854 tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • Release

    dcb/homeassistant-claude-kit

    Cut a new homeassistant-claude-kit version. An agent skill from dcb/homeassistant-claude-kit.

    123 GitHub stars~3.1k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

Works with

Categories

Questions about Release

What does Release do?

A skill your agent uses when preparing HACS releases, versions, tags, or release notes. Release is an agent skill from TimSoethout/goodwe-sems-home-assistant. Use when preparing HACS releases, versions, tags, or release notes.

When should I use Release?

Release fits situations like: preparing HACS releases; tasks that involve Changelog and release notes.

How do I install Release in Claude Code?

Run `npx skills add TimSoethout/goodwe-sems-home-assistant --skill release -a claude-code`. Or copy the skill folder (.github/skills/release in TimSoethout/goodwe-sems-home-assistant) 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 TimSoethout/goodwe-sems-home-assistant --skill release -a codex`. Or copy the skill folder (.github/skills/release in TimSoethout/goodwe-sems-home-assistant) 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 TimSoethout/goodwe-sems-home-assistant --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 (ruff).

Does Release access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. 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 MIT 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 411 tokens (SKILL.md is roughly 1.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 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 Release (rnovacek/homeassistant_cz_energy_spot_prices, 136 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

TimSoethout (a GitHub user) maintains it in TimSoethout/goodwe-sems-home-assistant, which has 147 GitHub stars. The repository was last updated on October 3, 2026.

Source: TimSoethout/goodwe-sems-home-assistant on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.