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

Tabler Release Notes Intro

by tabler in tabler/tabler

Writes the hand-written intro for a Tabler GitHub release, built from changesets, docs pages and upgrade guides in a fixed layout with a picture per headline feature.

MITAuto-check passedDevelopment

Install Tabler Release Notes Intro

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

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

GitHub CLI
$ gh skill install tabler/tabler 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/tabler/tabler.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/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
42k
Token cost
~1.8k tokens
SKILL.md length
874 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Writes the hand-written intro for a Tabler GitHub release, built from changesets, docs pages and upgrade guides in a fixed layout with a picture per headline feature.

  • Works in 6 steps: Collect the facts → Layout → Images → …
  • Writing the intro for an upcoming minor release of Tabler
  • SKILL.md covers 1. Collect the facts, 2. Layout, 3. Images and 4. Tone, plus 2 more sections
  • Calls pnpm, git and gh; reaches docs.tabler.io

What it does

A Tabler release body has two parts: an intro kept in a release-notes folder under `.github`, in a file named for the version, and generated Core, Demo and Docs lists produced by `pnpm run release-notes` from the changelogs. The skill covers only the intro and says never to write or repeat the generated lists. Minor releases always get an intro, patch releases only when users need to hear something, and the file has to be on `dev` before the version-update PR is merged because the workflow reads it from the published commit.

The agent never writes from memory. It reads every changeset file, treating minor entries for `@tabler/core` as headline candidates, checks the GitHub milestone for closed PRs without a changeset, reads the docs page of each headline feature and the version's upgrade guide, and checks every class name, attribute, event or number against current source. The layout is copied from the newest intro: a light and dark cover, one summary paragraph, a `##` section with a picture for each headline feature, then the smaller changes. The excerpt stops before the image rules and tone guidance.

When your agent uses it

  • Writing the intro for an upcoming minor release of Tabler
  • Updating a release description when a headline feature changes before publishing
  • Checking before a release whether the version PR is open but the intro file is missing

Example prompts

  • “Write the release notes intro for the next Tabler minor release from the pending changesets.”
  • “What's new in this version? Draft the release description with a section and picture for each headline feature.”
  • “The version PR is open, check whether the intro file exists and create it if not.”

Requirements

  • A checkout of the Tabler repository
  • GitHub CLI (`gh`) for milestone lookups
  • pnpm

Workflow steps

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

  1. Collect the facts
  2. Layout
  3. Images
  4. Tone
  5. Check the result
  6. Checklist

What it can do on your machine

Read from SKILL.md and the folder at commit dcacb65. 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
    • gh

    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:

    • docs.tabler.io

    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

Tabler Release Notes Intro loads about 1.8k tokens when it runs. Until then it costs about 137 tokens; SKILL.md has 874 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~137
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 tabler/tabler at commit dcacb65, republished under its MIT licence (© tabler). 874 words, ~1,844 tokens.

Download SKILL.mdSave it as .claude/skills/release-notes/SKILL.md (or your agent's skills folder).
name
release-notes
description
Write or update the intro of a Tabler GitHub release — `.github/release-notes/<version>.md`, the part above the generated Core, Demo and Docs lists. Use whenever the user asks for release notes, a release description, a release intro or "what's new in X.Y", and proactively before a minor release when the version PR is open and the intro file is missing. Covers where the facts come from, the fixed layout (cover, headline features with a picture each, then the other changes), the image rules, the tone and how to check the result.

Release notes intro

The GitHub release body has two parts. The intro is hand-written in .github/release-notes/<version>.md (for example 1.6.0.md). The ## Core changes, ## Demo changes and ## Docs changes lists under it are generated by pnpm run release-notes from the CHANGELOG.md files. Never write those lists by hand, and don't repeat them in the intro. .github/release-notes/README.md explains the pipeline. Read it first.

A minor release always gets an intro. A patch release gets one only when it has something a user should hear about. Otherwise the generated lists are enough.

The workflow reads the intro from the commit it publishes, so the file must be on dev before the chore: update versions PR is merged. After the release, the body is never rewritten. A later fix has to be made by editing the release on GitHub.

1. Collect the facts

Never write the intro from memory.

  1. Read every file in .changeset/*.md. The minor entries for @tabler/core are the candidates for headline features. The patch entries feed the smaller sections.
  2. Check the milestone on GitHub (gh api repos/tabler/tabler/milestones) for closed PRs that have no changeset.
  3. For each headline feature, read its docs page (summary, description and the ## headings in docs/content/ui/**). The intro should describe the feature the way the docs do, with the same class names, attributes and events.
  4. Read the upgrade guide for this version (docs/content/ui/getting-started/upgrade/<x-y>.mdx). The ## Upgrading section in the intro summarizes it and links to it.
  5. Before you print a class, an attribute, an event or a number (like the kB saved), check it against the current source.

2. Layout

The layout is fixed, so readers can compare releases. Copy the newest intro (1.6.0.md) and keep this order:

text
<picture> cover (light + dark) </picture>

One paragraph: "Tabler X.Y is out." + the three to five biggest things + a rough count of the rest.

## <Headline feature 1>          ← one section per headline feature
<picture> screenshot </picture>   ← the picture comes right after the heading, before the text
Two or three sentences on what it gives the user.

## <Headline feature 2>
…

---                               ← separator between the headline features and the rest

## <Other change group>           ← grouped smaller changes, no pictures, one short paragraph each
## Demo and docs
## Upgrading                      ← always last: what can break, what is deprecated, link to the guide

Rules:

  • Every headline feature has its own ## section. Don't group eight components under one "New components" heading with bold leads. Each one gets a heading, a picture and its own text.
  • A headline feature needs a picture. If there is none, the feature belongs below the separator, or you make the picture first (section 3).
  • 2 to 4 sentences per feature. Say what it is, when you'd use it, and the one API detail people will look for (a class, a data-bs-* attribute, an event). Mention what it replaces or deprecates, for example "Litepicker is deprecated".
  • Order the headlines by weight. Put the one people waited for first, and small helpers last.
  • Below the separator, group by theme (colors, layout, performance, JS behaviour), not by package. Use one paragraph per group and no bullet dumps. The generated lists already have every item.
  • ## Upgrading closes the intro. Say whether markup has to change, list what can break a build, list what is deprecated with its replacement, and link to https://docs.tabler.io/ui/getting-started/upgrade/<x-y>. It has to agree with the guide.
Show full SKILL.md (415 more words)Show less

3. Images

All images live next to the intro and are named <version>-<slug>.png / <version>-<slug>-dark.png.

  • Cover: <version>-cover.png and <version>-cover-dark.png, 1200×630. Check the size with sips -g pixelWidth -g pixelHeight <file>. The cover shows the release date, so re-export it if the release slips.
  • Feature pictures: make them with the screenshots/ app (see the screenshots skill). Copy the 1x <slug>.png and <slug>-dark.png from screenshots/captures/ and rename them with the version prefix.
  • Use a <picture> block for every image, so GitHub shows the dark one in dark mode:
html
<picture>
  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/tabler/tabler/dev/.github/release-notes/1.6.0-legend-dark.png">
  <img alt="Legend" src="https://raw.githubusercontent.com/tabler/tabler/dev/.github/release-notes/1.6.0-legend.png">
</picture>
  • Link to the raw file on the dev branch, never on a tag. A tag like @tabler/core@1.6.0 has a slash, and raw.githubusercontent.com reads it as part of the path.
  • The alt is the feature name, the same as the heading.
  • The images must be pushed to dev before the release, or the published body shows broken images.

4. Tone

  • Simple English, short sentences, contractions allowed. Write the way the write-docs skill asks.
  • No marketing words: no "powerful", "seamless", "blazing", "game-changer" and no exclamation marks. Say what changed and what it does.
  • Write to the user: "you can", "the sidebar folds now", not "we are excited to announce".
  • Wrap code names in backticks: classes, attributes, events, variables and file paths.
  • Give numbers when they're real: "about 110 kB came off tabler.min.css", "seven chart types".
  • Run the humanize-text skill over the draft if it reads stiff.

5. Check the result

  • git diff --check and a read-through in a Markdown preview in both color modes.
  • Every image URL resolves once pushed: git cat-file -e origin/dev:.github/release-notes/<file> for each one.
  • Every headline feature has a changeset, and every minor core changeset that adds a component or a page is mentioned somewhere in the intro.
  • On dev, pnpm run release-notes builds the body from the working tree's version, so it prints the previous release without the new intro. To see the real body, run it on the bot's files. The steps are in .agents/agents/release-check.md, section 5.
  • The release-check agent audits the intro as part of the pre-release checklist. Run it before the version PR is merged.

6. Checklist

  • Facts come from the changesets, the milestone, the docs pages and the upgrade guide
  • Cover in light and dark, 1200×630, with the right date
  • One ## section per headline feature: heading, <picture>, 2–4 sentences
  • --- separator, then the smaller changes grouped by theme
  • ## Upgrading last, in line with the upgrade guide, linking to it
  • Image URLs point to dev, files named <version>-<slug>[-dark].png
  • On dev before the version PR is merged

© tabler, 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 .agents/skills/release-notes of tabler/tabler.

Open the folder on GitHubat commit dcacb65

Compare with similar skills

Tabler Release Notes Intro 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.

Tabler Release Notes Intro compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tabler Release Notes Intro this skilltabler/tabler42k—~1.8kAutomated safety check: PassMIT
Moraine Release Noteseric-tramel/moraine117—~2.7kAutomated safety check: PassApache-2.0
CicdRussellSB/pytrendy106—~1.6kAutomated safety check: PassMIT
Mole Release Notes Publishertw93/Mole69k—~1.9kAutomated safety check: PassGPL-3.0
RStudio What's New Pagerstudio/rstudio5.1k—~2kAutomated safety check: PassCustom licence
Release Feature Scoringdotnet/core22k—~2.2kAutomated safety check: PassMIT

Similar skills

  • Moraine Release Notes

    eric-tramel/moraine

    Rewrites a moraine GitHub release body into a usage-focused format with install block, what's new, platform table, upgrade notes and one deduplicated changelog.

    117 GitHub stars~2.7k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Cicd

    RussellSB/pytrendy

    A skill your agent uses when touching .github/workflows/, release config (.releaserc), mkdocs.yml, docs deploy, or the whats-new generator.

    106 GitHub stars~1.6k tokensUpdated yesterday
    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.

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

  • RStudio What's New Page

    rstudio/rstudio

    Turns the current release's NEWS.md entries into the RStudio Desktop What's New page, picking only what Desktop users care about, then commits and opens a PR.

    5.1k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed

  • Release Feature Scoring

    dotnet/core

    Official

    Ranks the changes in a release manifest and writes a scored features file that release notes, docs and blog posts can each cut at their own threshold.

    22k GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Azure App Configuration Release Notes

    Azure/AppConfiguration

    Official

    Writes customer-facing release notes for Azure App Configuration libraries and providers in a fixed file layout, version heading and category structure.

    263 GitHub stars~3.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from tabler/tabler

All 21 skills in this repo

  • Tabler Astro Dev Server

    tabler/tabler

    Starts the right Tabler dev server, keeps it from clashing with builds and verifies changes in the browser before a page or component is handed back.

    42k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Tabler Astro Component Scripts

    tabler/tabler

    Rules for adding or fixing client-side scripts in Tabler's Astro components so the copied preview HTML stays readable, self-contained and runs in the right order.

    42k GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Tabler Bootstrap Component Rules

    tabler/tabler

    Sets the file structure, typing and Data API pattern for writing a new Bootstrap-style JavaScript component class in Tabler's vendored port of Bootstrap's JS.

    42k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Tabler Class Reference Tables

    tabler/tabler

    Writes or updates the classnames front matter that renders the class table at the end of a Tabler component docs page.

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

  • Tabler Core JavaScript

    tabler/tabler

    Guidance for changing the Tabler framework's own JavaScript in core/js: the tabler.js and tabler-theme.js bundles, the Bootstrap port and their tests.

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

  • Tabler Core SCSS

    tabler/tabler

    Rules for adding or changing styles in Tabler's core/scss framework: file placement, custom properties, dark mode, RTL, tests and build gates.

    42k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Tabler Release Notes Intro

What does Tabler Release Notes Intro do?

Writes the hand-written intro for a Tabler GitHub release, built from changesets, docs pages and upgrade guides in a fixed layout with a picture per headline feature. github`, in a file named for the version, and generated Core, Demo and Docs lists produced by `pnpm run release-notes` from the changelogs. The skill covers only the intro and says never to write or repeat the generated lists.

When should I use Tabler Release Notes Intro?

Tabler Release Notes Intro fits situations like: writing the intro for an upcoming minor release of Tabler; updating a release description when a headline feature changes before publishing; checking before a release whether the version PR is open but the intro file is missing.

How do I install Tabler Release Notes Intro in Claude Code?

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

How do I install Tabler Release Notes Intro in Codex?

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

Can I use Tabler Release Notes Intro 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 tabler/tabler --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 Tabler Release Notes Intro need to run?

Going by SKILL.md and its folder, Tabler Release Notes Intro needs the command-line tools its instructions call (pnpm, git and gh). Our summary lists: A checkout of the Tabler repository; GitHub CLI (`gh`) for milestone lookups; pnpm.

Does Tabler Release Notes Intro access the network?

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

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

Tabler Release Notes Intro 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 Tabler Release Notes Intro 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 Tabler Release Notes Intro?

Skills that share tags, products or a category with Tabler Release Notes Intro: Moraine Release Notes (eric-tramel/moraine, 117 stars), Cicd (RussellSB/pytrendy, 106 stars), Mole Release Notes Publisher (tw93/Mole, 69k stars) and RStudio What's New Page (rstudio/rstudio, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tabler Release Notes Intro?

tabler (a GitHub organization) maintains it in tabler/tabler, which has 41,821 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 6, 2026.

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