New: 97,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 Cut

by 4gray in 4gray/iptvnator

A skill your agent uses when preparing, cutting, tagging, publishing, or verifying an IPTVnator release or its release assets.

MITAuto-check passedDevelopment

Install Release Cut

skills CLI
$ npx skills add 4gray/iptvnator --skill release-cut -a claude-code

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

GitHub CLI
$ gh skill install 4gray/iptvnator release-cut --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/4gray/iptvnator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/release-cut .claude/skills/release-cut && 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-cut
GitHub stars
7.3k
Token cost
~929 tokens
SKILL.md length
445 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when preparing, cutting, tagging, publishing, or verifying an IPTVnator release or its release assets.

  • Works in 7 steps: Set package.json.version. → Run pnpm run release:notes:changelog. → Minor release: run pnpm run… → …
  • Verifying an IPTVnator release
  • SKILL.md covers Preflight, Generate, Push and External Effects and Failure Safety
  • Calls pnpm, git and node

What it does

Release Cut is an agent skill from 4gray/iptvnator. Use when preparing, cutting, tagging, publishing, or verifying an IPTVnator release or its release assets.

Its SKILL.md is about 930 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. It works with pnpm. The repository describes itself as: :tv: Cross-platform IPTV player application with multiple features, such as support of m3u and m3u8 playlists, favorites, TV guide, TV archive/catchup and more. The licence is MIT.

When your agent uses it

  • Verifying an IPTVnator release
  • Its release assets

Example prompts

  • “/release-cut”

Requirements

  • Docker

Workflow steps

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

  1. Set package.json.version.
  2. Run pnpm run release:notes:changelog.
  3. Minor release: run pnpm run release:notes:blog and finish every editorial
  4. Capture required manifest screenshots only against mock servers
  5. Render the announcement drafts, saving output outside the repository
  6. Render highlight cards after the screenshots
  7. Consume notes only after reviewing all generated output

What it can do on your machine

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

    • pnpm
    • git
    • node

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

  • Network

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

Release Cut loads about 929 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 445 words of instructions outside code blocks.

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

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 4gray/iptvnator at commit acb8cb0, republished under its MIT licence (© 4gray). 445 words, ~929 tokens.

Download SKILL.mdSave it as .claude/skills/release-cut/SKILL.md (or your agent's skills folder).
name
release-cut
description
Use when preparing, cutting, tagging, publishing, or verifying an IPTVnator release or its release assets.

Release Cut

Full contract, asset table and rationale: docs/architecture/release-pipeline.md.

For imagegen announcement covers, reuse the approved artwork prompt.

The tag workflow authors the public GitHub body with node tools/release/extract-changelog-section.mjs --public "${VERSION}". Keep the full changelog, including internal notes, committed before tagging.

Preflight

Work from clean, current master with the intended remote named explicitly. Confirm package.json contains bare semver, the exact v<version> tag does not exist locally or remotely, CI is green, and all notes validate.

bash
pnpm run release:notes:validate
pnpm run i18n:check

Generate

  1. Set package.json.version.
  2. Run pnpm run release:notes:changelog.
  3. Minor release: run pnpm run release:notes:blog and finish every editorial field. Patch release: edit the existing vX-Y post; do not scaffold or force-overwrite it.
  4. Capture required manifest screenshots only against mock servers: pnpm nx run electron-backend:build-e2e, then pnpm run release:screenshots.
  5. Render the announcement drafts, saving output outside the repository: pnpm --silent run release:notes:telegram and the :reddit counterpart (--silent, or pnpm's lifecycle banner lands in the saved post).
  6. Render highlight cards after the screenshots: pnpm run release:cards:generate. Review them; copy hero.jpg into the blog post's asset directory if it should ship as the hero image.
  7. Consume notes only after reviewing all generated output: node tools/release/build-release-notes.mjs --consume.

Steps 5 and 6 must precede --consume: highlight: exists only in the note files it deletes. Publishing announcements is manual, after the release.

The consume command is the destructive boundary: it deletes the direct note files. Stage only release-owned files, including exact website post/assets and git add -A -- .changes, then commit and create the exact tag.

bash
git commit -m "chore(release): v0.24.0"
git tag v0.24.0
Show full SKILL.md (195 more words)Show less

Push and External Effects

Push the named remote's master branch first, then push only the exact v<version> tag as a second command. Never use broad git push --tags. For remote upstream and version v0.25.1, run exactly:

bash
git push upstream master
git push upstream v0.25.1

Master and v* pushes can publish Docker images. The tag build creates a draft GitHub release. Run pnpm run release:verify:draft — it waits for the tag build, then checks draft status, warns on an empty authored body, and verifies the complete 27-asset set documented in docs/architecture/release-pipeline.md. It is read-only, and fails on an already-published release. Still review the authored text and generated commits by eye.

Manually publish the release; this verifies and uploads Snaps to edge. Installed-Snap smoke and candidate/stable promotion stay manual. After public-asset verification, publish the draft blog and update apps/website/released-version.json to the published version together. Follow the release pipeline's offline-download checks and verify deployment; never use the development/nightly version for this pin.

Failure Safety

Missing CHANGELOG section: regenerate, commit, delete the bad tag locally and remotely only after resolving its exact target, then retag. Never publish a draft until the source archive and Snap contract pass.

The .codex and .claude copies of this skill must remain byte-identical.

© 4gray, 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 .codex/skills/release-cut of 4gray/iptvnator.

Open the folder on GitHubat commit acb8cb0

Compare with similar skills

Release Cut 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 Cut compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Cut this skill4gray/iptvnator7.3k—~929Automated safety check: PassMIT
@pierre/diffs Code Renderingpierrecomputer/pierre6.2k2 repos~803Automated safety check: PassApache-2.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Pull Requestspnpm/pnpm37k—~2.2kAutomated safety check: PassMIT
Link Workspace Packagesnomcopter/react-mosaic4.8k5 repos~760Automated safety check: PassCustom licence
Release Notespnpm/pnpm37k—~2.8kAutomated safety check: PassMIT

Similar skills

  • @pierre/diffs Code Rendering

    pierrecomputer/pierre

    Guides an agent through using @pierre/diffs to render syntax-highlighted files and diffs, and to build editing and review surfaces in React or plain JavaScript.

    6.2k GitHub starsUsed in 2 repos~803 tokens
    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 yesterday
    DevelopmentAuto-check passed

  • Pull Requests

    pnpm/pnpm

    Take a change through a pull request in the pnpm repository — opening it, then staying with it after every push until CI is green and the review round is quiet.

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

  • Link Workspace Packages

    nomcopter/react-mosaic

    Link workspace packages in monorepos (npm, yarn, pnpm, bun).

    4.8k GitHub starsUsed in 5 repos~760 tokens
    DevelopmentAuto-check passed

  • Release Notes

    pnpm/pnpm

    Curate a pending release page - merging entries that describe one change, dropping notes for defects that never shipped, ordering by importance, and checking the version the intents ask for.

    37k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from 4gray/iptvnator

All 8 skills in this repo

  • Iptvnator Nx Architecture

    4gray/iptvnator

    A skill your agent uses when deciding where IPTVnator code belongs, creating or moving Nx projects, changing scoped aliases or tags, editing lint targets, or validating module boundaries.

    7.3k GitHub stars~828 tokensUpdated yesterday
    Auto-check passed

  • Iptvnator Sqlite DB Worker

    4gray/iptvnator

    A skill your agent uses when changing Electron SQLite IPC, database-worker operations, request-scoped progress or cancellation, worker packaging, or runtime verification of non-EPG database work.

    7.3k GitHub stars~824 tokensUpdated yesterday
    Auto-check passed

  • Release Notes

    4gray/iptvnator

    A skill your agent uses when a change may need a .changes note, the Release note gate fails, or deciding whether type: internal or no-release-note applies.

    7.3k GitHub stars~446 tokensUpdated yesterday
    Auto-check passed

  • Iptvnator Theme Style

    4gray/iptvnator

    A skill your agent uses when changing IPTVnator SCSS tokens, shared layout mixins, portal headers, sidebars, detail views, Electron drag regions, or cross-portal visual consistency.

    7.3k GitHub stars~796 tokensUpdated yesterday
    Auto-check passed

  • Iptvnator UI Design

    4gray/iptvnator

    A skill your agent uses when changing user-visible Angular UI in IPTVnator, especially channel rows or lists, EPG views, settings and playlist surfaces, selection states, shared portal components…

    7.3k GitHub stars~519 tokensUpdated yesterday
    Auto-check passed

  • Stalker Portal

    4gray/iptvnator

    A skill your agent uses when changing Stalker or Ministra routes, stores, catalog or series shapes, playback progress, favorites and recent items, EPG, or remote control.

    7.3k GitHub stars~990 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Release Cut

What does Release Cut do?

A skill your agent uses when preparing, cutting, tagging, publishing, or verifying an IPTVnator release or its release assets. Release Cut is an agent skill from 4gray/iptvnator. Use when preparing, cutting, tagging, publishing, or verifying an IPTVnator release or its release assets.

When should I use Release Cut?

Release Cut fits situations like: verifying an IPTVnator release; its release assets.

How do I install Release Cut in Claude Code?

Run `npx skills add 4gray/iptvnator --skill release-cut -a claude-code`. Or copy the skill folder (.codex/skills/release-cut in 4gray/iptvnator) into .claude/skills/release-cut in your project. Claude Code loads it when a task matches its description.

How do I install Release Cut in Codex?

Run `npx skills add 4gray/iptvnator --skill release-cut -a codex`. Or copy the skill folder (.codex/skills/release-cut in 4gray/iptvnator) into .agents/skills/release-cut in your project. Codex loads it when a task matches its description.

Can I use Release Cut 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 4gray/iptvnator --skill release-cut -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-cut, .gemini/skills/release-cut, .github/skills/release-cut and .opencode/skills/release-cut in your project.

What does Release Cut need to run?

Going by SKILL.md and its folder, Release Cut needs the command-line tools its instructions call (pnpm, git and node). Our summary lists: Docker.

Does Release Cut 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 Release Cut 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 Cut use?

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

About 929 tokens (SKILL.md is roughly 3.7k 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 Cut?

Skills that share tags, products or a category with Release Cut: @pierre/diffs Code Rendering (pierrecomputer/pierre, 6.2k stars), React Router Release Notes Prep (remix-run/react-router, 57k stars), Pull Requests (pnpm/pnpm, 37k stars) and Link Workspace Packages (nomcopter/react-mosaic, 4.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Cut?

4gray (a GitHub user) maintains it in 4gray/iptvnator, which has 7,292 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 6, 2026.

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