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

Openseo Release Notes

by VladSez in VladSez/easy-invoice-pdf

Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR.

AGPL-3.0Auto-check passedDevelopment

Install Openseo Release Notes

skills CLI
$ npx skills add VladSez/easy-invoice-pdf --skill openseo-release-notes -a claude-code

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

GitHub CLI
$ gh skill install VladSez/easy-invoice-pdf openseo-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/VladSez/easy-invoice-pdf.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/openseo-release-notes .claude/skills/openseo-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
openseo-release-notes
GitHub stars
1.1k
Used in
1 other repo
Token cost
~1.8k tokens
SKILL.md length
987 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR.

  • Works in 5 steps: Bump the version → Collect the changes since the last release → Draft the notes → …
  • The user asks to prepare a release
  • SKILL.md covers 1. Bump the version, 2. Collect the changes since…, 3. Draft the notes and 4. Review and verify, plus 1 more section
  • Calls git, gh and pnpm; reaches github.com; needs OPENROUTER_API_KEY

What it does

Openseo Release Notes is an agent skill from VladSez/easy-invoice-pdf. Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.

Its SKILL.md is about 1.8k 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 Forms and invoices. It works with Git and React. The repository describes itself as: Free & Open-Source Invoice Generator - No Sign-Up, No Ads, Instant PDF Export, 100% In-Browser, and Fully Customizable Templates. ⭐ Star the repo if you like it. The licence is AGPL-3.0.

When your agent uses it

  • The user asks to prepare a release
  • Bump the version
  • Write release notes

Example prompts

  • “release: vX.X.X”
  • “/openseo-release-notes”

Requirements

  • A credential in OPENROUTER_API_KEY

Workflow steps

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

  1. Bump the version
  2. Collect the changes since the last release
  3. Draft the notes
  4. Review and verify
  5. Open the PR

What it can do on your machine

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

    • git
    • gh
    • pnpm

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OPENROUTER_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Openseo Release Notes loads about 1.8k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 987 words of instructions outside code blocks.

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

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 VladSez/easy-invoice-pdf at commit ba85869, republished under its AGPL-3.0 licence (© VladSez). 987 words, ~1,845 tokens.

Download SKILL.mdSave it as .claude/skills/openseo-release-notes/SKILL.md (or your agent's skills folder).
name
openseo-release-notes
description
Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.

OpenSEO release notes

Cut a release for this repo end to end. The deliverables are a version bump in package.json, a new release-notes/v<version>.md, and a PR against origin/main titled release: v<version>.

1. Bump the version

  • Read package.json. If the branch has already bumped version, treat that as the source of truth and do not change it.
  • Otherwise bump the patch version (e.g. 0.0.19 → 0.0.20). Only bump minor/major if explicitly asked.

2. Collect the changes since the last release

  • Find the latest tag: git tag --sort=-creatordate | head -1. Verify the branch is up to date with origin/main (git fetch origin main && git log HEAD..origin/main --oneline should be empty; flag it if not).
  • List commits: git log <last-tag>..HEAD --oneline. You can also run pnpm release:notes for a raw commit inventory — use it only as a checklist of candidate changes, never as the draft's structure (its Improved/Changed/Docs sections must not appear in the notes).
  • For each commit, fetch the PR body and author (gh pr view <num> --repo <repo> --json title,body,author) — squash-commit subjects can be stale. The (#NN) in commit subjects can reference either repo: try bensenescu/open-seo (origin) first and fall back to every-app/open-seo (public) — outside contributors' PRs and their handles live on the public repo. Commits with no (#NN) may still be an outside contribution with a public PR (gh pr list --repo every-app/open-seo --state merged --author <login>); check git log --format=%an for the author. Verify claims against the final code when a PR body and commit subject disagree (features get reverted before merge).
  • Record the PR author's GitHub handle alongside each change so the bullet can credit them.

3. Draft the notes

Write release-notes/v<version>.md. release-notes/v0.0.24.md is the canonical style exemplar — match it (v0.0.25 and later follow the same style); v0.0.23 and earlier are the old verbose style, never imitate them. The notes are a scannable digest, not documentation: the whole file fits on one screen (roughly 15 lines including headings), and every line earns its place.

Format:

  • Top line: a fragment naming the release's 2–3 highlights ("GSC UI, improved app layout and beta in app agent."). Not a "This release brings…" sentence.
  • Sections: ## What's new and ## Fixed only. There is no "Improved" section — an improvement is either headline-worthy (What's new) or it's cut.
  • What's new bullets name the feature; they don't sell it. One short line each ("Redesigned the app layout", "Get GSC Insights inside the app") — no em-dash feature tours, no "so you can…" benefit copy, no lists of everything the feature touches. If the name alone is ambiguous, one clause of plain-words context is the maximum.
  • At most one sub-bullet per feature, one short line: the single most useful detail, a requirement ("Requires OPENROUTER_API_KEY"), or an expectation-setter.
  • Label rough features "(Beta)" and set expectations honestly, including pointing at the better alternative for now. The expectation-setter rides the top-level line after a dash ("(Beta) In app agent - MCP is still recommended, but we'll be working to improve this during the summer."), keeping the sub-bullet slot free for a requirement or detail.
  • Fixed: 3–5 bullets, one plain sentence each, only bugs a user plausibly hit and would recognize ("Claude answers in AI search work again."). No error codes, status codes, schema/infra vocabulary, or mechanism. If more than four qualify, keep the ones hit in core flows (searches, audits, tracking, MCP answers) and drop fixes for recovering self-inflicted state (re-adding, un-archiving, refreshing) first.
  • Credit the contributor. End the bullet with — thanks @handle for outside contributors only — never for the maintainer's own PRs (bensenescu). Credit goes on the top-level bullet, not sub-bullets. Multiple contributors: — thanks @a, @b.
  • End with: Full Changelog: https://github.com/every-app/open-seo/compare/v<prev>...v<version>
Show full SKILL.md (399 more words)Show less

Curation — this is where the work is. Cut aggressively; the Full Changelog link covers the long tail:

  • Only changes to the product itself — the app, the MCP tools, the SEO data/features someone running OpenSEO actually uses. Litmus test per bullet: would a self-hoster notice this while using the product? Caring in the abstract (a new backend option, a raised cap) is not enough.
  • Do NOT mention:
    • Marketing-website (web/) changes — landing pages, copy, positioning, blog.
    • Pricing / plans / subscription / billing — paywalls, free-trial/plan changes, Autumn config. Hosted-commercial concerns, irrelevant to self-hosters.
    • Onboarding-flow-only changes — signup/onboarding chat, profiling steps, upgrade rails, email-verification UX. Not a product capability, even when sizable.
    • Hosted-app internals & meta — analytics, specs/ADRs, CI, refactors, dependency bumps.
    • Invisible-to-the-user work, even when product-relevant — security hardening, raised caps/limits, stability/memory/perf fixes, database/backend options and migrations. A user reading the notes should recognize every line from using the product; if they'd only notice it in a config file or an incident that no longer happens, cut it.
  • When torn between including and cutting, cut. A 4-bullet What's new that gets read beats a 10-bullet one that doesn't.
  • Never invent features — every claim must trace to a commit.
  • Numbers in bullets are usually selling — cut them; if one is genuinely load-bearing, quote the conservative, typical figure, never a cherry-picked best case.

4. Review and verify

  1. Spawn a reviewer subagent with: the draft, the guidelines above, the per-commit facts you gathered, and repo access. It returns numbered review comments citing which guideline each violates. Its charge includes verbosity: flag any bullet that sells instead of names, any second sub-bullet, any Fixed bullet with mechanism vocabulary, and anything that pushes the file past one screen.
  2. For each substantive comment, spawn a verification subagent (in parallel) that adversarially checks the comment against the actual commits/code and verdicts APPLY / APPLY-MODIFIED / REJECT.
  3. Apply only verified comments.

5. Open the PR

  • Commit the version bump, release notes, and any skill changes on a branch named claude/v<version> (use the current branch if it already follows this pattern).

  • Push to origin and open a PR against main titled exactly release: v<version>. PR body: the release notes content.

  • Do not tag or publish the GitHub release — that happens after merge. After merge, run pnpm release:publish. It reads the version from package.json and publishes the matching release-notes/v<version>.md to every-app/open-seo.

  • The equivalent command is:

    sh
    gh release create v<version> \
  --repo every-app/open-seo \
  --title v<version> \
  --notes-file release-notes/v<version>.md

© VladSez, AGPL-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

Just SKILL.md in .agents/skills/openseo-release-notes of VladSez/easy-invoice-pdf.

Open the folder on GitHubat commit ba85869

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in VladSez/easy-invoice-pdf, which our catalogue first saw on October 7, 2026.

Compare with similar skills

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

Openseo Release Notes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Openseo Release Notes this skillVladSez/easy-invoice-pdf1.1k1 repos~1.8kAutomated safety check: PassAGPL-3.0
Gh Release Notesreact-cosmos/react-cosmos8.7k—~335Automated safety check: PassMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
Mole Release Notes Publishertw93/Mole70k—~1.9kAutomated safety check: PassGPL-3.0
Generate Release Notesteambit/bit18k—~2.2kAutomated safety check: PassCustom licence

Similar skills

  • Gh Release Notes

    react-cosmos/react-cosmos

    Generate a clean list of commits between two git tags for GitHub release notes.

    8.7k GitHub stars~335 tokensUpdated 17 days ago
    DevelopmentAuto-check passed

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

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

  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Mole Release Notes Publisher

    tw93/Mole

    Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Generate Release Notes

    teambit/bit

    Generate comprehensive release notes for Bit from git commits and pull requests.

    18k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • 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 3 days ago
    DevelopmentAuto-check passed

More from VladSez/easy-invoice-pdf

All 8 skills in this repo

  • Changelog Maintenance

    VladSez/easy-invoice-pdf

    Maintain a clear and informative changelog for software releases.

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

  • Trigger Authoring Chat Agent

    VladSez/easy-invoice-pdf

    Author and run a durable AI chat agent with chat.agent from @trigger.dev/sdk/ai: the per-turn run loop, why you MUST spread ...chat.toStreamTextOptions() first, returning a StreamTextResult vs…

    1.1k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Trigger Getting Started

    VladSez/easy-invoice-pdf

    Bootstrap Trigger.dev into an existing project from scratch: authenticate the CLI, install @trigger.dev/sdk and @trigger.dev/build, write trigger.config.ts with the project ref and task dirs…

    1.1k GitHub stars~2k tokensUpdated today
    Auto-check: notes

  • Better UI

    VladSez/easy-invoice-pdf

    Polishes and improves the UI in your project. An agent skill from VladSez/easy-invoice-pdf.

    1.1k GitHub starsUsed in 5 repos~1.9k tokens
    Auto-check passed

  • Merge Ready

    VladSez/easy-invoice-pdf

    Take a branch from "code exists (or is about to)" to "ready for Ben's final review" — multi-axis subagent review with verified findings, fixes, ci:check, checkpoint commits, and an updated PR.

    1.1k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Trigger Authoring Tasks

    VladSez/easy-invoice-pdf

    Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run…

    1.1k GitHub stars~1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Openseo Release Notes

What does Openseo Release Notes do?

Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Openseo Release Notes is an agent skill from VladSez/easy-invoice-pdf.X" PR.

When should I use Openseo Release Notes?

Openseo Release Notes fits situations like: the user asks to prepare a release; bump the version; write release notes.

How do I install Openseo Release Notes in Claude Code?

Run `npx skills add VladSez/easy-invoice-pdf --skill openseo-release-notes -a claude-code`. Or copy the skill folder (.agents/skills/openseo-release-notes in VladSez/easy-invoice-pdf) into .claude/skills/openseo-release-notes in your project. Claude Code loads it when a task matches its description.

How do I install Openseo Release Notes in Codex?

Run `npx skills add VladSez/easy-invoice-pdf --skill openseo-release-notes -a codex`. Or copy the skill folder (.agents/skills/openseo-release-notes in VladSez/easy-invoice-pdf) into .agents/skills/openseo-release-notes in your project. Codex loads it when a task matches its description.

Can I use Openseo 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 VladSez/easy-invoice-pdf --skill openseo-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/openseo-release-notes, .gemini/skills/openseo-release-notes, .github/skills/openseo-release-notes and .opencode/skills/openseo-release-notes in your project.

What does Openseo Release Notes need to run?

Going by SKILL.md and its folder, Openseo Release Notes needs the command-line tools its instructions call (git, gh and pnpm) and credentials named OPENROUTER_API_KEY. Our summary lists: A credential in OPENROUTER_API_KEY.

Does Openseo Release Notes access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

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

Openseo Release Notes is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Openseo Release Notes use?

About 1.8k tokens (SKILL.md is roughly 7.4k 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 Openseo Release Notes?

Skills that share tags, products or a category with Openseo Release Notes: Gh Release Notes (react-cosmos/react-cosmos, 8.7k stars), React Router Release Notes Prep (remix-run/react-router, 57k stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Mole Release Notes Publisher (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Openseo Release Notes?

VladSez (a GitHub user) maintains it in VladSez/easy-invoice-pdf, which has 1,106 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 9, 2026.

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